OK, here are the result of some more tests with mdadm_2.5.6-7ubuntu4: * my first boot went fine, allowing me to get your advice. * the second boot hanged, so I waited for a while. All my devices were here, both in /dev and in /proc/partitions The RAID array was assemble with 3 devices (out of 4) but not started (i.e. not degraded) running "/scripts/local-top/mdadm from udev" did not work, the screen was filled with error message: "mdadm: SET_ARRAY_INFO failed for /dev/md0: Device or ressource busy" I could stop it only using the sysreq, which took me back to the initramfs shell, with the raid array completely stopped. There running the same command again assembled the array correctly. [off topic] I could not leave the shell and continue booting, It took me back to this shell every time, saying: "can't access tty; job control turned off" [/off topic] * The third boot hanged also. The array was assembled with one drive only (thus it could not even have started in degraded mode). I tried running "mdadm -S /dev/md0" before doing anything else. After this, running "/scripts/local-top/mdadm from-udev" assembled the array properly
[off topic] But I still could not continue the boot. The next 4 boot did also hang (but I did not wait). Then it accepted to boot again [/off topic] -- initramfs script: race condition between sata and md https://launchpad.net/bugs/75681 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
