On Mon, 03 Apr 2000, Rainer Mager wrote:
> Hi all,
>
> I think my situation is the same as this "two failed disks" one but I
> haven't been following the thread carefully and I just want to double check.
>
> I have a mirrored RAID-1 setup between 2 disks with no spare disks.
> Inadvertantly the machine got powered down without a proper shutdown
> apparently causing the RAID to become unhappy. It would boot to the point
> where it needed to mount root and then would fail saying that it couldn't
> access /dev/md1 because the two RAID disks were out of sync.
> Anyway, given this situation, how can I rebuild my array? Is all it takes
> is doing another mkraid (given the raidtab is identical to the real setup,
> etc)? If so, since I'm also booting off of raid, how do I do this for the
> boot partition? I can boot up using one of the individual disks (e.g.
> /dev/sda1) instead of the raid disk (/dev/md1), but if I do that will I be
> able to do a mkraid on an in-use partition? If not, how do I resolve this
> (boot from floppy?).
> Finally, is there any way to automate this recovery process. That is, if
> the machine is improperly powered down again, can I have it automatically
> rebuild itself the next time it comes up?
As others already pointed out, this doesn't make sense. The boot sequence uses
the mount command to mount your fs, and mount doesn't know that your md device
is in any way different from other block devices.
Only if the md device doesn't start, the mount program will be unable to
request the kernel to mount the device.
We definitely need log output in order to tell what happened and why.
--
................................................................
: [EMAIL PROTECTED] : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob �stergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
