Now imagine what happens when sda5 is mounted "behind my back" on /boot and a new kernel is installed by the Software Updater: the new kernel ends up on sda5 and the /vmlinuz and /initrd.img "system" symlinks point the new files. On a reboot Grub does not mount sda5: the "system" symlinks point to non-existing files and Grub fails ...
The /var/log/messages file as provided shows that systemd mounts sda5 on /boot and I really cannot think of a reason for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691158 Title: systemd mounts efi partition, but /etc/fstab says "noauto" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1691158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
