*** This bug is a duplicate of bug 1902103 ***
https://bugs.launchpad.net/bugs/1902103
We must honor MNT_PASS.
The actual bug is that many things do not set it to 1 by default as they should
have.
I.e. bits in curtin, maas, subiquity, cloud-images.
It is correctly set to 1 on ubiquity desktop images and d-i based installs.
So this bug is a duplicate of https://bugs.launchpad.net/ubuntu/+source
/livecd-rootfs/+bug/1902103
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Won't Fix
** This bug has been marked a duplicate of bug 1902103
Ensure default fstab options are sane and consistent across all images
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1917780
Title:
initramfs-tools does not include fsck in initrd if mount pass is 0
Status in initramfs-tools package in Ubuntu:
Won't Fix
Bug description:
initramfs-tools does not include fsck in initrd if MNT_PASS equals
zero in the fstab entries.
This has lead to the following situation :
when dropping to initramfs shell during boot due to fs errors, we are not
able to run fsck manually
because it is not included in initrd.
fsck should be included regardless of the MNT_PASS value.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
