That's not very helpful if the damn thing won't come up even in single
user mode. ;) I could use the rescue mode from the CD, but I'd rather
everything work right w/o having to do that.

On Mon, 2002-09-30 at 04:15, Thomas Backlund wrote:
> From: "Wes Kurdziolek" <[EMAIL PROTECTED]>
> > On Sun, 2002-09-29 at 22:43, Bruno Prior wrote:
> > >  > Basically I've got a ASUS A7V133 RAID m/b with 1G ram, althon 1500XP
> and
> > >  > two 40G
> > >  > 7200rpm disks. One disk on the main  controller, the other on the
> > >  > onboard promise controller.
> > >  >
> > >  > Booted mandrake 9.0 disk #1, partitioned as follows:
> > >  >
> > >  > /dev/hda1    256M    -    /boot [ext2]
> > >  > /dev/hda2    24G    -    added to md0
> > >  > /dev/hda3    1G        swap
> > >  > /dev/hds4    reat    -    addes to md1
> > >  >
> > >  > /dev/hde1    256M    -    /tmp [reiserfs]
> > >  > /dev/hde2    24G    -    added to md0
> > >  > /dev/hde3    1G        swap
> > >  > /dev/hde4    reat    -    addes to md1
> > >  >
> > >  > md0 is mode 0    /
> > >  > md1 is mode 1    /home
> > >  >
> > >  > Installed mandrake, went fine, rebooted, failed !
> >
> > <Snip incredibly long instructions>
> >
> > When I did an MDK 9.0 install that resembled this (ext3 /boot, RAID-0 /,
> > /usr, /usr/local, /var/, and /tmp -- yes, performance is critical), the
> > system failed to come up after rebooting b/c the raid0 module was not
> > included in the initrd and/or not loaded by the initrd's linuxrc script
> > therefore / couldn't be mounted. I believe this is a simple fix that
> > involves checking to see if / is a software RAID volume, including the
> > correct module in the initrd, and loading it in the initrd's linuxrc. I
> > will submit a patch if someone can tell me if this is part of mdkinst or
> > mkinitrd that is broken.
> >
> 
> Have you tried to recreate the initrd:
> mkinitrd /boot/initrd-2.4.19-16mdk.img  2.4.19-16mdk
> (according to docs, it should be able to recognize all needed modules)
> 
> if not...
> 
> mkinitrd --with=raid0 /boot/initrd-2.4.19-16mdk.img  2.4.19-16mdk
> 
> dont forget to rerun lilo after you have made the new initrd,
> or it won't be mapped correctly...
> 
> Thomas
> 
> 
> 
> 
> *** Tämä viesti on VirusTarkistettu INRITEL OY:n postipalvelimella!! *** 
> 


Reply via email to