SOLVED. Re: Aw: Re: [qubes-users] HELP! after update dom0 "no bootable device found"

2021-01-31 Thread haaber
It seems it ignores your mountpoint, you pass directly the hard disk and EFI partition number (which should be the first) so in: efibootmgr -v -c -u -L Qubes -l /EFI/qubes/xen.efi -d /dev/sda -p 1 "placeholder /mapbs /noexitboot" You only have to worry about /dev/sda

Re: Aw: Re: [qubes-users] HELP! after update dom0 "no bootable device found"

2021-01-30 Thread donoban
On 1/30/21 6:14 PM, haa...@web.de wrote: > root@debian:~# efibootmgr -v -c -u -L Qubes -l /EFI/qubes/xen.efi -d > /dev/nvme0n1 -p 1 "placeholder /mapbs /noexitboot" > efibootmgr: ** Warning ** : Boot0002 has same label Qubes > BootCurrent: 0001 > Timeout: 0 seconds > BootOrder: ,0001 >

Aw: Re: [qubes-users] HELP! after update dom0 "no bootable device found"

2021-01-30 Thread haaber
      Gesendet: Samstag, 30. Januar 2021 um 10:28 Uhr Von: "donoban" An: qubes-users@googlegroups.com Betreff: Re: [qubes-users] HELP! after update dom0 "no bootable device found" Hi, On 1/30/21 8:43 AM, haa...@web.de wrote: > I am surprised by the sizes -- files seem small. Do the seem