Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #81336
| From | hastalavista_debian@murena.io |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#1059518: initramfs-tools-core: mkinitramfs with `MODULES=most` doesn't correctly identify dependent modules, caused BIOS-installed system to fail booting on btrfs rootfs with xxhash checksum |
| Date | 2023-12-27 13:50 +0100 |
| Message-ID | <HPBwd-gsVg-7@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Package: initramfs-tools-core Version: 0.142 Severity: important mkinitramfs fails to detect that kernel module `xxhash_generic` should be installed to init ramdisk, when the rootfs is on a btrfs filesystem with checksum algorithm xxhash, and the disk partition table is msdos. This resulted in the system being unbootable because the init ramdisk lacks kernel xxhash support: BTRFS info (device sda2): first mount of filesystem fs-uuid BTRFS error (device sda2): error allocating xxhash64 hash for checksum BTRFS error (device sda2): open_ctree failed mount: mounting /dev/sda2 on /root failed: No such file or directory Failed to mount /dev/sda2 as root filesystem. Busybox v1.35.0 (Debian 1:1.35.0-4+b3) built-in shell (ash) (Omitted) After I added `xxhash_generic` to `/etc/initramfs-tools/modules` and regenerated the init ramdisk the system booted without issue. UEFI-installed system is unaffected (in fact I have been using btrfs rootfs with xxhash as checksum alg on UEFI-only machines for almost a year so this came as a big surprise when I found that it doesn't even boot), probably due to xxhash module being marked as a dependency of another thing? I would also like to propose that we add a (debug) option to include all available kernel modules in init ramdisk, which may help debug issues like this in the future. For the debugging process I went through see: https://paste.debian.net/1302284/ if anyone is interested. -- System Information: Debian Release: 12.4 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-15-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages initramfs-tools-core depends on: ii coreutils 9.1-1 ii cpio 2.13+dfsg-7.1 ii e2fsprogs 1.47.0-2 ii klibc-utils 2.0.12-1 ii kmod 30+20221128-1 ii logsave 1.47.0-2 ii udev 252.19-1~deb12u1 Versions of packages initramfs-tools-core recommends: ii busybox-static [busybox] 1:1.35.0-4+b3 ii zstd 1.5.4+dfsg2-5 Versions of packages initramfs-tools-core suggests: pn bash-completion <none> -- no debconf information
Back to linux.debian.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Bug#1059518: initramfs-tools-core: mkinitramfs with `MODULES=most` doesn't correctly identify dependent modules, caused BIOS-installed system to fail booting on btrfs rootfs with xxhash checksum hastalavista_debian@murena.io - 2023-12-27 13:50 +0100 Bug#1059518: initramfs-tools-core: mkinitramfs with `MODULES=most` doesn't correctly identify dependent modules, caused BIOS-installed system to fail booting on btrfs rootfs with xxhash checksum Ben Hutchings <ben@decadent.org.uk> - 2025-03-02 16:30 +0100 Processed: Re: initramfs-tools-core: mkinitramfs with `MODULES=most` doesn't correctly identify dependent modules, caused BIOS-installed system to fail booting on btrfs rootfs with xxhash checksum "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-03-02 16:30 +0100
csiph-web