> Hmm, well, I'm certainly not positive why it wouldn't boot and I don't have
> the logs in front of me, but I do remember it saying that it couldn't mount
> /dev/md1 and therefore had a panic during boot. My solution was to specify
> the root device as /dev/sda1 instead of the configured /dev/md1 from the
> lilo prompt.
Hmm.... the only time I've seen this message has been when using initrd
with an out of sync /dev/md or when the raidtab in the initrd was bad or
missing. This was without autostart.
Michael
>
> The disk is marked to auto raid start and marked as fd. And, it booted just
> fine until the "dumb" shutdown.
>
> As for a rescue disk I'll put one together. Thanks for the advice.
>
> --Rainer
>
>
> > -----Original Message-----
> > From: Michael Robinton [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, April 03, 2000 8:50 AM
> > To: Rainer Mager
> > Cc: Jakob Ostergaard; [EMAIL PROTECTED]
> > Subject: RE: Raid5 with two failed disks?
> >
> > Whether or not the array is in sync should not make a difference to the
> > boot process. I have both raid1 and raid 5 systems that run root raid and
> > will boot quite nicely and rsync automatically after a "dumb" shutdown
> > that leaves them out of sync.
> >
> > Do you have your kernel built for auto raid start?? and partitions marked
> > "fd" ?
> >
> > You can reconstruct you existing array by booting with a kernel that
> > supports raid and with the raid tools on the rescue system. Do it all the
> > time.
> >
> > Michael
> >
>
