From: trevor.mclachlan@richemont.com
Date: Tue Feb 10 2004 - 04:31:01 EST
Hi All,
I have an E250 running Solaris 8 and Disksuite 4.2.1 .... c0t0d0 being the
boot disk with s0 being / (all o/s/ installed to this) and s1 is swap.
c0t0d0 is mirrored to c8t0d0. Note: I have only worked here a few weeks and
this was configured a couple of years ago !!
A couple of weeks ago we had the following problem -
c0t0d0 disk failed, causing the machine to reboot. But it got caught in a
boot loop, and kept failing cause c0t0d0 is the boot disk (and I don't
think there is an alernate boot disk configured) ... This machine is
co-located off site. The on-site engineer physically swapped the disks
around, and c0t8d0 became c0t0d0, and with an fsck against / he was able to
boot the machine back up. The old boot disk was now c0t8d0 (and faulty) we
couldn't fix the mirror, so Sun came out, replaced the disk, and I was able
to do a metareplace and it sync'ed up fine and since then everything has
been running ok.
My questions are -
When the boot disk (c0t0d0) failed, why didn't the server stay up and run
off the other disk (c0t8d0) as this is why we have disks mirrored is it not
?
Was it feasible to just swap the disks, and "make" c0t8t0 become the boot
disk (c0t0d0) and reboot and fsck to fix ?
I am now worried that the "new" boot disk does not have a bootblk
installed. Would this be the case after swapping disks ? I am worried the
server won't boot next time I try.
Any feedback would be appreciated and thx in advance.
Regards
Trevor McLachlan
_______________________________________________
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:28:01 EDT