Closed ominitay closed 3 years ago
This is the output I get ^
I'm pretty sure something wrong with kernel configuration or partition layout. Look, mount(2)
fails with ENODEV error (No such device). According to https://man7.org/linux/man-pages/man2/mount.2.html this means that filesystem is not supported in kernel or corresponding module wasn't loaded.
Are you using kernel with builtin or external modules?
Oh, I have modules in /lib/modules/5.10.16, so I'll try rebuilding with monolith=0...
Unfortunately that did not fix it. Do you think I may have misconfigured my kernel perhaps? I'm going to build the kernel I use on my Arch install, which is known to work, just to reduce the factors.
:woman_facepalming: I realised that I hadn't built the Kernel with BTRFS support. Sorry for making this issue.
All good :)
I am trying to run Kiss from a BTRFS partition on an LVM logical volume. I get dropped into an emergency shell, with the error that the device being mounted doesn't exist. I can see the device in
/dev
. From the emergency shell, I get the same error if I try to mount the root partition manually, though this doesn't happen to the non-lvm, non-btrfs, EFI partition (that mounts fine).My config is:
The output of
blkid | grep kissroot
is