I'm experiencing the same thing. With a full snapshot and a disabled splash screen, I get an error message telling me that a command has timeouted (lvscan, IIRC), and it had been terminated. I removed the snapshot and it booted all right.
I think terminating boot commands using a predefined timeout is a double-edged sword - it does help if a program trying to access an unessential resource has hanged, but it does prevent boots on slow systems - examples would include lvm snapshots which slow the boot process quite a lot, and failing hardware. I've had the same issue when I was trying to boot from a hard drive that was failing. The boot never succeeded because initrd decided to kill everything. Wouldn't it make more sense if a more intelligent approach is used? E.g. run the tools in parallel repeatedly until the root is found, or re-run the killed ones if the root wasn't found or something? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/360237 Title: cannot boot root on lvm2 with (largish) snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/360237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
