[Bug 1912835] Re: ESP should be fscked
Dimitri John Ledkov
1912835 at bugs.launchpad.net
Tue Feb 9 20:50:38 UTC 2021
>From https://launchpad.net/~xnox/+livefs/ubuntu/xenial/any/+build/259781
downloading the livecd.ubuntu-cpc.uefi1.img image.
mounting p1 i can see that:
$ cat /mnt/etc/fstab
LABEL=cloudimg-rootfs / ext4 defaults 0 1
LABEL=UEFI /boot/efi vfat defaults 0 1
fsck will be performed
$ file /mnt/usr/bin/systemd-detect-virt
/mnt/usr/bin/systemd-detect-virt: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=48194abca8f0a3e7b9e698e2dcf114e787057a00, stripped
systemd-detect-virt exists. Although the bug in question would not be
triggered on any xenial images.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1912835
Title:
ESP should be fscked
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in livecd-rootfs source package in Xenial:
Fix Committed
Status in livecd-rootfs source package in Bionic:
Fix Committed
Status in livecd-rootfs source package in Focal:
Fix Committed
Status in livecd-rootfs source package in Groovy:
Fix Committed
Bug description:
[Impact]
* ESP can be not clean, thus failing to mount on boot.
* fsck should be enabled for ESP partition.
[Test Case]
* $ systemctl status systemd-fsck*.service
On boot, that should produce status for two drives, the one with
short uuid should be the one mounted as /ESP
[Where problems could occur]
* The change will affect only newly deployed instances. Old instances
will have to correct this in fstab themselves.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912835/+subscriptions
More information about the foundations-bugs
mailing list