v440 raidctl problems with boot disk
I actually created this problem myself. I have two v440s and one has a quad ethernet card and one doesn't . I swapped the disks and neither system came back up. I swapped the disks back and one system came back up. I booted the other one from the cdrom and then when I run raidctl I get:
# raidctl
RAID RAID RAID Disk
Volume Status Disk Status
c1t0d0 FAILED c1t1d0 MISSING
c1t0d0 OK
# raidctl -d c1t0d0
# raidctl -c c1t0d0 c1t1d0
Disk 'c1t0d0' is not present.
Cannot create RAID volume.
I tried deleting the device and creating the device but the delete of the device doesn't work. Anyone have any ideas? Should I post this to the storage group as well?
The raidctl command on Solaris 8 appears to be different from the one on Solaris 9 and has quite a few less options.
Any help would be greatly appreciated.
Susan
# 2
I got "Disk 'c1t0d0' is not present." too just like susan_short did so I just ran devfsadm and tried again but the result was even more disappointing:
Before devfsadm:
# raidctl -c c0t0d0 c0t1d0
Disk 'c0t1d0' is not present.
Cannot create RAID volume.
After running devfsadm:
# raidctl -f -c c0t0d0 c0t1d0
Cannot create RAID volume, disk "c0t0d0" is mounted .
Is this for real? I mean I can't re-attach a broken mirror while online? Even ODS gives you that.
If anyone knows (please don't guess if you can't test your guesses) how to re-attach a split mirror online please post how.
BTW I'm on a T2000 not a v440.
Thanks,
Ken
# 3
Now that I'm booted from the DVD and c0t0d0 is not mounted I get:
# raidctl -c -r 1 c0t0d0 c0t1d0
Creating RAID volume c0t0d0 will destroy all data on member disks, proceed (yes/no)?
"WILL" destroy the on "ALL" member disks? With RAID-1? How astonishing.
I went ahead and used "yes" since I think that message about destroying all the member disks is not valid for RAID-1 only RAID-0, etc.
While the resyncing is in progress I see
# fsck -n /dev/rdsk/c0t0d0s0
** /dev/rdsk/c0t0d0s0 (NO WRITE)
** Last Mounted on /
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3a - Check Connectivity
** Phase 3b - Verify Shadows/ACLs
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cylinder Groups
4506 files, 121973 used, 368578 free (2890 frags, 45711 blocks, 0.6% fragmentation)
#
So either it's not really destroying anything or it's not starting at the beginning of the disk.
The worst part is that you should be able to rebuild a RAID-1 volume in mult-user mode using raidctl but even with the "-f" option raidctl doesn't let you do it. How un-UNIX-like.
