On 16.01.2024 19:39, Harry Hirte wrote:
On Tuesday, January 16, 2024 at 03:28:43 PM GMT+1, Andrei Borzenkov
wrote:
You specify it as (hd0) *where*?
instead of the ($keyfile)0+ I use (hd0) - then it does work
cryptomount -k ($keyfile)0+ -O xxx -S yyy -u $crypto_uuid
Do you
On Tuesday, January 16, 2024 at 03:28:43 PM GMT+1, Andrei Borzenkov
wrote:
> You specify it as (hd0) *where*?
instead of the ($keyfile)0+ I use (hd0) - then it does work
>> cryptomount -k ($keyfile)0+ -O xxx -S yyy -u $crypto_uuid
>Do you really have the file with the name "0+" on
On Tue, Jan 16, 2024 at 5:13 PM Harry Hirte wrote:
>
> Hello,
>
> I am trying to read data from a USB-Stick when booting from grubx64.efi
> This basically only works if I specify the device as (hd0).
You specify it as (hd0) *where*?
> I am looking for a possibility to uniquely identify the
Hello,
I am trying to read data from a USB-Stick when booting from grubx64.efi
This basically only works if I specify the device as (hd0).
I am looking for a possibility to uniquely identify the USB-stick.
I build my grubx64.efi using
grub-mkimage ... -c -o ... luks2 part_gpt cryptodisk ...