Hmm...as far as I know you MUST compile in the md support if you want to
have / or /boot useable if they are md/lvm devices.
--
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: austin@xxxxxxxxxxxxxxx
On Wed, 2 May 2001, Seth Mos wrote:
> On Tue, 1 May 2001, Russell Cattelan wrote:
>
> > "Martin K. Petersen" wrote:
> >
> > > >>>>> "Eric" == Eric Sandeen <sandeen@xxxxxxx> writes:
> > >
> > > >> The installation went fine after loading the update disk. However,
> > > >> upon reboot, raidautorun reports "failed to open /dev/md0" which
> > > >> obviously leads to a kernel panic (my / is on md0). Suggestions?
> > >
> > > Eric> Hm... hopefully Martin or Russell can speak to this - I don't
> > > Eric> have any raid machines here, and have not ever tested it...
> > >
> > > Eric> Could this be a devfs thing? Has /dev/md0 moved to /dev/md/0
> > > Eric> perhaps? If devfsd hasn't started, the compatibility links
> > > Eric> won't be there if / isn't even mounted.
> > >
> > > That's probably the case, yes.
> >
> > Wouldn't this be before / is mounted? so it probably doesn't matter if
> >
> > /dev/ is real or devfs.
> >
> > How does the kernel find and mount / if it is an md device? the dev_id
> > is usually
> > part of the lilo boot process but in the md case?
>
> Do you have a initrdimage for inserting the md modules?
> AFAIk they were also modular on redhat kernels.
> I managed to make the server I admin 100Km away unbootable after
> forgetting to compile raid 1 support in :-/
>
> Bye
> Seth
>
|