@tombert, thats fine! thanks for the files! I have updated the summary and bug title with the information you provided. Shall provide further updates soon!
** Description changed: Binary package hint: mdadm Creating an mdadm array works fine: mdadm --create /dev/md0 -n 3 -l5 /dev/sdb1 /dev/sdc1 /dev/sdd1 Now when booting the array is assembled correctly. Delete the array and zero-superblock, create new partition and mark as "fd", create the same array again with command above. Now the system tries to assemble a single device into /dev/md_d0 - when other devices are missing. I checked each device with -examine and each reports the same uuid, the same host and the same name. In order to get it working one has to stop the md_d0 and assemble manually: mdadm --stop /dev/md_d0 mdadm --assemble /dev/md0 /dev/sdb1 /dev/sdc1 /dev/sdd1 To overcome this problem one has to remove the homehost from mdadm.conf and assemble the array manually during boot. What helps ist to reinstall the system ... This bug is pretty often found when googling around. Possible hints are udev and dmraid, whereas I already deinstalled dmraid but didn't help. Ubuntu 9.10 Linux 2.6.31-14-generic-pae mdadm 2.6.7.1 + + * The array gets configured when mdadm.conf reflects the array + definitions. But it does not get assemble automatically ** Summary changed: - [->UUIDudev] mdadm fails to assemble raid during boot + [->UUIDudev] mdadm fails to automatically assemble raid during boot (without mdadm.conf) -- [->UUIDudev] mdadm fails to automatically assemble raid during boot (without mdadm.conf) https://bugs.launchpad.net/bugs/541058 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
