Issue is present also moving do mdadm (which is possible for my fake raid since it uses intel metadata).
When it happens, the boot hangs for 1 minute and a half on A start job is running for dev-disk-by... with all disks appearing in turn on the line. After that the machine drops to an emergency prompt. Analyzing the systemd journal shows the corresponding jobs timing out. Interestingly: 1) *all* the items mentioned in /etc/fstab get shown here. Namely, when the issue occurs, the error is shown even for the swap partintion (that is on a plain ssd partition... 2) It is not a problem with /etc/fstab but some race: every few attempts the system succeeds to boot 3) When you get to the emergency prompt all the disks on which systemd hangs appear to be working just fine 4) Removing from the fstab the entries corresponding to stuff on the slower fake raid, the boot starts being reliable (I think) How can I debug this? How can I force systemd to wait before it tries to access the disks? Should I open a bug on systemd? Can someone provide pointers at some systemd documentation that might be releant to this issue? It seems such a complex device that I do not know where to start. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635023 Title: yakkkety boot is erratic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
