Uploaded image for project: 'Funtoo Linux'
  1. Funtoo Linux
  2. FL-11913

cannot mount ext4 rootfs during boot if created with recent `e2fsprogs`

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium (Ebuild) Medium (Ebuild)
    • None
    • None
    • Hide
      New install initially constructed while booted from sysresccd (https://systemrescuecd.org) and using the version of e2fsprogs present there requires manual intervention at the initramfs shell to load the `crc32c-intel` (or similar, depending on platform) module before the ext4 rootfs can be mounted.
      Show
      New install initially constructed while booted from sysresccd ( https://systemrescuecd.org ) and using the version of e2fsprogs present there requires manual intervention at the initramfs shell to load the `crc32c-intel` (or similar, depending on platform) module before the ext4 rootfs can be mounted.
    • Changes in e2fsprogs upstream have changed its behavior.

      At some point, `mkfs.ext4` has changed to include `-O metadata_csum` in the default options.  Our kernel builds `crc32c` as a module and at least for people still using `genkernel` while `ramdisk` doesn't support `lvm` rootfs, the module isn't loaded by the initramfs script.  I've fixed this problem where it occurs by building that module into the kernel and using a custom config.  We can fix it for everyone that way; so I propose to test it in harvester.

            cuantar cuantar
            cuantar cuantar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: