Going back to the menu and selecting LILO gives me the same error. The installation log saysAn installation step failed. You can try running the failing item again from the menu, or skip it and choose something else. The failing step is: Install the GRUB boot loader on a hard disk
Code: Select all
May 1 13:24:23 main-menu[188]: WARNING **: Configuring 'grub-installer' failed with error code 1
May 1 13:24:23 main-menu[188]: WARNING **: Menu item 'grub-installer' failed.
May 1 13:24:28 main-menu[188]: INFO: Menu item 'lilo-installer' selected
May 1 13:24:28 main-menu[188]: WARNING **: Unable to set title for fdisk-udeb.
May 1 13:24:28 main-menu[188]: WARNING **: Configuring 'lilo-installer' failed with error code 1
May 1 13:24:28 main-menu[188]: WARNING **: Menu item 'lilo-installer' failed.
- I disabled UEFI boot in the BIOS and selected legacy boot instead. The error still occurs with both GRUB and LILO.
- Instead of the netinstall CD, I used the full DVD. Same error. I'm booting both of these from USB.
- The machine passed all hardware tests. When I first bought it, I ran all the available hardware tests, both from within the BIOS and from within Windows, and it passed all of them. I'm assuming that means the hardware isn't malfunctioning.
- Following this thread on the Crunchbang forums that had a similar error (albeit with LVM), I redid the partition scheme with a small /boot partition at the beginning of the disk, formatted with ext2. Same error with both bootloaders.
- Switching to TTY4 to look at the installation output, I also see the error
Searching for information on that turns up this thread and this bug report related to GRUB. However, those are fairly old posts, and I have run through the installation over a dozen times now and I get the error every time, so it doesn't seem like a one-off thing.
Code: Select all
chroot: can't execute 'grub-probe': No such file or directory
- I've used Gparted to check that the hard disk is completely empty. Other threads have mentioned that Windows' recovery partitions and other hidden partitions may cause problems, but as far as I can tell that isn't the case here. I was able to successfully create an msdos partition table and three partitions (for /, /home, and swap) on the drive in the previous installation step, so I don't know why GRUB and LILO suddenly can't write to the drive when parted could.
- Following the instructions on this StackExchange question that had a (possibly) similar issue with GRUB, GPT, and RAID, I can
from TTY2, but I get an error that says "parted not found." On my system /dev/nvme01 is the only hard disk.Code: Select all
parted /dev/nvme01 set 1 bios_grub on
---
Could part of the problem be that Debian/parted recognizes the disk incorrectly? It says the disk is 512.1 GB, which is true in the sense that the specs say 512 GB and that's what is advertised, and it will let me allocate all 512 GB to various partitions. However, if I load it in Gparted live, the actual disk space is closer to 476 GB, but I assumed that's just the usual 1024 vs 1000 stuff.