[SOLVED] Unknow filesystem "btrfs" when booting Linux 6.0.2

Tid91 · 2022-10-22 22:09:51

My daily configuration is on linux-lts. Wanted to try to use the mainline version, so I switched to that version using refind and the kernel doesn´t boot giving "Unknown filesystem `btrfs`", like if it was not compiled with btrfs support. Any idea why?

sudo lsinitcpio /boot/initramfs-linux.img | grep btr

usr/bin/fsck.btrfs
usr/lib/modules/6.0.2-arch1-1/kernel/btrfs.ko
usr/lib/udev/rules.d/64-btrfs.rules

/etc/mkinitcpio.conf

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=()

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

/boot/refind_linux.conf (second entry is the one I'm triggering)

"Boot with standard options LTS"  "ro root=UUID=71bef7d1-9c9e-4bc9-ba39-94a2c0bee1b8 initrd=/boot/intel-ucode.img initrd=/boot/initramfs-linux-lts.img init_on_alloc=0"
"Boot with standard options"  "ro root=UUID=71bef7d1-9c9e-4bc9-ba39-94a2c0bee1b8 initrd=/boot/intel-ucode.img initrd=/boot/initramfs-linux.img init_on_alloc=0"
"Boot to single-user mode"    "ro root=UUID=71bef7d1-9c9e-4bc9-ba39-94a2c0bee1b8 single"
"Boot with minimal options"   "ro root=UUID=71bef7d1-9c9e-4bc9-ba39-94a2c0bee1b8"

tree /efi

/efi
├── BOOTLOG
├── efi
│   ├── APPLE
│   │   ├── CACHES
│   │   │   └── CAFEBEEF
│   │   ├── EXTENSIONS
│   │   │   └── Firmware.scap
│   │   └── FIRMWARE
│   │       └── MBP61.scap
│   └── refind
│       ├── drivers_x64
│       │   ├── btrfs_x64.efi
│       │   ├── ext2_x64.efi
│       │   ├── ext4_x64.efi
│       │   ├── hfs_x64.efi
│       │   ├── iso9660_x64.efi
│       │   ├── LICENSE_GPL.txt
│       │   ├── LICENSE.txt
│       │   └── reiserfs_x64.efi
│       ├── icons
│       │   ├── arrow_left.png
│       │   ├── arrow_right.png
│       │   ├── boot_linux.png
│       │   ├── boot_win.png
│       │   ├── func_about.png
│       │   ├── func_bootorder.png
│       │   ├── func_csr_rotate.png
│       │   ├── func_exit.png
│       │   ├── func_firmware.png
│       │   ├── func_hidden.png
│       │   ├── func_install.png
│       │   ├── func_reset.png
│       │   ├── func_shutdown.png
│       │   ├── licenses
│       │   │   ├── cc-3.0.txt
│       │   │   ├── cc-by-sa-4.0.txt
│       │   │   ├── gpl-2.0.txt
│       │   │   └── lgpl-3.0.txt
│       │   ├── mouse.png
│       │   ├── os_arch.png
│       │   ├── os_artful.png
│       │   ├── os_bionic.png
│       │   ├── os_centos.png
│       │   ├── os_chakra.png
│       │   ├── os_chrome.png
│       │   ├── os_clover.png
│       │   ├── os_crunchbang.png
│       │   ├── os_debian.png
│       │   ├── os_devuan.png
│       │   ├── os_elementary.png
│       │   ├── os_fedora.png
│       │   ├── os_freebsd.png
│       │   ├── os_frugalware.png
│       │   ├── os_gentoo.png
│       │   ├── os_gummiboot.png
│       │   ├── os_haiku.png
│       │   ├── os_hwtest.png
│       │   ├── os_kubuntu.png
│       │   ├── os_legacy.png
│       │   ├── os_linuxmint.png
│       │   ├── os_linux.png
│       │   ├── os_lubuntu.png
│       │   ├── os_mac.png
│       │   ├── os_mageia.png
│       │   ├── os_mandriva.png
│       │   ├── os_manjaro.png
│       │   ├── os_netbsd.png
│       │   ├── os_network.png
│       │   ├── os_opensuse.png
│       │   ├── os_redhat.png
│       │   ├── os_refind.png
│       │   ├── os_refit.png
│       │   ├── os_slackware.png
│       │   ├── os_suse.png
│       │   ├── os_systemd.png
│       │   ├── os_trusty.png
│       │   ├── os_ubuntu.png
│       │   ├── os_uefi.png
│       │   ├── os_unknown.png
│       │   ├── os_void.png
│       │   ├── os_win8.png
│       │   ├── os_win.png
│       │   ├── os_xenial.png
│       │   ├── os_xubuntu.png
│       │   ├── os_zesty.png
│       │   ├── README
│       │   ├── tool_apple_rescue.png
│       │   ├── tool_fwupdate.png
│       │   ├── tool_memtest.png
│       │   ├── tool_mok_tool.png
│       │   ├── tool_netboot.png
│       │   ├── tool_part.png
│       │   ├── tool_rescue.png
│       │   ├── tool_shell.png
│       │   ├── tool_windows_rescue.png
│       │   ├── transparent.png
│       │   ├── vol_efi.png
│       │   ├── vol_external.png
│       │   ├── vol_internal.png
│       │   ├── vol_net.png
│       │   └── vol_optical.png
│       ├── refind.conf
│       ├── refind_x64.efi
│       ├── tools_x64
│       │   ├── gptsync_x64.efi
│       │   └── shell.efi
│       └── vars
│           └── PreviousBoot
└── startup.nsh

12 directories, 97 files

Last edited by Tid91 (2022-11-02 09:20:45)

Slithery · 2022-10-22 22:40:37

What's the output of...

pacman -Q linux
uname -a

astralc · 2022-10-23 05:05:38

refind, by default, combine the kernels to single entry (fold_linux_kernels option), so it incorrect to use refind_linux.conf with hard coded initramfs values.
read the wiki & refind site for examples exactly how (using %v).

Are you sure you selected the correct kernel version in refind in the tab menu?

Last edited by astralc (2022-10-23 05:06:39)

cfr · 2022-10-23 05:35:42

I don't think the %v is relevant to Arch since the files aren't versioned anyway., but the syntax is wrong. You don't forward slashes in refind_linux.conf.

astralc · 2022-10-23 06:44:24

cfr wrote:

I don't think the %v is relevant to Arch since the files aren't versioned anyway., but the syntax is wrong. You don't forward slashes in refind_linux.conf.

you need it is if you use more than one kernel (like mainline and lts) - you are using single file for both of the kernels. (of course need extra_kernel_version_strings set correctly). Also you can use both slashes (it passed as parameter) in refind.

cfr · 2022-10-23 23:02:25

astralc wrote:

you need it is if you use more than one kernel (like mainline and lts) - you are using single file for both of the kernels. (of course need extra_kernel_version_strings set correctly). Also you can use both slashes (it passed as parameter) in refind.

Thanks. I'd forgotten %v could be used that way. But the wiki definitely suggests forward slashes should be avoided.

wiki wrote:

Use backslashes (\) as path separators in the initrd parameter, otherwise the kernel may fail to find the initramfs image(s): EFI stub: ERROR: Failed to open file: /boot/intel-ucode.img.

Personally, I avoid using refind_linux.conf and do all my configuration elsewhere because I find it easier to see what I'm doing, but I'm not relying on autodetection to find things so things have to be specified a bit more extensively.

Tid91 · 2022-11-02 08:51:42

Slithery wrote:

What's the output of...
pacman -Q linux
uname -a

linux 6.0.2.arch1-1
Linux rdbisme-mbp 5.15.74-1-lts #1 SMP Sat, 15 Oct 2022 06:43:47 +0000 x86_64 GNU/Linux

Tid91 · 2022-11-02 08:55:30

astralc wrote:

refind, by default, combine the kernels to single entry (fold_linux_kernels option), so it incorrect to use refind_linux.conf with hard coded initramfs values.
read the wiki & refind site for examples exactly how (using %v).
Are you sure you selected the correct kernel version in refind in the tab menu?

Well, yes? I can see exactly the second entry name, and when loading the kernel parameters, intitrd file, and microcode are matching exactly what's in `refind_linux.conf`. I actually read the wiki for refind, but I can´t manage to understand what I'm doing wrong (since the first entry works correctly).

Can you elaborate a bit on what I should check?

I have also configured this in `refind.conf`, as told by the wiki article, in `/efi/efi/refind/refind.conf`.

extra_kernel_version_strings linux-lts,linux

Last edited by Tid91 (2022-11-02 09:02:12)

Tid91 · 2022-11-02 09:19:23

Ok, update: if I switch to use the %v and using backslashes in `/boot/refind_linux.conf`, I can manage to boot into 6.0.2. I have some other troubles with the desktop manager, but that is for another thread. Thanks for helping!

"Boot with standard options"  "ro root=UUID=71bef7d1-9c9e-4bc9-ba39-94a2c0bee1b8 initrd=boot\intel-ucode.img initrd=boot\initramfs-%v.img init_on_alloc=0"
"Boot to single-user mode"    "ro root=UUID=71bef7d1-9c9e-4bc9-ba39-94a2c0bee1b8 single"
"Boot with minimal options"   "ro root=UUID=71bef7d1-9c9e-4bc9-ba39-94a2c0bee1b8"

Last edited by Tid91 (2022-11-02 09:20:23)

Arch Linux

#1 2022-10-22 22:09:51

[SOLVED] Unknow filesystem "btrfs" when booting Linux 6.0.2

#2 2022-10-22 22:40:37

Re: [SOLVED] Unknow filesystem "btrfs" when booting Linux 6.0.2

#3 2022-10-23 05:05:38

Re: [SOLVED] Unknow filesystem "btrfs" when booting Linux 6.0.2

#4 2022-10-23 05:35:42

Re: [SOLVED] Unknow filesystem "btrfs" when booting Linux 6.0.2

#5 2022-10-23 06:44:24

Re: [SOLVED] Unknow filesystem "btrfs" when booting Linux 6.0.2

#6 2022-10-23 23:02:25

Re: [SOLVED] Unknow filesystem "btrfs" when booting Linux 6.0.2

#7 2022-11-02 08:51:42

Re: [SOLVED] Unknow filesystem "btrfs" when booting Linux 6.0.2

#8 2022-11-02 08:55:30

Re: [SOLVED] Unknow filesystem "btrfs" when booting Linux 6.0.2

#9 2022-11-02 09:19:23

Re: [SOLVED] Unknow filesystem "btrfs" when booting Linux 6.0.2

Board footer