On 10/04/2025 at 15:23, Marcos Dione wrote:
On Wed, Apr 09, 2025 at 10:35:46AM +0200, Pascal Hambourg wrote:
On 08/04/2025 at 14:25, Marcos Dione wrote:
BootOrder: 0001,0002,0003,0004,0006,0007
Boot0000* ubuntu
HD(1,GPT,127eb1be-f7c7-4a2b-9745-4cb61cba7420,0x800,0x190000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* Diskette Drive BBS(Floppy,Diskette Drive,0x0)0000424f
Boot0002* M.2 PCIe SSD BBS(HD,P0: WDC WDS200T2B0C-00PXH0,0x0)0000424f
Boot0003* USB Storage Device BBS(USB,SanDisk,0x0)0000424f
Boot0004* CD/DVD/CD-RW Drive BBS(CDROM,CD/DVD/CD-RW Drive,0x0)0000424f
Boot0005* Onboard NIC BBS(Network,Onboard NIC,0x0)0000424f
Boot0006* Onboard NIC BBS(Network,Onboard NIC,0x0)0000424f
Boot0007* UEFI: SanDisk, Partition 1
PciRoot(0x0)/Pci(0x14,0x0)/USB(16,0)/HD(1,MBR,0x52bf7ba9,0x117c,0x4a20)0000424f
Boot0008* M.2 PCIe SSD BBS(HD,P0: PM981 NVMe Samsung 512GB,0x0)0000424f
Boot0009* debian
HD(1,GPT,127eb1be-f7c7-4a2b-9745-4cb61cba7420,0x800,0xbe5e)/File(\EFI\debian\shimx64.efi)
The debian boot entry number 0009 is not in BootOrder, no wonder why it does
not boot automatically. grub-install updates BootOrder to make the debian
entry first unless --no-nvram is passed, so something is wrong here.
... so it's trying to boot from where, the m.2?
If the UEFI firmware follows BootOrder (not all do), it first tries to
boot from a diskette drive (0001), then from the WDC SSD (0002), then
from a USB storage device (0003), then from an optical disc drive
(0004), then from the network (0006, then from the Sandisk USB drive (0007).
It's the only other
thing listed there that's still available when I boot w/o the USB stick.
What would that mean? Trying to boot from the MBR?
No, it tries to boot from the "removable media path"
/EFI/boot/bootx64.efi in the EFI partition.
I don't know why the M.2 appears twice.
There are two different SSDs, 2TB Western Digital and 512GB Samsung.
Did you mean SanDisk? That's the USB stick.
No, I mean "WDC WDS200T2B0C-00PXH0" and "PM981 NVMe Samsung 512GB".
The EFI partition is very small. It is big enough for GRUB but not for
systemd-boot.
I guess I'm not using systemd-boot, so that's OK?
Yes, unless GRUB monolithic image grows ridiculously big or eventually
switches to the BLS (Boot Loader Specification) which needs to put
kernel images and initramfs's into the EFI partition.
