Sun Enterprise 6500 DON'T BOOT ANYMORE

Hi to all,

I have a Sun Enterprise 6500 running with solaris 8 and Veritas Volume Manager 3.2 with boot disk incapsulated.

After a DIMM failure the system done a panic and boot again perfectly. All this happen on friday, I received the part on monday but in the week-end the system panic again and don't boot anymore. I suppose because the DIMM and on monday I replaced the DIMM but the system

Don't boot anymore.

below the boot msgs :

{1} ok boot

Resetting...

Software Power ON

Clock board TOD does not match TOD on any IO board.

screen not found.

Can't open input device.

Keyboard not present. Using ttya for input and output.

Clock board TOD does not match TOD on any IO board.

16-slot Sun Enterprise E6500, No Keyboard

OpenBoot 3.2.30, 30720 MB memory installed, Serial #15561205.

Copyright 2002 Sun Microsystems, Inc. All rights reserved

Ethernet address 8:0:20:ed:71:f5, Host ID: 80ed71f5.

Rebooting with command: boot

Boot device: rootdisk File and args:

SunOS Release 5.8 Version Generic_108528-27 64-bit

Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.

/kernel/drv/sparcv9/fcaw symbol ddi_model_convert_from multiply defined

fcaw0: JNI Fibre Channel Adapter model FCW

fcaw0: 64-bit SBus 2: IRQ 3: FCODE Version 13.5.7 [1a5e9b]: SCSI ID 125: AL_PA 01

fcaw0: Fibre Channel WWNN: 100000E06940ACBD WWPN: 200000E06940ACBD

fcaw0: FCA SCSI/IP Driver Version 2.6.13, Feb 26, 2003 for Solaris 64-bit

fcaw0: All Rights Reserved.

NOTICE: fcaw0 NPORT Initialization Complete, SID=40ACBD

fcaw1: JNI Fibre Channel Adapter model FCW

fcaw1: 64-bit SBus 2: IRQ 3: FCODE Version 13.5.7 [1a5e9b]: SCSI ID 125: AL_PA 01

fcaw1: Fibre Channel WWNN: 100000E06940ACBD WWPN: 200000E06940ACB4

fcaw1: FCA SCSI/IP Driver Version 2.6.13, Feb 26, 2003 for Solaris 64-bit

fcaw0: New Fabric Parameters Received. Resetting...

fcaw1: All Rights Reserved.

fcaw0: LINK DOWN

NOTICE: fcaw0 NPORT Initialization Complete, SID=40ACBD

fcaw0: LINK UP(180002FF)

fcaw0: Host: Port 7F2513 (100000E06940ACBD:200000E06940ACBD)

fcaw0: Port 7F1B13 (5006016090602E38:5006016110602E38) available.

fcaw0: Port 7F2C13 (50060484497D3256:50060484497D3256) available.

fcaw0: Port 624413 (50060484497D2E53:50060484497D2E53) available.

fcaw0: Port 624813 (50060484497D2E56:50060484497D2E56) available.

fcaw0: Port 7F1C13 (50060484497D3253:50060484497D3253) available.

fcaw1: LINK DOWN: Check Connections...

fcaw0: Target 0: Port 7F1B13 (5006016090602E38:5006016110602E38) online.

fcaw0: Target 0 Lun 0: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

fcaw0: Target 1: Port 7F2C13 (50060484497D3256:50060484497D3256) online.

fcaw0: Target 1 Lun 0: Port 7F2C13 (50060484497D3256:50060484497D3256) present.

WARNING: /sbus@2,0/fcaw@2,0/sd@1,0 (sd31):

corrupt label - wrong magic number

fcaw0: Target 2: Port 624413 (50060484497D2E53:50060484497D2E53) online.

fcaw0: Target 2 Lun 0: Port 624413 (50060484497D2E53:50060484497D2E53) present.

WARNING: /sbus@2,0/fcaw@2,0/sd@2,0 (sd32):

corrupt label - wrong magic number

fcaw0: Target 3: Port 624813 (50060484497D2E56:50060484497D2E56) online.

fcaw0: Target 3 Lun 0: Port 624813 (50060484497D2E56:50060484497D2E56) present.

WARNING: /sbus@2,0/fcaw@2,0/sd@3,0 (sd33):

corrupt label - wrong magic number

fcaw0: Target 4: Port 7F1C13 (50060484497D3253:50060484497D3253) online.

fcaw0: Target 4 Lun 0: Port 7F1C13 (50060484497D3253:50060484497D3253) present.

WARNING: /sbus@2,0/fcaw@2,0/sd@4,0 (sd34):

corrupt label - wrong magic number

fcaw0: Target 0 Lun 1: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

fcaw0: Target 0 Lun 2: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

fcaw0: Target 0 Lun 3: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

fcaw0: Target 0 Lun 4: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

fcaw0: Target 0 Lun 5: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

fcaw0: Target 0 Lun 6: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

fcaw0: Target 0 Lun 7: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

fcaw0: Target 0 Lun 8: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

fcaw0: Target 0 Lun 9: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

fcaw0: Target 0 Lun 10: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

fcaw0: Target 0 Lun 11: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

fcaw0: Target 0 Lun 12: Port 7F1B13 (5006016090602E38:5006016110602E38) present.

WARNING: /sbus@2,0/fcaw@2,0/sd@4,9c (sd1127):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,9c (sd362):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@4,9c (sd1127):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,9c (sd362):

