Hi, as I see it, #1334699 is the bug producing the symptoms described in the initial post. Because of that, the fixes seem somewhat arbitrary (due to many causes showing the same symptoms). Nastily hides true problems.
In my case, the underlying issue also was that a device could not be found (see https://serverfault.com/a/594833). /boot/grub/grub.cfg showed in the cmdline root=/dev/md0p2 (the system was set up in a live environment where in a script /dev/md0 was hard- coded as raid device). Removing the quiet parameter allowed to glance mentions of md127 prior to entering the infinite loop. After changing that to the proper form of root=/dev/disk/by-id/yadda- yadda, the system came up just fine. Is there an issue for trying to reliably set the root parameter? I would expected it to be most useful to always use UUIDs here. PS: WTF. Tentative first post. Was unable to find any info on community rules, best practices, etc. Hope this comment helps someone out there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335642 Title: mdadm runs into infinite loop and prevents initrd/initramfs phase to finish on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1335642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
