RAID/Root Update

[Matthew Carpenter]

Well folks, the good news is this:

By using the SuSE-provided mkinitrd I was able to make it all work correctly.
The trick is to tell mkinitrd where the *new* root filesystem will be.  It 
does a lot of checks and automation based on whether LVM and RAID are 
involved in the root partition.  For example, I have my new filesystem 
mounted on /media/floppy/  (seldom in use so it's become general purpose 
mount-point).  The command then is:

# mkinitrd -d /media/floppy

Ta da!  mkinitrd is intelligent enough to validate that the proposed 
filesystem is not only on a RAID device but also an LV.  The appropriate 
modules, apps, and boot script are then packaged into the 
correct /boot/initrd, ready for boot.  The reason it didn't work for me was I 
simply called "mkinitrd" so it inspected my current root filesystem, which 
was still /dev/hda1.

Thanks for all the input on this one.  I hope it's been informative for you as 
it has been for me!

On Wednesday 09 February 2005 01:12 am, Matthew Carpenter wrote:
> Well, I'm not willing to settle for it just yet, but by removing the LVM
> from /dev/md0 and simply using it as one filesystem I'm able to boot ok
> off the md* devices...  Now, just need to figure out the trick to
> telling the kernel to boot from LVM *on* md.  So far, I can do either,
> but not both.
>
> hopefully more good news to come.
>
> _______________________________________________
> Linux-users mailing list
> Linux-users at linux-sxs.org
> http://mail.linux-sxs.org/cgi-bin/mailman/listinfo/linux-users
>
> Need to chat further on this subject? Check out #linux-users on
> irc.linux-sxs.org !

-- 
Matthew Carpenter 
matt at eisgr.com                          http://www.eisgr.com/

Enterprise Information Systems
* Network Server Appliances
* Security Consulting, Incident Handling & Forensics
* Network Consulting, Integration & Support
* Web Integration and E-Business