2011/2/5, martin f krafft <madd...@debian.org>: > also sprach Roel Brook <rainmake...@gmail.com> [2011.02.04.0205 +0100]: >> It complains "cannot find /proc/mdstat. If I modprobe the md module from >> the prompt, and then manually run /scripts/local-top/mdadm, it does >> assemble the array. >> >> I'm just not really sure where to tell local-top to load this module... > > It should do so automatically. Please uploade your initrd file to > a downloadable location (do not send it by mail), or upload it to > ftp://ftp.madduck.net/incoming. > > -- > .''`. martin f. krafft <madduck@d.o> Related projects: > : :' : proud Debian developer http://debiansystem.info > `. `'` http://people.debian.org/~madduck http://vcs-pkg.org > `- Debian - when you have better things to do than fixing systems > > "one should never allow one's mind > and one's foot to wander at the same time." > -- edward perkins (yes, the librarian) >
Thank you, and sorry for the late response. After the latest aptitude dist-upgrade, I too got hit with bug #56782, which caused me to investigate the entire boot sequence again. After a couple of changes, update-grub2 and friends do not tell me "no such file or directory", but just work as expected without error. This also seems to be causing the RAID array to be assembled correctly on boot (though I think it too got updated during the process). Without the DEVICES line in the mdadm.conf and with a correct and working devices.map, everything works. Thanks for your help. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
