Unusual actions involving several GRUB setups Multiple GRUB configurations causing unexpected behavior
Unusual actions involving several GRUB setups Multiple GRUB configurations causing unexpected behavior
I just went through LFS over the past few days and everything seemed fine. Now it won’t even start up. From the start, I swapped out my NVMe SSD because I feared damage during installation. I installed two drives—one running Manjaro, the other as the host for building LFS. After finishing the build, I could switch between Manjaro and LFS via the boot menu. Once I felt safe, I removed both drives and reinstalled the NVMe. That’s when I realized it wouldn’t boot at all. I’m puzzled because the only other drive connected is a 4TB EXT4 one, which shouldn’t have caused issues. I suspect GRUB might have been installed incorrectly or its root partition changed.
I fixed it by disconnecting everything except my NVMe, then chrooting from a live system, remounting files, and reinstalling GRUB. But this morning the same thing happened again—reconnecting LFS failed. I can now boot from Arch but my board still won’t recognize the disk as bootable. Even when I tried to connect the Manjaro drive just in case, LFS remained missing.
Now that my NVMe is back, I’m worried about installing GRUB inside a chroot environment, fearing it could ruin my main installation. The thermal pad on the SSD got stuck during removal, making it hard to handle. Anyone have any thoughts on why such a smooth build would fail after just a few hours?
The standard Grub setup places the entry on the Boards EFI list, but some boards may remove it if the drive isn't detected. You might want to try a portable/removable install. Use the command: grub-install --target=x86_64-efi --removable --efi-directory=/boot --bootloader-id="Linux From Scratch"
The process seems logical and helps clarify the boot issue. Installing GRUB via chroot can pose risks if not handled carefully. There could be potential dangers to the host if security settings or system configurations are altered improperly during installation.
It shouldn't impact the host because everything should stay within the updated root directory of the chroot.
I will proceed with uploading this now because the "--boot-directory" choice wasn’t included. The guide suggests it’s likely required. https://www.gnu.org/software/grub/manual...stall.html You may need to adjust mount points and paths—though both "/boot" and "/boot/efi" technically exist in my setup. I’m not certain how Grub manages them. It’s been a while since I had to configure a portable Grub. Edited November 6, 2021 by Nayr438