From: Travis Haas (thaas@topcoder.com)
Date: Thu Sep 02 2004 - 09:11:14 EDT
Thanks to everyone who responded. I had to run fsck on the disk before
it would mount, as the Super Block was bad. Unfortunately, I wasn't
able to recover any data on the drive as after the fsck ran I only had
lost+found on the disk. I was able to mount the original bad drive in a
different Sun box and get at the data, so it wasn't a total loss, other
than having to reinstall Solaris.
Most suggestions were along the same lines for booting disk1:
>From Chad Truhn:
Try booting off of the Solaris cdrom using 'boot cdrom -s'. Once it
boots mount the drive 'mount -F ufs /dev/dsk/c#t#d#s0' and cd to the
drive and change the /etc/vfstab back from the metadevices to the simple
partition slices. Then edit the /etc/system file and delete everything
that says 'forceload'. Then unmount, shutdown, and boot off of that.
It may also still be trying to boot off of disk 0. Try switching the
drives so that disk 1 is in the disk 0 slot. If you have any questions
about this feel free to ask...
Thanks again everybody.
Travis
///////////
Original Message:
From: Travis Haas
Sent: Tuesday, August 31, 2004 3:31 PM
To: 'sunmanagers@sunmanagers.org'
Subject:
Server: Solaris 7, disksuite, mirrored system drives.
disk0 fails, I reboot with disk1. I delete the wrong database replica
(deleted the one on disk1), reboot, the system won't come up as it says
there is not a bootable disk.
Is there a way I can recover disk1?
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:29:23 EDT