Bug#1099655: initramfs-tools 146 generates incorrect initramfs : does not boot, does not find root fs

[Ben Hutchings <ben@decadent.org.uk>]

On Thu, 2025-03-27 at 16:46 +0100, Eric Valette wrote:
> On 25/03/2025 01:12, Ben Hutchings wrote:
> > 
> > Hi Eric,
> 
> > - The *complete* kernel config that you were using (before enabling
> > CONFIG_MODULE_DECOMPRESS).
> 
> I switched tp 6.12.20 but same problem. Config attached.
> > 
> > - All the error messages from the initramfs when using this kernel and
> > initramfs-tools 0.146.  (A photograph of the screen is fine, if it's
> > readable.)
> 
> Photo attached
> 
> 
> No module loaded at all.

Indeed.  But the root device is there anyway, presumably because the
nvme driver is built-in.  So I think the "No such device" error is
actually because the *filesystem* module fails to load.

So I have more questions:

- Your kernel config has ext4 enabled as a module.  Is that the root
  filesystem type?
- What does the command "/usr/lib/klibc/bin/fstype /dev/nvme0n1p5"
  print?
- Using the bad initramfs, in the rescue shell:
  - What does "echo $ROOTFSTYPE" print?
  - What does "cat /proc/filesystems" print?
  - What does "modprobe fs-ext4" print, if anything?
  - If you then exit the rescue shell, does the boot process succeed?

Ben.

-- 
Ben Hutchings
If at first you don't succeed, you're doing about average.

Attachment: signature.asc
Description: This is a digitally signed message part