Ultra 60 Boot hang with "Timeout waiting for ARP/RARP packet

[werb]

Hi All,
I baught a SUN ULTRA 60 450 MHz 2048 MB Memory,
CD-Rom Drive and 18 GB Harddisk.

If I power on the U60 following messages are displayed:

Sun Ultra 60 UPA/PCI (UltraSPARC-II 450MHz), Keyboard Present
OpenBoot 3.23, 2048 MB memory installed, Serial # .........
Ethernet address ..... , Host ID: .....

Bad magic number in disk label
Can't open disk label package
Boot devices: net File and args:
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout wai......................................
............................

no keyboard input possible.
I leave it on for 1 hour and no Boot prompt appears.
what means:
Bad magic number in disk label
Can't open disk label package
?????
any suggestion how to solve this problem.

thx
Werner

 

[cndcadams]

You need to fsck the boot drive. Do you have a Solaris OS CD?

When the systam banner appears, before it starts to try booting hit STOP and A key at the same time. This should drop you to the OK prompt.

Do yourself a favor and set auto-boot to false. This way when you power it on it will go to ok prompt and not just try booting. Once you fix this problem you can set it back to true.

Insert your OS cd, then type boot cdrom -s wait for it to boot. Then run fsck -y and it should fsck the boot drive. Once it is finished do type halt and hit enter the try typing boot and hit enter and see if it boots. If It still does not boot then let me know, you may need try reinstalling the boot block.

Thanks

CA

 

[werb]

I did it, so far so good
now I am able to boot from CD-Rom

But now the error message has changed:

WARNING: /pci@1f, 4000/scsi@3/sd@0,0 (sd2)
Corrupt label; wrong magic number

I think it's not the harddisk because I replaced the
harddisk with a new one but the error is still there :-(

thx
Werner

 

[cndcadams]

Werb;

That actually is a disk error. When you bought this system did the original drive come with an OS installed? If fsck dd not fix the issue then you should try to install a new boot block, this will not destroy the OS if it has one.

To verify the system is seeing the drive run probe-scsi from the OK prompt.


The second drive, did it come from another U60 which had an OS?

Try running fsck on this drive by runnning boot cdrom -s, then fsck -y.

The drive you just installed if it has no OS, run boot cdrom -s and run the format command. Choose the drive which will be #0; when you choose it it will ask if you want to label it, answer Y, If the drive can not be labeled this is a bad drive. Then quit format, then halt the system. Then run boot cdrom and you should be able to install the OS on the drive.

Thanks

CA

 

[werb]

Hello again,

the second drive I tested was a new empty drive. I don't know if there is
an OS installed on the originsl drive.
I did following tests on the OK prompt:

OK test scsi
"no output on the screen the cursor simply come back to OK prompt"

OK probe-scsi -->shows following output
Target 0
Unit 0 Disk FUJITSU MAJ3182M SUN18G 0804
Target 6
Unit 0 Removable Read Only device TOSHIBA XM6201TASUN32XCD1103
"and return to the "OK" prompt
OK probe-scsi-all ---> shows following output
/pci@1f,4000/scsi@3,1

/pci@1f,4000/scsi@3
Target 0
Unit 0 Disk FUJITSU MAJ3182M SUN18G 0804
Target 6
Unit 0 Removable Read Only device TOSHIBA XM6201TASUN32XCD1103
"and return to the "OK" prompt
OK
OK boot cdrom -s --> boot to single user mode ?? I think
Boot devices..............
SunOS Release 5.10.............
Copyright..........................
Use is subject to................
Booting to milestone..................
Configuring devices.
WARNING: /pci@1f, 4000/scsi@3/sd@0,0 (sd2)
corrupt label; wrong magic number

Using RPC Bootparms............
Attempting to configure....................
Skipped interface.....................
Requesting System Management Mode
SINGLE USER MODE
# fsck -y
# "no output come only back to # prompt
# init 0
OK "get back to OK prompt"
OK test scsi "by the next try of test scsi the message following appears"
Bus fault
Bus fault
Bus fault
Bus fault "now no more input is possible I have to power off an power on"
............ "the U60 and if I try to install Solaris the install screen says"
"there is no harddisk on your system"

any idea ??? :-o
does anybody know if the Adaptec 39160 Contoller is
supported by SUN Ultra 60 and Solaris 10 ???

thx

werb

 

[cndcadams]

werb;

As my other post says;

boot cdrom -s and run the format command. Choose the drive which will be #0; when you choose it, it will ask if you want to label it, answer Y, If the drive can not be labeled this is a bad drive. Then quit format, then halt the system. Then run boot cdrom and you should be able to install the OS on the drive.

As far as the controller Adaptec 39160, your best bet is to put it into the system and see if probe-scsi-all recognizes it. If the low level doesn't recognize it, then the OS will not recognize it.

Also the reason you got the bus error is because you did an init 0 then tried running test, you need to type reset then hit enter. For some reason the OBP can't handle low level commands when being brought down from CD, or OS. Also I would not worry about running test commands as probe-scsi or probe-scsi-all really does the same thing and actually works.

Anyways go ahead and do my first part of this post and then you should be able to load the OS.

Thanks

CA
Thanks

CA

 

[werb]

Hello CA,

your hints where very helpfull, thank you very much !!!!


;-)

Installation is running right now and the harddisk was found

Problem fixed
thx

werb

 

[daFranze]

Servus Werner,

the problems you are facing is by 90% a failed disk.
The OBP tries to boot the "default boot device" set in OBP. The disk label of the disk cannot be read (faulty disk, mad controller, etc) by OBP. The alternate boot device is net; if you haven't setup Jumpstart (bootserver & installserver) your arp requests get no answer, the machine will never boot...

I am not sure if your Adaptec 39160 is supported by Sun, but I suggest to remove everithing from the box, which is not Sun to find out, what's the root of all evil...

btw: running OBP Commands after a "init 0" is not a good idea; Sun recommends to use the following procedure:

# init 0
-> ok setenv auto-boot? false
-> ok reset
or
-> ok reset-all
depending on the OBP Version
-> probe-scsi-all
or other OBP commands


Best Regards, Franz
--
UNIX System Manager from Munich, Germany