Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I still end up at a grub rescue prompt when I reboot the system ...
Any advice or suggestions as to how I might "force" grub
to use aforementioned environmental parameters and find the
EFI directory would be greatly appreciated.
Tom
(Naturally Nuts ... no pharmaceuticals required)
The efi partition is normally a small FAT?? type partition with key stuffs.
# blkid
/dev/sda1: UUID="FFFF-FFFF" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="01234567-0123-4567-89ab-0123456789ab"
Looks kind of like that. I just use DOS based grub installs. Normally a small debian stable install and it's grub boots whatever other distros. Although on one system I use grub to jump to the other grub on the SSD.
Mostly because I was too lazy to redo the SSD in a dos partitioning scheme. And it didn't seem to be bootable in it's GPT configuration. So I booted a usb stick to jump to the grub on the GPT formatted SSD.
Why are you installing grub to a partition ?. Especially grub2 and more bizarrely when using EFI ?.
What distro ? - use of update-grub implies Debian derived. Mint (and presumably other Ubuntu based distros) finds everything properly when simply installed to the device node. I've tested this by deliberately forcing errors in the boot environment on a UEFI test system.
I have verified backups for my Windows, Linux & home partitions (Clonezilla)
but not my UFI partition.
A little more background information for you syg00 ...
This is a HP laptop dual boot system: WindowsPro 10 and MX Linux (Jessie).
By the way this boot problem occurred immediately after installing Ext2Fsd on the windows system / partition.
The EFI boot partition is /dev/sda1 ... the first partition as expected
The Windows partition is /dev/sda3
The Linux root partition is /dev/sda4
Yes I have tried installing grub to /dev/sda1 the default choice ...
However the following error occurs:
You indicate you are trying to boot 'MXLinux' and are using a UEFI intall in your last post. The output you posted in your last post shows the contents of the EFI directory/partition which clearly shows 'MX16' so I'm not sure that reinstalling Grub is the solution. That directory should contain the needed folders to boot that system. What happens when you boot? Does it boot directly to windows? Does it no boot at all. If it boots directly to windows, you need to change the boot option priority. It would be useful if the next time you booted the system you logged into a terminal as root and ran this command, post the output here:
Code:
efibootmgr
On my HP Laptop on boot, I hit the Esc key and then get a screen with several options. One is F10 which goes to the BIOS and one is F9 which gives different boot options. When you do the F9, do you see anything other than windows or boot from disk? If so, what?
There is a fairly simple command to install Grub EFI from a booted system but given the fact that your EFI partition clearly shows the MX16 folder, I doubt that is the problem. The efibootmgr command output will show the various entries you have and their priority and that can be changed.
# mount -t vfat /dev/sda1 /mnt
# cd /mnt
# ls -l
drwxr-xr-x 6 root root 4096 Jul 15 14:17 EFI
drwxr-xr-x 2 root root 4096 Dec 3 2016 System Volume Information
# cd EFI
# ls -l
drwxr-xr-x 2 root root 4096 Dec 3 2016 Boot
drwxr-xr-x 5 root root 4096 Jul 15 14:17 HP
drwxr-xr-x 4 root root 4096 Dec 3 2016 Microsoft
drwxr-xr-x 2 root root 4096 Dec 22 2016 MX16
Hi griffon, I actually dual boot Win10 and Slackware using UEFI.
The problem is that the grub commands do not work the same way as before due to UEFI. Your config files for grub remain on your / filesystem at /boot/grub/ but the grub EFI binary which boots at start is actually installed on the EFI partition, which in your case is /dev/sda1. If you look into EFI/MX16 I bet you'll find your grub EFI binary, since your system actually boots grub (but unfortunately the grub rescue).
Now, since you solved your problem with a few lines, you might want to add these lines to grub.cfg. So edit the file /boot/grub/grub.cfg and it should work. If it doesn't, try to see if there is a grub.cfg on the EFI partition near grub's EFI binary.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.