Hello everyone,
I can't get my refind configuration to work properly.
My goal is to use arch and debian in dual boot. The arch system is automatically recognized by refind and can be booted (and is used). The debian system is not recognized and whenever I try to create a manual entry for the debian system, I get the following error after selecting the debian entry in the boot menu:
The corresponding entry in my refind.conf looks like this:The boot partition for the debian system is /dev/nvme0n1p5This is its content:I have one EFI partition (which is only an EFI partition) and seperate boot partitions (one for each system).
The only difference between the boot partition of my arch system and the one of the debian system is that the boot partition of my arch system is formatted with FAT32 and the one of the debian system with ext4. But refind supports ext4 so I do not think that this should be an issue.
I no longer have any idea why it shouldn't work.
I would be very grateful for any help!
I can't get my refind configuration to work properly.
My goal is to use arch and debian in dual boot. The arch system is automatically recognized by refind and can be booted (and is used). The debian system is not recognized and whenever I try to create a manual entry for the debian system, I get the following error after selecting the debian entry in the boot menu:
Code:
Error: Not Found while loading vmlinuz-6.1.0-21-amd64Code:
menuentry DaggerDebian { icon EFI/refind/icons/os_debian.png volume F736CA13-8DA0-400A-9FC0-A626E6A770A3 # according to the arch wiki this has to match either a filesystems LABLE, a PARTLABEL or a PARTUUID of the partition where the kernel image resides (not the UUID!) loader /vmlinuz-6.1.0-18-amd64 initrd /initrd.img-6.1.0-18-amd64 options "rw cryptdevice=UUID=431e411a-e641-4715-9d09-dd8cd56da209:daggerdebian-crypt:allow-discards root=/dev/mapper/daggerdebianvg-root quiet" # disabled}Code:
sudo blkid /dev/nvme0n1p5/dev/nvme0n1p5: UUID="d24a13ee-c133-4a87-b9ff-c68ab0097d26" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="daggerdebian-boot" PARTUUID="f736ca13-8da0-400a-9fc0-a626e6a770a3"Code:
❯ sudo mount /dev/nvme0n1p5 /mnt❯ ls /mntconfig-6.1.0-18-amd64 grub initrd.img-6.1.0-21-amd64 refind_linux.conf System.map-6.1.0-21-amd64 vmlinuz-6.1.0-21-amd64config-6.1.0-21-amd64 initrd.img-6.1.0-18-amd64 lost+found System.map-6.1.0-18-amd64 vmlinuz-6.1.0-18-amd64❯ cat /mnt/refind_linux.conf"Boot daggerdebian System" "rw cryptdevice=UUID=431e411a-e641-4715-9d09-dd8cd56da209:daggerdebian-crypt:allow-discards root=/dev/mapper/daggerdebianvg-root quiet"The only difference between the boot partition of my arch system and the one of the debian system is that the boot partition of my arch system is formatted with FAT32 and the one of the debian system with ext4. But refind supports ext4 so I do not think that this should be an issue.
I no longer have any idea why it shouldn't work.
I would be very grateful for any help!
Statistics: Posted by RisingPheonix — 2024-07-20 19:43 — Replies 2 — Views 43