[Software] os-prober or equivlent mkconfig cannot find encrypted LVM

[lWanderingl]

For the past few months I've been trying to create a LUKS LVM, first manually via terminal, then through the installation drive and now manually again.

Fact is that I'm not able to boot into debian, will it be because the boot results in an init terminal or because I can't even manage to create an option for the boot menu (check title.
Technically I could try to create the boot option manually but I have the feeling that it won't work so I prefer the automatic procedure.

I'll explain how I set up the system after creating the encrypted LVM, to do so I have followed many guides and forum threads and patched all the info togeter.

This is my /etc/crypttab:

Code: Select all

                                                                                                            
# /etc/crypttab: mappings for encrypted partitions.
#
# Each mapped device will be created in /dev/mapper, so your /etc/fstab
# should use the /dev/mapper/<name> paths for encrypted devices.
#
# See crypttab(5) for the supported syntax.
#
# NOTE: You need not list your root (/) partition here, but it must be set up
#       beforehand by the initramfs (/etc/mkinitcpio.conf). The same applies
#       to encrypted swap, which should be set up with mkinitcpio-openswap
#       for resume support.
#
# <name>               <device>                                     <password>       <options>
nvme0n1p5_crypt       UUID=9220f2d8-62e0-4931-9596-e3678023c69c        none         luks,discard,lvm=nvme0n1p5_crypt--vge01-root

Where nvme0n1p5_crypt is the physical volume (the UUID belongs to the decrypted volume NOT to the partition #5), vge01is the volume group and root is the logical volume that acts as the root partition.


Then there's /etc/fstab, which is pretty self-explanatory imo

[/code]
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/nvme0n1p5_crypt--vge01-root / ext4 errors=remount-ro 0 1
/dev/mapper/nvme0n1p5_crypt--vge01-swap none swap sw 0 0
UUID=8d2e6b2d-a504-4c6a-b829-d95d32c3a0bc /boot ext4 defaults 0 2
UUID=D4C1-5BA2 /boot/efi vfat vmask=0077 0 0
/dev/mapper/nvme0n1p5_crypt--vge01-var /var ext4 errors=remount-ro 0 2
/dev/mapper/nvme0n1p5_crypt--vge01-home /home ext4 defaults 0 2

[/code]

This is the result for both sudo grub-mkconfig -o /boot/grub/grub.cfg or simply update-grub

Code: Select all

Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done

As you can see only Windows gets detected, and yes my linux has efi variables mounted AND I've ran update-initramfs -u -k all.

Any idea on how to fix this issue? I've been trying for quite a long time while other people manage to make it work so easily, there must be some critical step I'm doing wrong but there's no precise guide on how to set all of these files under /.

[ruwolf]

I am not an expert, but where are you running command grub-mkconfig from? USB stick?
And where are your Debian images which you want to boot, i.e. Linux kernel image & initial ramdisk image?
(I am asking, because you have written, that you cannot boot into Debian.)