Closed DrRac27 closed 1 year ago
The btrfs module is not built in, but rather as a module.
Try boot to another Linux install, mount root to /mnt and boot to /mnt/boot. Chroot in, add 'btrfs' into list of modules in /etc/mkinitcpio.conf and regenerate initramfs.
This is nothing that changed so I didn't think it could cause the problem. And in fact all that was necessary was to regenerate the initramfs. Maybe my -Syu
failed? It is working again.
I am a bit confused because I checked my /etc/mkinitcpio.conf
and the modules array is empty and it works anyways?
Steps to reproduce
I have been using the same install of arch for a long time. I used FDE + btrfs to install it and until now everything worked but now i compiled the new kernel and the new u-boot (uboot-pinephone-2023.01-1-aarch64.pkg.tar.xz), made a full update and now it boots into an emergency shell with the error message:
mount: /new_root: unknown filesystem type 'btrfs'.
Did you disable btrfs in the u-boot config?(I checked kernel & u-boot -> you didn't. The commits shouldn't have anything to do with btrfs....)Expected behavior
Boot as every time before.
Actual behavior
Boots into emergency shell. Doesn't open a osk so I can't type and find out more because I have a unpatched UBPorts Edition where the USB data pins have to be soldered somehow (didn't look into it yet).
Logfiles and additional information
FDE unlocking works.