@Thomas, first off, thanks for taking the time to file this report. I think we all want to make sure systems boot in as simple a manner as possible, and this issue does sound important. I'm not really sure what would be run from inside initrd that would change the way upstart boots, as the 'startup' event is emitted quite early on, which starts things rolling nicely. It sounds a bit like maybe this is actually an issue with mountall and how it fsck's the root filesystem. Also its probably worth noting that booting Ubuntu without an initrd is by no means a default configuration, so this may end up in the Wishlist. Given that, can you explain what the benefits of running without an initrd are? Actually here are the exact questions that need answering:
1. what exact steps did you use to boot your system without an initrd 2. what would you expect to happen when the root fs hits its max mount count 3. what actually happens when you've followed all the steps from question 1, and then hit the max mount count? 4. what are the reasons users might want to run without an initrd. @Rolf, thanks very much for assigning yourself and trying to figure out how to reproduce. You may want to read this page: https://wiki.ubuntu.com/Bugs/HowToTriage As you have skipped a few steps that would be required before assigning yourself to the bug. Marking Incomplete pending response from Thomas. Unassigning Rolf, and setting Importance back to Undecided. ** Changed in: upstart (Ubuntu) Importance: High => Undecided ** Changed in: upstart (Ubuntu) Assignee: Rolf Leggewie (r0lf) => (unassigned) ** Changed in: upstart (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/588624 Title: upstart fails to boot without initrd -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
