[This is a total showstopper for everyone that we are trying to hard to encourage to use Linux. Once any of those hit by this, will never ever come back. We should have another category for this type of bugs. But that gets me off-topic. I better file an RFE for this.]
The situation shows - aside from the bug as such - a serious design flaw, that must never happen: It is a bad sequence error (in the sense of IEEE denomination of flaws), when a bootable state is removed well before the new (upgraded) bootable state is reached. And this is what we see here. I am hit by this and can vouch for this serious programmer's (designer's) error. During dpkg, some configuration is removed rather early on in the upgrade process that messes with the ability to mount the root partition rw. Any interruption, by power outage, battery drained, or just the user not wanting to wait, will leave / in an unmountable state. And the install becomes a write-off, to almost any user. That is just plain dead wrong. Before the setting for any previous bootable state can be removed, the new state must be ready. The transition between the two states should ideally be an atomic one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/753853 Title: [natty] The disc drive for / is not ready yet or not present -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
