stuck in SVM and grub hell

Hi--

I have a Solaris 10 system that had its root partition mirrored in a standard volume manager setup. One disk had an error and then the next one soon after. Now I am unable to boot the second disk (it just flips out looking for md database info etc) and I can't complete a good boot on the first disk now.

The / file system (/dev/md/rdsk/d10) is being checked.

WARNING - Unable to repair the / filesystem. Run fsck

manually (fsck -F ufs /dev/md/rdsk/d10).

Oct 16 16:27:19 svc.startd[7]: svc:/system/filesystem/usr:default:

Method"/lib/svc/method/fs-usr" failed with exit status 95.

[ system/filesystem/usr:default failed fatally (see'svcs -x'for details) ]

Requesting System Maintenance Mode

(See /lib/svc/share/READMEfor more information.)

Console login service(s) cannot run

Root passwordfor system maintenance (control-d to bypass):

I have tried mounting c1d0s0 manually in /mnt, editing vfstab to only point to static partitions, and doing the bootadm update-archive. But it still tries to do an fsck on the mirrored root partition. I am stuck in a loop here. What can I do to get booted on a static volume? thanks for any suggestions

[1447 byte] By [MattSF] at [2007-11-26 10:50:23]
# 1
You need to boot from cd or net boot then mount the disks and edit both vfstab and /etc/system.The procedure is described here http://sunsolve.sun.com/search/document.do?assetkey=1-9-76217-1
robertcohen at 2007-7-7 3:02:58 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...
# 2

thanks for the reply! i had been booting from cdrom several times, and I had gone ahead and mounted the first disk and edited the vfstab, system, md.cf and md.conf files. What was happening was that during the bootadm update-archive, it was dragging in the info from the second disk. That disk still had the old md info in vfstab, system, etc. once i edited those, I was finally able to do the bootadm thing, and boot off of the first disk successfully.

it was a bit of an ordeal, but I finally got it sorted. I was also able to finally jumbo patch myself past kernel 118844-26 by not only editing the patch (the boot-device vs bootpath issue) but also by removing the altbootpath entry from the "eeprom" settings. now why did I have to do that?

After having run format, analyze, etc. and iozone several times on all disks, I get no IDE errors at all now. I wonder what was going on. It appears the disks were all fine.

I have to say the whole boot archive thing throws me a bit, and tossing in SVM with it makes it even more fun! :)

MattSF at 2007-7-7 3:02:58 > top of Java-index,Solaris Operating System,Solaris Essentials - General Technical Questions...