also sprach Moshe Yudkowsky <[EMAIL PROTECTED]> [2005.05.23.1956 +0200]: > The reason I suspected it is because if mdadm.conf has /dev/md3 as the > device in its ARRAY statement, and I use the notation "mdadm --assemble > /dev/md/3", then mdadm wouldn't start. It couldn't translate between the > two. Since /script in initrd.img had this notation, I thought that if I > moved everything to /dev/md/n style notation, I'd be able to boot -- and I > could.
"mdadm: /dev/md/3 not identified in config file" Is this your error? If yes, then well, tough. I don't think we will fix this anytime soon. I did file a bug about this though. Note that the problem only applies to the mdadm call. You should be able to use any of /dev/md3 or /dev/md/3 to mount the device. Why are you manually calling `mdadm --assemble` anyway? Doesn't the /etc/init.d/mdadm-raid script do everything you need? I need more information or I cannot fix this bug. I need to know exactly when there is a failure assembling RAID devices: at initrd time, or when mdadm-raid gets called...? -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! http://www.vcnet.com/bms/
signature.asc
Description: Digital signature
