Hi, Tim. I ran into this issue a few days ago on a local server where I'd made an fstab mistake. The behavior seems un-changed from previous observations (drops to the same recovery console). I believe this would still result in an un-bootable cloud VM.
For those who are experiencing the issue in the cloud, I did find a workaround. It's a hassle but it allows the VM to work again. 1. Shut down the VM. 2. Detach the system volume from the VM. 3. Attach the system volume to a different VM as a secondary volume. Mount it. 4. Log into the other VM and edit fstab on the mounted secondary volume. 5. Unmount and detach the secondary volume from the other VM. 6. Re-attach the volume to the original VM as its system volume. 7. Boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463120 Title: Failure to boot if fstab disk mounts fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
