Bug#1071420: linux-image-6.8.9-1-amd64: cannot mount btrfs root partition
Thanks Bastian,
I was able to reproduce this only with dracut, using a virtual machine
I tried both dracut and initramfs.
There seems to be a different problem at play indeed:
mag 22 21:44:12 rosebud systemd-journald[358]: Journal started
mag 22 21:44:12 rosebud systemd-journald[358]: Runtime Journal
(/run/log/journal/022ce7df193548d6ab2007cb814f1d04) is 8.0M, max
640.1M, 632.1M free.
mag 22 21:44:12 rosebud systemd-modules-load[359]: Inserted module
'msr'
mag 22 21:44:12 rosebud systemd-modules-load[359]: Inserted module
'bfq'
mag 22 21:44:12 rosebud dracut-cmdline[387]: dracut-dracut-060+5-8
mag 22 21:44:12 rosebud dracut-cmdline[387]: Using kernel command line
parameters: rd.driver.pre=btrfs rd.luks.uuid=luks-13bd3015-55c4-40d3-
a805-4d5f2b90ac1f root=/dev/mapper/root rootfstype=btrfs
rootflags=rw,noatime,compress=zstd:3,ssd,space_cache=v2,subvolid=608,su
bvol=/rootfs,subvol=rootfs BOOT_IMAGE=/vmlinuz-6.8.9-amd64
root=UUID=6fd6a999-b02d-4856-8412-64dff369d45f ro
rootflags=subvol=rootfs rd.luks.name=13bd3015-55c4-40d3-a805-
4d5f2b90ac1f=root rd.luks.allow-discards quiet splash
mag 22 21:44:12 rosebud systemd[1]: Starting systemd-tmpfiles-
setup.service - Create Volatile Files and Directories...
mag 22 21:44:12 rosebud systemd[1]: Started systemd-journald.service -
Journal Service.
mag 22 21:44:12 rosebud dracut-cmdline[444]:
//lib/dracut/hooks/cmdline/00-parse-root.sh: line 28:
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-
uuid\x2f6fd6a999-b02d-4856-8412-64dff369d45f.sh: Read-only file system
mag 22 21:44:12 rosebud dracut-cmdline[387]:
//lib/dracut/hooks/cmdline/00-parse-root.sh: line 38:
/lib/dracut/hooks/emergency/80-\x2fdev\x2fdisk\x2fby-uuid\x2f6fd6a999-
b02d-4856-8412-64dff369d45f.sh: Read-only file system
mag 22 21:44:12 rosebud systemd[1]: Finished systemd-tmpfiles-
setup.service - Create Volatile Files and Directories.
mag 22 21:44:12 rosebud systemd-escape[471]: Input 'root' is not an
absolute file system path, escaping is likely not going to be
reversible.
mag 22 21:44:12 rosebud dracut-cmdline[387]:
//lib/dracut/hooks/cmdline/30-parse-crypt.sh: line 169:
/lib/dracut/hooks/initqueue/finished/90-crypt.sh: Read-only file system
mag 22 21:44:12 rosebud dracut-cmdline[387]:
//lib/dracut/hooks/cmdline/30-parse-crypt.sh: line 126:
/lib/dracut/hooks/emergency/90-crypt.sh: Read-only file system
mag 22 21:44:12 rosebud systemd[1]: Finished dracut-cmdline.service -
dracut cmdline hook.
mag 22 21:44:12 rosebud systemd[1]: Starting dracut-pre-udev.service -
dracut pre-udev hook...
...
mag 22 21:44:16 rosebud dracut-initqueue[752]: rm: cannot remove
'/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-
uuid\x2f09CB-D388.sh': Read-only file system
mag 22 21:44:16 rosebud dracut-initqueue[754]: rm: cannot remove
'/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-
uuid\x2f469f76d8-6293-4fd4-ad46-180c7bd186f4.sh': Read-only file system
I apologize for the confusion.
I kindly ask you to close this bug as invalid.
Thanks again,
Matteo
Il giorno dom, 19/05/2024 alle 21.24 +0200, Bastian Blank ha scritto:
> Control: tags -1 moreinfo
> Control: severity -1 important
>
> On Sat, May 18, 2024 at 10:25:14PM +0200, Matteo Settenvini wrote:
> > booting kernel 6.8.9-1 with dracut, systemd, and btrfs as the root
> > device fails
> > to mount the root partition. I just tried the kernel from sid and
> > it seems indeed \
> > affected. The 6.7 kernel from trixie is instead booting fine even
> > after
> > regenerating all initrds.
>
> Please provide proper error messages.
>
> Also dracut is not the default option, so please check with
> initramfs-tools as well.
>
> Bastian
Reply to: