Sometimes it can happen that the network install in text mode finishes without writing a boot loader to the disk on a system where EFI is enabled. I am not sure why this happens. Usually the install asks for the location of the boot loader to be written, but in such cases the install ends with a screen suggesting to boot into the new system. And since grub is not installed, it will never boot into the new system.
chroot
.
mount devpts /dev/pts -t devpts
/etc/init.d/ssh start
ip addr show
x86_64-efi
or i386-pc
) is used a simple ls
will do:
ls -1 /usr/lib/grub/
grub-mkconfig_lib
x86_64-efi
x86_64-efi-signed
sda
to the correct device!)
grub-install /dev/sda
Installing for x86_64-efi platform.
grub-install: warning: EFI variables are not supported on this system.
Installation finished. No error reported.
efivar
file system:
modprobe efivarfs
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
grub-install /dev/sda
Installing for x86_64-efi platform.
Installation finished. No error reported.
update-grub
initramfs
update-initramfs -u
There have been reports of this not working. As a workaround, switch the BIOS to legacy mode, reboot, and then either reinstall the OS, or follow similar steps as above, but omit modprobe
and mount
, and install the correct i386-pc
grub libraries via package before running grub-install
.
Version | Date | Notes |
---|---|---|
0.1.0 | 2023-04-24 | Initial release |