Comment # 14 on bug 1209985 from
> BootOrder: 0001,0000,0010,0011,0012,0013,0014,0017,0018,0019,001A,001B,001C,001D
> Boot0000* opensuse-secureboot   HD(1,GPT,3fe41252-3fdc-476c-9520-034fd1bef10f,0x800,0x100000)/File(\EFI\opensuse\shim.efi)
> Boot0001* opensuse-secureboot   HD(1,GPT,a6944199-4d90-4c5a-a920-70181216dea6,0x800,0x100000)/File(\EFI\opensuse\shim.efi)

That looks a bit suspicious - why two entries with different partition GUID if
there is only one ESP?

lsblk says:

nvme0n1                        259:0    0 476.9G  0 disk
������������������nvme0n1p1                    259:1    0   512M  0 part  /boot/efi
������������������nvme0n1p2                    259:2    0 476.4G  0 part
  ������������������cr_nvme-WDC_PC_SN530_SDBPMPZ-512G-1001_21023T470222-part2
                               254:0    0 476.4G  0 crypt
    ������������������system-swap              254:1    0  14.9G  0 lvm   [SWAP]
    ������������������system-root              254:2    0 461.6G  0 lvm   /var ...

sgdisk --print /dev/nvme0n1 -i 1 says:

Disk /dev/nvme0n1: 1000215216 sectors, 476.9 GiB
Model: WDC PC SN530 SDBPMPZ-512G-1001
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 7C56EC3D-4445-4A0C-999A-40FA74E15942
...
Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         1050623   512.0 MiB   EF00
   2         1050624      1000215182   476.4 GiB   8E00
Partition GUID code: C12A7328-F81F-11D2-BA4B-00A0C93EC93B (EFI system
partition)
Partition unique GUID: A6944199-4D90-4C5A-A920-70181216DEA6
First sector: 2048 (at 1024.0 KiB)
Last sector: 1050623 (at 513.0 MiB)
Partition size: 1048576 sectors (512.0 MiB)
Attribute flags: 0000000000000000
Partition name: ''

so Boot0001 has the right GUID and is also the first in the BootOrder, so it
should work.
Question is where this weird Boot0000 is coming from. lsblk doesn't show any
other block
devices which might host another ESP.


You are receiving this mail because: