[Bug 126934] Re: mdadm-RAID compromises bootup process
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! ** Changed in: mdadm (Ubuntu) Status: Incomplete => Invalid -- mdadm-RAID compromises bootup process https://bugs.launchpad.net/bugs/126934 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 126934] Re: mdadm-RAID compromises bootup process
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance. ** Changed in: mdadm (Ubuntu) Status: New => Incomplete -- mdadm-RAID compromises bootup process https://bugs.launchpad.net/bugs/126934 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 126934] Re: mdadm-RAID compromises bootup process
Comparing a fresh install with a alternate-desktop installed as single0drive, upgraded to raid, then 6.10-7.04: #1. Both systems suffer from bug Bug #108971. Message "mdadm : No devices listed in conf file were found" on boot-up right after "Loading, please wait..." This is fixed by adding "/sbin/udevsettle" to the end of /usr/share/initramfs-tools/scripts/init-premount/udev, then issue command "update-initramfs -u -k `uname -r`" and reboot #2. This starts raid before raid is supposed to be started, and the upgraded system therefore gives an error message: Begin: Assembling MD array /dev/md1 ... mdadm: device /dev/md1 already active - cannot assemble it Failure: failed to start /dev/md1 It is unclear if this has any functional impact. The root cause is that the /conf/md.conf file in the RAM file system image initrd.img-... contains MD_DEVS='/dev/md1' instead of MD_DEVS='all' which is the case for fresh install (The image can be examined by "cpio -i https://bugs.launchpad.net/bugs/126934 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
