Maybe I do have the problem that it worked so well in the past which allowed my assumption that testing is basically a rolling release which is as stable as other distributions standard releases. (Other people told me something along these lines too.)The Testing install images are to test the installer as much as for installing, and not guaranteed to always work. Installing Stable and upgrading to Testing is more reliable.
It seems even the expert installer did deal with "ESP" in the past automatically and therefore until now I never even heard or red anything about it. But I do always start the installer in UEFI mode nowadays.For the netinstall, make sure you create an ESP and set its mount point as /boot/efi/, and boot the installer in UEFI mode.
Unfortunately, I again ran into the same problem with the stable live image using the normal GUI installer (my own translation from German):
I wonder if my hard disk is somehow faulty after several days of failed installations. I always select to delete all partitions in order to wipe all possible conflicting files, but I can't be sure if some left-over code from previous attempts messes things up since I don't actually know what happens under the hood.The boot loader couldn't be installed. The installation command "grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=Debian --force" resulted in error code 1.
I always go for a fully LUKS encrypted system. Maybe this causes the issue. (It however has worked in the past without issues.)
The live image of the stable release works as intended by the way.
Statistics: Posted by Onsemeliot — 2024-12-08 10:55