For what it's worth I use S/W RAID1 as well and my root is md5.  Using the ARCH provided mkinitrd I have not had any issues with either the default ARCH kernel nor with my custom 2.6.15.4 kernel.  HOWEVER, I do have issues using mkinitramfs (and thus with the archck kernel).  For some reason, with mkinitramfs my system's root partition is seen just fine and my system boots.  However, I also have RAID1 for partitions /home & swap and a RAID0 /files0 (which is an LVM2 volume) and those are not seen and so far I have been unable to activate my LVM volume nor get the other RAID1 volumes to come online so I have remained using mkinitrd until I can sort through this on my box.
RAID_ROOT_ARRAY="md5"
RAID_ROOT_DEVICES="/dev/sda5 /dev/sdb5"


On 3/4/06, Greg Nyce < [EMAIL PROTECTED]> wrote:
First, just upgraded my home machine to Xorg7.  Was expecting to have some issues to work through, esp. as this runs MythTV and LTSP, but it all "just worked".  Very impressive, and kudos to the developers!  Will feel more confident as I do this remotely to my 69 year-old mother's PC (on Arch as well).

Second, question:  I have a server that is running s/w RAID1 on a 2.6.13 kernel.  I am considering moving to the current 2.6.15, but thought I saw something/somewhere about how when using the Initrd that the root has to be on  /dev/md0.  Is that still the case?  I have root on /dev/md2 (md0 is my boot)... am I hosed?  Or can I just specify in the /etc/mkinitrd.conf, like:
RAID_ROOT_ARRAY="md2"
RAID_ROOT_DEVICES="/dev/sda3 /dev/sdb3"

thanks,
Greg

_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch



--
****************
jps
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to