Problems with cachyos kernel: VFS: Cannot open root device "/dev/mapper/cryptroot" or unkown-block(0,0): error -6
I used bootster with the default arch linux kernel, without problems. But for some reason the same config doesn't work with the cachyos kernel.
My setup:
- btrfs with
- LUKS encrytped swap partition (cryptswap)
- LUKS encrypted root partition (cryptroot)
I didn't use `/etc/booster.yaml` for my initial setup, but I have tried many settings there for debugging without luck.
Grub config:
```
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 rd.luks.name={root_luks_uuid}=cryptroot rd.luks.name={swap_luks_uuid}=cryptswap root=/dev/mapper/cryptroot rw"
```
Building:
```
sudo /usr/lib/booster/regenerate_images
sudo cp /boot/booster-linux-cachyos.img /boot/initramfs-linux.img
sudo grub-mkconfig -o /boot/grub/grub.cfg
```
Kernel Panic at boot:
```
check access for rdinit=/init failed: -2, ignoring
ext3: Unknown parameter 'subvol'
ext2: Unknown parameter 'subvol'
ext4: Unknown parameter 'subvol'
fuseblk: Unknown parameter 'subvol'
VFS: Cannot open root device "/dev/mapper/cryptroot" or unkown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
List of all bdev filesystems:
ext3
ext2
ext4
fuseblk
btrfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block(0,0)
fbcon: Taking over console.
```
It seems that it doesn't matter what I put in `booster.yaml` or `GRUB_CMDLINE_LINUX_DEFAULT`, the issue always looks the same...
I've been fiddling with this for hours and hours, without luck...
Does anyone know what is going 🙏
关闭于 2026-01-10 1 条评论