On Thu, 2 Feb 2006, dean gaudet wrote: > i've never looked at yaird in detail -- but you can probably use > initramfs-tools instead of yaird... i take it all back... i just tried initramfs-tools and it failed to boot my system properly... whereas yaird almost got everything right. the main thing i'd say yaird is doing wrong is that it is specifying the root raid devices explicitly rather than allowing mdadm to scan the partitions list and assemble by UUID... maybe try the patch below on your yaird configuration and then run: dpkg-reconfigure linux-image-`uname -r` which will rebuild your initrd with this change... then see if it survives your boot testing. -dean p.s. this patch has been submitted to debian bugdb... --- /etc/yaird/Templates.cfg 2006/02/03 02:44:49 1.1 +++ /etc/yaird/Templates.cfg 2006/02/03 02:46:15 @@ -299,8 +299,7 @@ SCRIPT "/init" BEGIN !mknod <TMPL_VAR NAME=target> b <TMPL_VAR NAME=major> <TMPL_VAR NAME=minor> - !mdadm --assemble <TMPL_VAR NAME=target> --uuid <TMPL_VAR NAME=uuid> \ - ! <TMPL_LOOP NAME=components> <TMPL_VAR NAME=dev></TMPL_LOOP> + !mdadm -Ac partitions <TMPL_VAR NAME=target> --uuid <TMPL_VAR NAME=uuid> END SCRIPT END TEMPLATE - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
