On 14/01/2025 at 04:04, Ted wrote:
I installed Debian with "GNU/Linux trixie-DI-alpha1 _Trixie_ - Official Alpha amd64 NETINST with firmware 20241230-11:26" using the luks encrypted full disk partition scheme. It installed but the installer used an efi partition from another disk where there was another Debian installation.
Possibly a duplicate of #1034208, #1034812, #1041168. Hopefully fixed by the change proposed in #1092892.
When I moved the disk to its real home and tried to boot the computer looked at me like a dog who was just shown a card trick, it couldn't boot. I did the luks-encrypted full disk trixie installation to /dev/sdb.
Note that even if the installer had used the correct EFI partition, it would not have booted on another machine because the EFI boot variables were not updated on the target machine but on the installing machine (possibly breaking booting on the other disk).
I had to boot a computer from a working Linux installation, decrypt the encrypted partition, then mount the proper partitions at /mountpoint, /mountpoint/boot and /mountpoint/boot/efi, then chroot to the system, edit the fstab to point to the efi partition on the OS disk, then reinstall grub with "grub-install /dev/sdb" and run update-grub
"/dev/sdb" is useless with EFI. By default grub-install uses the EFI partition mounted on /boot/efi.
