Follow-up Comment #3, bug #63127 (project grub):
[comment #2 comment #2:] > Do not use losetup with offset. Use kpartx instead I've just tried, but it seems there's still some kind of a problem that grub-install is not happy with. Here's the session log: mk7@linux-xmpl:~/development/milan/uefi> sudo /usr/sbin/kpartx -avg ./uefi.img add map loop0p1 (254:0): 0 91669 linear 7:0 2048 mk7@linux-xmpl:~/development/milan/uefi> sudo /sbin/mkfs.fat -F 32 /dev/mapper/loop0p1 mkfs.fat 4.2 (2021-01-31) mk7@linux-xmpl:~/development/milan/uefi> sudo mount /dev/mapper/loop0p1 /mnt mk7@linux-xmpl:~/development/milan/uefi> sudo /usr/local/sbin/grub-install --bootloader-id=GRUB --disable-shim-lock --efi-directory=/mnt --target=x86_64-efi --no-nvram --boot-directory=/mnt --debug-image=all /dev/mapper/loop0p1 Installing for x86_64-efi platform. Found EFI device: /dev/mapper/loop0p1 Volume group "loop0p1" not found Cannot process volume group loop0p1 Volume group "loop0p1" not found Cannot process volume group loop0p1 /usr/local/sbin/grub-install: error: disk `lvm/loop0p1' not found. mk7@linux-xmpl:~/development/milan/uefi> _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?63127> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/