Hello Eric, Eric Fournie [2015-04-27 11:15 -0000]: > OK to put the bug to "Won't fix", but I would be happy to understand why > upstart was being able to boot although the uuid of the / partition was > incorrect.
I'm not entirely familiar with the details of mountall; but it looks like it just ignored the fstab entry for the root partition in this case, together with all of its options, and merely made the root partition read-write. So if you have multiple installations on your system, you could end up booting the wrong one in the worst case. Also, having a wrong UUID in fstab means that you could never rebuild your initramfs, as that would propagate the wrong UUID there. I actually wonder how your system managed to boot like that before? Every other package in -updates or -security triggers an initramfs update, after all.. Thanks, Martin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448865 Title: does not boot with broken UUIDs in fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448865/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
