[ISSUE] dracut/initramfs: 6.6.54_1 fails to mount root partition

[ISSUE] dracut/initramfs: 6.6.54_1 fails to mount root partition

[dezifit]

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

New issue by dezifit on void-packages repository

https://github.com/void-linux/void-packages/issues/52546

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.54_1 x86_64 libc

### Package(s) Affected

linux-6.6_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

After updating the kernel from 6.6.51_1 to 6.6.54_1 the systems fails to mount the root partition and boots into the recovery console.

 `/run/initrunfs/rdsosreport.txt` shows:
 `dracut Warning: Failed to mount -t jfs -o ro,ro /dev/disk/ny-uuid/<correct uuid> /sysroot`

Manual invocation of `fsck /dev/sda1` gives `Filesystem is clean.`, but manual mount with `mkdir -p /mnt; mount /dev/sda1 /mnt` fails with:
`mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda1`

Choosing the last working kernel `6.6.51` in grub boots the (grub legacy bios) system without any issue. I have already recreated the initramfs with `dracut --force --kver $(uname --kernel-release)`, but it fails with the same same error. Are there JFS related changes in the kernel configuration? Any ideas?

### Expected behaviour

Regular system boot.

### Actual behaviour

Can't mount root partition.

### Steps to reproduce

100% reproducible on the failing system.

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[dezifit]

[-- Attachment #1: Type: text/plain, Size: 708 bytes --]

New comment by dezifit on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2399843162

Comment:
Some more testing shows that the dracut-emergency environment is able to mount another JFS partition just fine. Only the root partition fails, even after a forced filesystem check, which just confirms a valid superblock and clean filesystem.

I tried with kernel 6.11.2 (also fails to boot, same symptom), did a memcheck (passed without error) and finally switched back to the still working kernel 6.6.51 after running out of ideas.

It looks like a strange issue of the specific root partition, therefore I will close this ticket if there is no participation.

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[witseid]

[-- Attachment #1: Type: text/plain, Size: 274 bytes --]

New comment by witseid on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2402163200

Comment:
I had similar problems with booting the 6.6.54 kernel, not sure what that might be related to. I had to go back to version 6.6.51.

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[Katnjia]

[-- Attachment #1: Type: text/plain, Size: 291 bytes --]

New comment by Katnjia on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2403285537

Comment:
I can confirm this issue. Broke my system with ZFS root, and switching over to mkinitcpio generated initramfs images that works with newer kernels.

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[Katnjia]

[-- Attachment #1: Type: text/plain, Size: 376 bytes --]

New comment by Katnjia on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2403285537

Comment:
I can confirm this is an issue with Dracut and kernel 6.6_54 and up. Broke my system with ZFS root where it couldn't find the root partition, and switching over to mkinitcpio generated initramfs images that works with newer kernels.

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[dkwo]

[-- Attachment #1: Type: text/plain, Size: 229 bytes --]

New comment by dkwo on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2403387206

Comment:
One option could be to try other initramfs: as suggested mkinitcpio, or maybe tinyramfs?

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 250 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2403530748

Comment:
are you sure it wasn't just a single bad initramfs? `xbps-reconfigure -f linux6.6` will regenerate it

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[dezifit]

[-- Attachment #1: Type: text/plain, Size: 615 bytes --]

New comment by dezifit on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2407175119

Comment:
I regenerated the initrafs with `xbps-reconfigure` now again (in addition to to direct dracut invocation before). Still fails to boot.

This system has 3 partitions:
* root (jfs, sda1) - mount of clean filesystem fails
* home (jfs, sda2) - mount of clean filesystem fails
* data (jfs, sda4) - mounts just fine

[Katnjia](https://github.com/Katnjia) has issues with ZFS root,  
[witseid](https://github.com/witseid), which filesystem type is involved in your case?

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[witseid]

[-- Attachment #1: Type: text/plain, Size: 387 bytes --]

New comment by witseid on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2407209035

Comment:
> I can confirm this is an issue with Dracut and kernel 6.6_54 and up. Broke my system with ZFS root where it couldn't find the root partition, and switching over to mkinitcpio generated initramfs images that works with newer kernels.

btrfs

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[witseid]

[-- Attachment #1: Type: text/plain, Size: 229 bytes --]

New comment by witseid on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2407216209

Comment:
I get stuck on displaying the UEFI logo when trying to boot from a linux6.6.64 kernel

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[witseid]

[-- Attachment #1: Type: text/plain, Size: 229 bytes --]

New comment by witseid on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2407216209

Comment:
I get stuck on displaying the UEFI logo when trying to boot from a linux6.6.54 kernel

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[witseid]

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

New comment by witseid on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2407209035

Comment:
> I regenerated the initrafs with `xbps-reconfigure` now again (in addition to to direct dracut invocation before). Still fails to boot.
> 
> This system has 3 partitions:
> 
> * root (jfs, sda1) - mount of clean filesystem fails
> * home (jfs, sda2) - mount of clean filesystem fails
> * data (jfs, sda4) - mounts just fine
> 
> [Katnjia](https://github.com/Katnjia) has issues with ZFS root, [witseid](https://github.com/witseid), which filesystem type is involved in your case?

btrfs

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 329 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2407588149

Comment:
can you compare the contents of the initramfs? `diff -u <(sudo lsinitrd /boot/initramfs-6.6.x_1.img) <(sudo lsinitrd /boot/initramfs-6.6.54_1.img)` (this syntax requires bash/zsh) 

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[dezifit]

[-- Attachment #1: Type: text/plain, Size: 215 bytes --]

New comment by dezifit on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2407647940

Comment:
Losts of differences because of date/time, see attached `lsinitrd.zip`.

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 168 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2407665682

Comment:
attachment missing?

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[dezifit]

[-- Attachment #1: Type: text/plain, Size: 250 bytes --]

New comment by dezifit on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2407687315

Comment:
> attachment missing?

[lsinitrd.zip](https://github.com/user-attachments/files/17344859/lsinitrd.zip)

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 210 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2407692774

Comment:
can you also post the lsinitrd of each version by themselves?

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[dezifit]

[-- Attachment #1: Type: text/plain, Size: 296 bytes --]

New comment by dezifit on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2407708798

Comment:
> can you also post the lsinitrd of each version by themselves?

[lsinitrd-2.zip](https://github.com/user-attachments/files/17345007/lsinitrd-2.zip)

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[classabbyamp]

[-- Attachment #1: Type: text/plain, Size: 249 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2407725397

Comment:
ok, removing obvious differences (timestamp, kernel version), i don't see anything significant there

Re: dracut/initramfs: 6.6.54_1 fails to mount root partition

[dezifit]

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

New comment by dezifit on void-packages repository

https://github.com/void-linux/void-packages/issues/52546#issuecomment-2431302757

Comment:
I've created a JFS specific kernel [ticket](https://bugzilla.kernel.org/show_bug.cgi?id=219417) and received a patch which fixes the problem for me. As far as I'm concerned this ticket can be closed now as my issue is unrelated to Void Linux.