corrupt label - wrong magic number

NOTICE: vxvm:vxdmp: disabled path 32/0x2338 belonging to the dmpnode 238/0x208

NOTICE: vxvm:vxdmp: disabled dmpnode 238/0x208

WARNING: /sbus@2,0/fcaw@2,0/sd@4,9d (sd1128):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,9d (sd363):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@4,9d (sd1128):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,9d (sd363):

corrupt label - wrong magic number

NOTICE: vxvm:vxdmp: disabled path 32/0x2340 belonging to the dmpnode 238/0x210

NOTICE: vxvm:vxdmp: disabled dmpnode 238/0x210

WARNING: /sbus@2,0/fcaw@2,0/sd@4,9e (sd1129):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,9e (sd364):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@4,9e (sd1129):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,9e (sd364):

corrupt label - wrong magic number

NOTICE: vxvm:vxdmp: disabled path 32/0x2348 belonging to the dmpnode 238/0x218

NOTICE: vxvm:vxdmp: disabled dmpnode 238/0x218

WARNING: /sbus@2,0/fcaw@2,0/sd@4,9f (sd1130):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,9f (sd365):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@4,9f (sd1130):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,9f (sd365):

corrupt label - wrong magic number

NOTICE: vxvm:vxdmp: disabled path 32/0x2350 belonging to the dmpnode 238/0x220

NOTICE: vxvm:vxdmp: disabled dmpnode 238/0x220

WARNING: /sbus@2,0/fcaw@2,0/sd@4,a0 (sd1131):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,a0 (sd366):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@4,a0 (sd1131):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,a0 (sd366):

corrupt label - wrong magic number

NOTICE: vxvm:vxdmp: disabled path 32/0x2358 belonging to the dmpnode 238/0x228

NOTICE: vxvm:vxdmp: disabled dmpnode 238/0x228

WARNING: /sbus@2,0/fcaw@2,0/sd@4,a1 (sd1132):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,a1 (sd367):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@4,a1 (sd1132):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,a1 (sd367):

corrupt label - wrong magic number

NOTICE: vxvm:vxdmp: disabled path 32/0x2360 belonging to the dmpnode 238/0x230

NOTICE: vxvm:vxdmp: disabled dmpnode 238/0x230

WARNING: /sbus@2,0/fcaw@2,0/sd@4,a2 (sd1133):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,a2 (sd368):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@4,a2 (sd1133):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,a2 (sd368):

corrupt label - wrong magic number

NOTICE: vxvm:vxdmp: disabled path 32/0x2368 belonging to the dmpnode 238/0x238

NOTICE: vxvm:vxdmp: disabled dmpnode 238/0x238

WARNING: /sbus@2,0/fcaw@2,0/sd@1,0 (sd31):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@4,3 (sd974):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,3 (sd209):

corrupt label - wrong magic number

The system is coming up. Please wait.

checking ufs filesystems

fsck: line in vfstab has too few entries

WARNING - Unable to repair one or more filesystems.

Run fsck manually (fsck filesystem...).

Exit the shell when done to continue the boot process.

Type control-d to proceed with normal startup,

(or give root password for maintenance)

waiting,

best regards

Tug

[9136 byte] By [tugmani] at [2007-11-26 9:58:19]
# 1
The 'copy-clock-tod-to-io-boards' command may help you here, you can find information about it in the firmware documentation. Your firmware patch ( 103346-30 ) seems to be the latest version as far as I can tell.
mlennon at 2007-7-7 1:23:48 > top of Java-index,General,Talk to the Sysop...
# 2
i'd boot net or cdrom or single user and checkout that fsck warning about a broken /etc/vfstab. once that is corrected hopefully the system might make more progress.tim
timuglow at 2007-7-7 1:23:48 > top of Java-index,General,Talk to the Sysop...
# 3

Look at the errors

WARNING: /sbus@2,0/fcaw@2,0/sd@4,9c (sd1127):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,9c (sd362):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@4,9c (sd1127):

corrupt label - wrong magic number

WARNING: /sbus@2,0/fcaw@2,0/sd@1,9c (sd362):

corrupt label - wrong magic number

It seems something wrong with disks.

dombal at 2007-7-7 1:23:48 > top of Java-index,General,Talk to the Sysop...
# 4

The disk errors are more than likely nothing to be concerned about. My experiences with fcaw disks have produced the same results. The errors are just showing that the disks have not been labeled by the OS.

Looks like the disks are attached to an EMC SAN?

Booting to single user mode, or from CD (or network) to view the vfstab is what is needed.

NoWin4Me at 2007-7-7 1:23:48 > top of Java-index,General,Talk to the Sysop...
# 5
Is it possible that the cabling was not replaced correctly when the DIMM was replaced?--A.
andrewness at 2007-7-7 1:23:48 > top of Java-index,General,Talk to the Sysop...
# 6

{EDIT} Sorry didn't see this original post is a month old. If this system is still down I don't think the admin cares anymore.

I all so would double check the cabling. Then I would boot from cdrom and comment out everything you can in the vfstab(excpet for /, /etc, /var, etc). This will at least make sure your system and OS is healthy. Then you can start to mount your veritas volumes one at a time and see if some of the drives are not accessable.

You also will whant to look at what drives can be seen when the CD is booted.

Message was edited by:

Lee_McCreery

Lee_McCreery at 2007-7-7 1:23:48 > top of Java-index,General,Talk to the Sysop...