cancel
Showing results for 
Search instead for 
Did you mean: 

Rootdrive failure & Rootmirror keeps asking for new Superblock

Sunny_Sysadmin
Level 3
I have a Sun V480 server running Solaris 9. The server has two 36GB internal drives that are mirrored using Veritas Volume Mgr (version unknown). The primary rootdrive has failed and I cannot get the system to boot off the rootmirror drive. Below are further details I am able to see by booting into single user mode off of the Solaris 9 cd.

1) ERROR: OpenBoot Diagnostics failed

The following two warnings...does this indicate a failed NIC card or that perhaps there is no network cable in those particular ports??

WARNING: Device /pci@8,700000/pci@2/SUNW,qfe@2,1 being marked with 'status' == fail
WARNING: Device /pci@8,700000/pci@2/SUNW,qfe@1,1 being marked with 'status' == fail

Rebooting with command: boot cdrom -s
Boot device: /pci@8,700000/ide@6/cdrom@0,0:f File and args: -s
SunOS Release 5.9 Version Generic_117171-07 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
WARNING: status 'fail' for '/pci@8,700000/pci@2/SUNW,qfe@1,1'
WARNING: status 'fail' for '/pci@8,700000/pci@2/SUNW,qfe@2,1'
WARNING: Device ssd1 failed to power up.
WARNING: Please see your system administrator or reboot.
WARNING: Device ssd1 failed to power up.
WARNING: Please see your system administrator or reboot.
Configuring /dev and /devices
Using RPC Bootparams for network configuration information.
Skipping interface fcip0
Skipping interface ce1

2) Once in single user mode, I ran the command: "echo | format" to view the disks...

AVAILABLE DISK SELECTIONS:
0. c1t0d0 <*drive not available*>
/pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf96d267,0

1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf96cd2b,0

iostat -En also revealed that device c1t1d0 has 8 "Hard Errors"

3) From the "ok" prompt, printenv shows the following information for the disks

boot-device rootdisk rootmirror

If I attempt to perform a "boot rootmirror" from the ok prompt, I get the following message:

Rebooting with command: boot rootmirror
Boot device: /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf96cd2b,0:a File an d args:
The file just loaded does not appear to be executable.

4) Here is the output from my attempt to fsck the good drive...

fsck -y /dev/rdsk/c1t1d0s0

** /dev/rdsk/c1t1d0s0
BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION;

So, I use the newfs command to view available super blocks as follows:

newfs -N /dev/rdsk/c1t1d0s0

Warning: cylinder groups must have a multiple of 16 cylinders with the given
parameters
Rounded cgsize up to 256
/dev/rdsk/c1t1d0s0: 16779312 sectors in 5808 cylinders of 27 tracks, 107 sectors
8193.0MB in 182 cyl groups (32 c/g, 45.14MB/g, 5632 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 92592, 185152, 277712, 370272, 462832, 555392, 647952, 740512, 833072,
15902432, 15994992, 16087552, 16180112, 16272672, 16365232, 16457792,
16550352, 16642912, 16735472,

Attempts to use any of the above super blocks doesn't appear to work...see sample output as follows:

fsck -F ufs -o b=16180112 /dev/rdsk/c1t1d0s0

Alternate super block location: 16180112.
** /dev/rdsk/c1t1d0s0
BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION;
eg. fsck [-F ufs] -o b=# [special ...]
where # is the alternate super block. SEE fsck_ufs(1M).

Any help would be appreciated, my goal here obviously is to see if I can boot from the mirrored drive and then I will get the other drive replaced.
 
I found this document: http://seer.entsupport.symantec.com/docs/233187.htm , but since I am having to boot into single user mode from the cdrom drive, the /dev/vx/.... path isn't available to me. I did find a copy of the vfstab that I will post below. This copy of the vfstab I had saved off to another system for safe keeping.

#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes -
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/vx/dsk/swapvol - - swap - no -
/dev/vx/dsk/rootvol /dev/vx/rdsk/rootvol / ufs 1 no logging
/dev/vx/dsk/var /dev/vx/rdsk/var /var ufs 1 no logging
swap - /tmp tmpfs - yes size=2048m
#NOTE: volume rootvol (/) encapsulated partition c1t0d0s0
#NOTE: volume swapvol (swap) encapsulated partition c1t0d0s1
#NOTE: volume var (/var) encapsulated partition c1t0d0s5

and here is a saved output of the df command:

Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/rootvol 4129290 1443242 2644756 36% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
mnttab 0 0 0 0% /etc/mnttab
/dev/vx/dsk/var 4129290 471328 3616670 12% /var
swap 16817272 32 16817240 1% /var/run
swap 2097152 88 2097064 1% /tmp

and finally, a vxdisk list output that had been saved off prior to the drive failure

DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 sliced rootdisk rootdg online
c1t1d0s2 sliced rootmirror rootdg online
5 REPLIES 5

cowboycraig
Level 4



at the OK prompt do a:

probe-scsi-all


Then try a "boot" from what ever device it shows to be rootmirror. Maybe the alias isn't correct.


Craig



Sunny_Sysadmin
Level 3
Ok, here is the output from performing a "probe-scsi-all":
 
LiD HA LUN  --- Port WWN ---  ----- Disk description -----
 0   0   0  21000004cf96d267  SEAGATE ST336605FSUN36G 0438
 1   1   0  21000004cf96cd2b  SEAGATE ST336605FSUN36G 0438
 
And here is some additional information that will hopefully help.....
 
Devalias output for disks
===========================
rootmirror               /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf96cd2b,0:a
rootdisk                 /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf96d267,0:a
disk1                    /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@1,0
disk0                    /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@0,0
disk                     /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@0,0
 
Attempts to boot to the above devices
=======================================
ok boot rootmirror
Boot device: /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf96cd2b,0:a  File and args:
The file just loaded does not appear to be executable.
 
 ok boot disk1
Boot device: /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@1,0  File and args:
The file just loaded does not appear to be executable.
 
ok boot disk0
Boot device: /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@0,0  File and args:
Can't open boot device
 
ok boot disk
Boot device: /pci@9,600000/SUNW,qlc@2/fp@0,0/disk@0,0  File and args:
Can't open boot device
 
Any other suggestions or tips would be greatly appreciated.
 
 

bbh
Not applicable
Employee
Isn't there a "vx" prefix to the names of the encapsulated boot disk and its mirror?
Try boot vx-rootdisk

sunshine_2
Level 4
looks like you have a bootblk problem

example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk \
               /dev/rdsk/c1t0d0s0

sunshine_2
Level 4

Boot block on the hard disk is corrupted .Boot the system in single user mode with cdrom and reinstall boot block .

# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t3d0s0