Sun Blade 1500 Boot Warning Message 2

[bryan408]

do a search on google i found out this website very interesting As a newbie, this is a first new problem for y'all pros in here

Whenever i boot up a SUN BLADE 1500 with a new 120GB hardrive Seagate ATA Model: ST3120814 (not from Sun), i always got this warning message
Warning: /pci@1e,600000/ide@d/dad@0,0 (dad0):
corrupt label - wrong magic number
how can i get rid of this message?

This SUN BLADE 1500 runs on Solaris 8, OBP 4.17.1, 1GB mem, Serial # 63233863, Ethernet Address 0:3:ba:c4:df:47
and the original SEAGATE hardrive from SUN is ATA model ST3120026A

 

[bryan408]

i have occurred another problem. i tried the command dd if=/dev/zero of=/dev/rdsk/c0t0d0s0 count=1024 and reboot the system and i can't boot up the system at this point (message:Bad magic numer.... cant' boot disk...)
what does that command do to the disk and how can i make that disk be able to boot up without reload the solaris again?

Best regards,
Bryan

 

[tuka]

You have overwrote(ZERO'ed) the first 1024 blocks of the disk. The disk is FUBAR.

 

[tuka]

My mistake you sent zeros to the disk slice 0 X 1024 counts.

Slice 0 has a lot of zeros.

 

[tuka]

The disk itself is okay, jsut slice 0 has a lot of zeros and no data of value.

 

[cndcadams]

bryan408;

basically reload is what Tuka is trying to say nicely.

This is why I had you run that command on your non-boot drive so you would not have to reload. Guess I should have put in my previous post that the command is data destructive.

Just walk away, don't act on your urge to bounce the drives off the ground. Then come back and start your reload.

CA

 

[bryan408]

sorry guys,
i'm little lost what am i supposed to do now???

Best regards,
Bryan

 

[cndcadams]

bryan408;

I hope this was a test bed?

If you had a backup, boot cdrom -sw, newfs slice /dev/dsk/c0t0d0s0, mount /dev/dsk/c0t0d0s0 /a and restore from tape.

or reload the OS. If this is a test bed why don't you load solaris 9 if possible to see if this could be a driver issue causing the problem (I doubt it but it would be another thing you can rule out).

thanks

CA

 

[bryan408]

cndcadams,
i dont have these problem with solaris 9 and 10 though
only with solaris 8 and it's really bugging me so much yeah let me try to restore that drive then

tuka,

i have tried the od -x c0t0d0s2 0x0 but it seems doesnt work

message:
od: cannot open c0t0d0s2: No such file or directory
od: cannot open 0x0: No such file or directory

i really don't understand ******Lets look at the whole disk label in hex and look for VTOC_SANE AND DKL_MAGIC??????????

 

[tuka]

Bryan ,

Forget about checking the VTOC_SANE and DKL_MAGIC. The file is gone. The command should be:
od -x /tmp/diskdata.dat 0x0

You will have to restore. If no backup is available then a rebuild is required.

 

[bryan408]

tuka,
it's weird the first time i tried od -c /tmp/diskdump.dat 0x0 but it didn't work now it's ok
what is wrong though?



# dd if=dev/dsk/c0t0d0s2 of=tmp/diskdump.dat bs=512 count=1
1+0 records in
1+0 records out
# od -c /tmp/diskdump.dat 0x0
0000000 S T 3 1 2 0 0 2 6 A c y l 5
0000010 7 4 5 9 a l t 2 h d 1 6
0000020 s e c 2 5 5 \0 \0 \0 \0 \0 \0 \0 \0
0000030 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
*
0000080 \0 \0 \0 001 \0 \0 \0 \0 \0 \0 \0 \0 \0 \b \0 002
0000090 \0 \0 \0 003 \0 001 \0 005 \0 \0 \0 \0 \0 \0 \0 \0
00000a0 \0 \0 \0 \0 \0 \0 \0 004 \0 \0 \0 \0 \0 \0 \0 \0
00000b0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 ` \r 336 356
00000c0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
*
00001a0 \0 \0 \0 \0 025 030 340 u \0 \0 \0 \0 \0 \0 \0 001
00001b0 340 s \0 002 \0 020 \0 377 \0 \0 \0 \0 \0 \0 \0 \0
00001c0 \0 > 201 @ \0 \0 003 354 \0 017 320 \0 \0 \0 \0
00001d0 \r 371 ( 320 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0
00001e0 \0 \0 \0 \0 \0 \0 005 357 \0 > 201 @ \0 \0 \t 333
00001f0 \0 > 201 @ \0 \0 \r 307 001 8 206 @ 332 276 9 8
0000200
#

# od -x /tmp/diskdata.dat 0x0
od: cannot open /tmp/diskdata.dat: No such file or directory
od: cannot open 0x0: No such file or directory
#
#
# od -x /tmp/diskdump.dat 0x0
0000000 5354 3331 3230 3032 3641 2063 796c 2035
0000010 3734 3539 2061 6c74 2032 2068 6420 3136
0000020 2073 6563 2032 3535 0000 0000 0000 0000
0000030 0000 0000 0000 0000 0000 0000 0000 0000
*
0000080 0000 0001 0000 0000 0000 0000 0008 0002
0000090 0000 0003 0001 0005 0000 0000 0000 0000
00000a0 0000 0000 0000 0004 0000 0000 0000 0000
00000b0 0000 0000 0000 0000 0000 0000 600d deee
00000c0 0000 0000 0000 0000 0000 0000 0000 0000
*
00001a0 0000 0000 1518 e075 0000 0000 0000 0001
00001b0 e073 0002 0010 00ff 0000 0000 0000 0000
00001c0 003e 8140 0000 03ec 0020 0fd0 0000 0000
00001d0 0df9 28d0 0000 0000 0000 0000 0000 0000
00001e0 0000 0000 0000 05ef 003e 8140 0000 09db
00001f0 003e 8140 0000 0dc7 0138 8640 dabe 3938
0000200

 

[bryan408]

forget about the first output line S T 3 1 2 0 0 2 6 A it's supposed to be S T 3 1 2 0 8 1 4 A cause i've just tried both drives to compare the output anyway just ignored them
best regards
Bryan

 

[cndcadams]

bryan408;

So you said that you do not get these errors if you are running solaris 9. Very interesting, leads me to believe this is a driver issue.

Have you loaded any patches for the solaris 8 environment. The dad driver patch would be the first one i tried then the kernel patch.

dad driver patch for solaris 8 is 108974-50. this is a public patch so you don't need a software contract to get it.

If those don't work load the recommended cluster and see if that clears up the issue.

thanks

ca

 

[bryan408]

cndcadams,
sorry i'm very dummy with solaris 8 and sun system
i don't really know i have any patches for Sol 8 Environment
dad driver patch???? kernel patch????
Anyway i try to download dad driver patch for Sol 8 108974-50 from sun and load it up.
ah what is "recommended cluster" anyway?
Best regards,
Bryan

 

[cndcadams]

bryan408;

to show patches and patch levels you can do a showrev -p, or showrev -a.

If looking for a particluar patch you could do

showrev -p | grep 108974-50 which will show the patch if installed.

or showrev -p | grep 108974-* which will give you info if you don't know the rev level of the patch

Recommended cluster patches are what Sun currently suggest you install on your system. It includes multiple patches.

You will need a sun account login and password as not alll the patches in the cluster are public.


Cluster patches are found at

http://au.sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

Thanks

ca

 

[bryan408]

cndcadams,

I already installed 108974-50 but still it didn't clear up the problem.

****

http://au.sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

****so which patch in the cluster should i download???

best regards,
Bryan

 

[cndcadams]

Bryan408;

you are running solaris 8 so you need the solaris 8 patch cluster. run more /etc/release it will show you what you are running.

I believe you need the sol8 159.6m cluster

thanks

CA

 

[bryan408]

cndcadams,
yep i already loaded SOL 8 159.6m Cluster, 108974-50, and 111792-16 and the warning messages are still there.

i also have another problem though. Sometimes the SunBlade 1500 can't boot up, it just hang rite after it shows the warning message: wrong magic number @disk0, and i have to turn off the power then turn back on again and it works ?????

 

[cndcadams]

bryan408;

Things are sounding rather bleek (spelling? to lazy to check). I really don't know what else you can do. The system firmware looked uptodate, the OS has been patched. You have tried relabeling. Have you contacted your Vendor to see if their QC dept. has any answers?

Basically I am out of ideas!

CA

 

[bryan408]

thank you so much for all replies
i really appreciate your help cndcadams, tuka
Best regards,
Bryan