On 18/12/2024 04:56, Roger Price wrote:
On Tue, 17 Dec 2024, Max Nikulin wrote:
Have you tried to plug the stick into another USB port (e.g. USB2
instead of USB3 or vice versa)? Try full power cycle, not just reboot.
All the 10 USB ports on my T5820 are specified as USB 3.1 Gen 1. I
always do a full powercycle.
I just happened to have a cheap USB3 that fails on attempt to boot when
it is plugged into the USB2 port of my old laptop.
A variation is: not the same hub as keyboard and mouse.
grub> echo $cmdpath
(hd2,gpt1)/EFI/debian
grub> echo $fw_path
### no output ###
(hd2,gpt3) and (hd2,gpt4) have filesystem ntfs, so hd2 is the Microsoft
SSD.
So during some attempt installer picked existing ESP (expected). Does
EFI/debian/grub.cfg on this partition contains valid UUID ("lsblk --fs"
to list)?
Maybe I misunderstood your messages, but I decided that you could not
boot from the installer USB stick any more. I suspected that Grub from
installer tried to use config from some internal drive.
I pulled out the Microsoft SSD
Does UEFI firmware settings (BIOS) allow to disable booting from
specific drives? It took some time for me to discover this feature on my
HP laptop (it does not allow to manage boot entries though).
Finally, I installed Debian 12.8 taking care to specify the special file
type EFI for the small bootable partition.
A warning against excessively small ESP:
<https://fedoraproject.org/wiki/Changes/BiggerESP>
With the "windows" drive plugged in you still can create ESP manually on
any drive and to specify its purpose.
I suggest to inspect output of
findmnt /boot/efi
efibootmgr -v
and to remove stale entries. If the ESP for Debian is on the Kingston
drive then I suggest to remove EFI/debian from the Windows ESP. This
directory might cause confusion later. (There is nothing bad to have ESP
shared by multiple OSes, but it is less flexible in the approach with
drive per OS.)
