[Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.139ubuntu3

---------------
initramfs-tools (0.139ubuntu3) hirsute; urgency=medium

  * hooks/fsck: always include fsck binaries irrespective of PASSNO value,
    otherwise initrds fail to mount rootfs and have no ability to fix the
    rootfs. LP: #1917780

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Wed, 24 Mar 2021 15:21:50
+0000

** Changed in: initramfs-tools (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1917780

Title:
  initramfs-tools does not include fsck binaries in the initrd if all
  mount pass are 0

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * 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.

  [Test Plan]

   * change /etc/fstab with PASSNO set to 0 for all entries
   * update-initramfs -u
   * lsinitramfs that is just generated
   * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist

  
  [Where problems could occur]

   * The initramfs size will increase slightly upon upgrade, for the
  same initramfs-tools default options & kernel. However, one can
  control and remove fsck binaries (or include more of them) by setting
  FSTYPE variable in the initramfs settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+subscriptions