Solaris 10 drive concat. restore

[dyebyu]

I recently moved the drives from one solaris box to a new case with new hardware. The box had a volume that spanned 3 disks (I used growfs to create them). After installing the disks in the new box I booted and found that my large volume is unavailable. boot -s reports "Unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c0d0s0). I tried the command and the OS reported "Can't stat /dev/rdsk/c0d0s0". I was worried that I might've mixed up order of the drives in the volume, so I switched them around and rebooted only to get the same result. How can I check the configuration to see what order the drives should be in, and how do I fix the root filesystem once the drives are ordered properly? What other steps do I need to take to restore my volume?

I ran metastat and got the following information. I think it tells me that the primary master drive is a 40gig WD, the secondary master is a 120gig WD, and the secondary slave is an 80gig WD. I'm not sure, though, if that's right; I also don't know if there's anything else in there that can help me. Thank you in advance for your consideration and assistance.


d1: concat/stripe
size: 207GB
stripe 0:
dev. start block dbase reloc
c0d0s3 18144 y y

stripe 1:
c1d1s2 20160 y y

stripe 2:
c1d0s2 20160 y y


device relocation information:
dev. reloc. device id
c0d1 y id1,cmdk@awdc_wd400bb-00ccb0=wd-wma9t1086391
c1d1 y id1,cmdk@awdc_wd800jb-22ja0=wd-wcam92628840
c1d0 y id1,cmdk@awdc_wd1200sb-01kbc0=wd-wcala1853591

 

[marrow]

thread60-1156930
thread60-1142849
thread60-761144

Not sure if this'll help

 

[dyebyu]

Thank you for taking the time to respond to my problem. I'm not sure, though, what will happen to my concatenated volume if I can get fsck to run on the disk containing the root filesystem. Do I need to have the drives in the right order and the metadb stuff accurate before I run fsck? I don't want to blow away my data by attempting to repair one drive in the series while ignoring the others.

However, I am ready to apply the procedures in the posts you mentioned if it turns out that this disk stat problem is, in fact, the only thing that needs fixing.

 

[coffeysm]

Are you running the X86 version of Solaris?

 

[dyebyu]

Yes. Sorry for not mentioning it earlier.

 

[coffeysm]

I still don't understand everything though. So your root file system is part of that concatnation or is on a separate disk totally? The first thing I would do is get your boot drive up -odds are you need to rebuild the /dev, /devices, and /etc/path_to_inst file- You can not just swap from one hardware to another and expect the drives to boot up.