BL4.5.0 64bit - How to reinstall GRUB, please?

cordx · 04-19-2019, 08:04 AM

in case it might be helpful:

https://www.gnu.org/software/grub/ma...2dinstall.html

madmax25 · 04-19-2019, 04:16 PM

@ colorpurple21859

I moved Bodhi to the 1st place in my BIOS. But it didn't help.

@ mrmazda

Started in Bodhi

Code:

efibootmgr -v

is giving me this information:

Code:

efibootmgr -v
efibootmgr: Skipping unreadable variable "Boot0000": Permission denied
BootCurrent: 0000
Timeout: 0 seconds
show_boot_order(): Permission denied
Boot0001* ubuntu        HD(1,GPT,d1b43d87-d7a1-4691-818b-97ad41b44b0b,0x800,0x82000)/File(\EFI\ubuntu\shimx64.efi)
Boot0003* USB Hard Drive (UEFI) - Generic Flash Disk    PciRoot(0x0)/Pci(0x14,0x0)/USB(2,0)/HD(2,GPT,0d29a6d7-b087-4ddf-95a0-75b9d3f4d39c,0x114,0x1680)RC
Boot0004* Windows Boot Manager  HD(1,GPT,d1b43d87-d7a1-4691-818b-97ad41b44b0b,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...FS...............
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot3000* Internal Hard Disk or Solid State Disk        RC

Something must have severly gone wrong.
"Boot 0000" is denied and "Boot 0002" is missing.
Btw. "Boot 0002" was a copy of "Boot 0003" and I deleted it because I didn't understand why I need two of them.
Probably, I better should have kept that entry, I guess.
How can I get "Boot 0002" back and what can I do about "Boot 0000", please?

Here's the fstab of Bodhi

Code:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda7 during installation
UUID=78b6548b-51d1-4686-a004-b7f26ef54b5a /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=D259-85FC  /boot/efi       vfat    umask=0077      0       1
# /home was on /dev/sda8 during installation
UUID=862737f7-758f-4ad6-aca9-21cb4fc916c9 /home           ext4    defaults        0       2
# swap was on /dev/sda6 during installation
UUID=d71dd44a-8328-43e6-b5b4-e5895dd7d6dd none            swap    sw              0       0

and the output of

Code:

sudo parted -l

Code:

Model: ATA WDC WD10JPVX-60J (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system     Name                          Flags
 1      1049kB  274MB   273MB   fat32           EFI system partition          boot, esp
 2      274MB   290MB   16.8MB                  Microsoft reserved partition  msftres
 3      290MB   492GB   492GB   ntfs            Basic data partition          msftdata
 6      492GB   501GB   8855MB  linux-swap(v1)
 7      501GB   544GB   42.5GB  ext4
 8      544GB   630GB   86.4GB  ext4
 9      630GB   718GB   87.8GB  ext4
10      718GB   984GB   266GB   ext4
 4      984GB   985GB   1028MB  ntfs            Basic data partition          hidden, diag
 5      985GB   1000GB  15.0GB  ntfs            Basic data partition          hidden, msftdata

The information from Xubuntu will follow...

madmax25 · 04-19-2019, 05:21 PM

Here's the fstab of Xubuntu:

Code:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda9 during installation
UUID=f5811b96-28e3-4a0e-a2a0-8064adf69e21 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda1 during installation
UUID=D259-85FC  /boot/efi       vfat    umask=0077      0       1
# /home was on /dev/sda10 during installation
UUID=7d19e5ef-817b-493b-9a2c-694ef214abee /home           ext4    defaults        0       2
# swap was on /dev/sda6 during installation
UUID=d71dd44a-8328-43e6-b5b4-e5895dd7d6dd none            swap    sw              0       0

and the output of

Code:

sudo parted -l

Code:

sudo parted -l
Model: ATA WDC WD10JPVX-60J (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name                          Flags
 1      1049kB  274MB   273MB   fat32           EFI system partition          boot, esp
 2      274MB   290MB   16.8MB                  Microsoft reserved partition  msftres
 3      290MB   492GB   492GB   ntfs            Basic data partition          msftdata
 6      492GB   501GB   8855MB  linux-swap(v1)
 7      501GB   544GB   42.5GB  ext4
 8      544GB   630GB   86.4GB  ext4
 9      630GB   718GB   87.8GB  ext4
10      718GB   984GB   266GB   ext4
 4      984GB   985GB   1028MB  ntfs            Basic data partition          hidden, diag
 5      985GB   1000GB  15.0GB  ntfs            Basic data partition          hidden, msftdata

And with

Code:

efibootmgr -v

I get this:

Code:

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,3000,0004,0001,2001,2002,2004
Boot0000* bodhi	HD(1,GPT,d1b43d87-d7a1-4691-818b-97ad41b44b0b,0x800,0x82000)/File(\EFI\bodhi\shimx64.efi)
Boot0001* ubuntu	HD(1,GPT,d1b43d87-d7a1-4691-818b-97ad41b44b0b,0x800,0x82000)/File(\EFI\ubuntu\shimx64.efi)
Boot0003* USB Hard Drive (UEFI) - Generic Flash Disk	PciRoot(0x0)/Pci(0x14,0x0)/USB(2,0)/HD(2,GPT,0d29a6d7-b087-4ddf-95a0-75b9d3f4d39c,0x114,0x1680)RC
Boot0004* Windows Boot Manager	HD(1,GPT,d1b43d87-d7a1-4691-818b-97ad41b44b0b,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...FS...............
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot3000* Internal Hard Disk or Solid State Disk	RC

mrmazda · 04-19-2019, 07:15 PM

First two things I would would do is ensure CSM mode is disabled in the BIOS, and ensure that the latest available motherboard BIOS is installed.

Next I'd try a BIOS reset. I don't have much faith this is likely to do anything, but I'd do it nevertheless.

Next I would delete the UEFI entry that points to (X)Ubuntu. Whether to first try that in BIOS or using efibootmgr is a good question. I'd probably try efibootmgr first, but since you've had little success with it so far, you might wish to try the BIOS path first. If one didn't work, I'd try the other. If neither worked, I'd delete all except Boot0000/Bodhi UEFI, from within the BIOS, and ensure the BIOS has instruction that the Bodhi entry has maximum priority, whatever the BIOS happens to call it. There may be more than one location in BIOS that affects this. There's quite a bit of variability in the way UEFI BIOS work, and nomenclature used.

I would not be concerned with whether Windows boots or not until having the Bodhi Grub you want working as you want it. It should be able to load Windows once it works as it should.

madmax25 · 04-20-2019, 04:49 AM

Quote:

Originally Posted by mrmazda

...I'd delete all except Boot0000/Bodhi UEFI,...

This is the missing entry, at least from Bodhi's point of view and I wonder, how can I get it back there?

I'm starting to think, I better should format or even totally delete all of my Linux partitions and rebuild/reinstall everything from scratch,
hoping this will fix all of the issues I've been facing lately and I also hope, this will fix the entire content of the efi partition.

mrmazda · 04-20-2019, 05:56 AM

Quote:

Originally Posted by madmax25

This is the missing entry, at least from Bodhi's point of view and I wonder, how can I get it back there?

https://wiki.gentoo.org/wiki/Efiboot...g_a_boot_entry has an example.

Quote:

I'm starting to think, I better should format or even totally delete all of my Linux partitions and rebuild/reinstall everything from scratch, hoping this will fix all of the issues I've been facing lately and I also hope, this will fix the entire content of the efi partition.

Bulldozing a field to get rid of one weed.

madmax25 · 04-20-2019, 06:24 AM

I just checked the example, but I have to confess, this is confusing me too much.
I don't know what to enter to compose the wanted line, even after reading the example.

Quote:

Originally Posted by mrmazda

https://wiki.gentoo.org/wiki/Efiboot...g_a_boot_entry has an example.

Bulldozing a field to get rid of one weed.

Well, of course, it's a lot of work, but at least, I can be sure, everything is going to be alright again (hopefully!).

Besides, I want to find out, what's better, installing Bodhi first or Xubuntu first.

Btw. do you know how to find out if there's a 2nd installation of GRUB somewhere else on my UEFI computer?

mrmazda · 04-20-2019, 06:52 AM

Quote:

Originally Posted by madmax25

I just checked the example, but I have to confess, this is confusing me too much.
I don't know what to enter to compose the wanted line, even after reading the example.

Probably

Code:

sudo efibootmgr -c -d /dev/sda -p 1 -L "Bodhi" -l '\EFI\bodhi\bootx64.efi'

but possibly \EFI\bodhi\shimx64.efi, depending what's actually in /boot/efi/EFI/bodhi/. bootx64.efi is generic, while shimx64.efi provides secure boot service.

yancek · 04-20-2019, 08:44 AM

Your post 9 showed your EFI boot files which included EFI files for both Bodhi and Ubuntu so the first option to try was suggested in post 2, use efibootmgr to set the order you want. From the efibootmgr output in your most recent post, the following should work:

Code:

sudo efibootmgr -o 0000,0001,...

Replace the ... with the other numbers in the order you want them, comma separated and obviously, use sudo and that is a lower case letter O in the command, order.

You kept trying to re-install Grub when it was already installed for both Bodhi and Ubuntu. If you want the Bodhi Grub first, you need to either use efibootmgr or access your BIOS. As has been pointed out above, the BIOS settings for UEFI vary immensely among various manufacturers so methods vary.

I had this same problem last week trying to change the OS priority to another system with efibootmgr and it failed several times but I easily changed it in the BIOS.

Quote:

Here, in the 5th line, I don't understand, why is grub installed at /dev/sda (without a number)

The above comment from your earlier post 9 which shows the steps, sda is correct as shown in the output you posted mounting the / and efi partitions, explained also at the link below.

https://askubuntu.com/questions/8312...-efi-partition

Quote:

Then you install Linux2.
Now, Linux2 is the 1st one in GRUB, and so Linux2 is the default system, booting automatically.

Well, that is the default behavior but I have never installed any Ubuntu which did not give an option as to where to install Grub on a Legacy system but UEFI is different.

So with an EFI install, to change the boot order, first use efibootmgr (as root/sudo) and if that fails, you need to make the change in the BIOS.

madmax25 · 04-20-2019, 09:00 AM

Quote:

Originally Posted by yancek

If you want the Bodhi Grub first, you need to either use efibootmgr or access your BIOS.

Changing the boot order in BIOS doesn't work either.
I tried several times. No chance.

After changing the order, it says, it is changed, but it doesn't affect GRUB.

Another attempt to fix this also failed.
I tried the chroot method to install a fresh GRUB.
This is what I did (sda7 is where I installed Bodhi):

Code:

sudo mount /dev/sda7 /mnt
sudo mount /dev/sda1 /mnt/boot
sudo mount /dev/sda1 /mnt/boot/efi
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt
grub-install /dev/sda
update-grub

After the last command, the terminal is telling me:

Quote:

grub-probe: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.

but I cannot find a file called device.map anywhere.

At this point, I'm already so confused, I got no idea about what to do anymore, anyway.

madmax25 · 04-20-2019, 09:05 AM

mrmazda · 04-20-2019, 02:04 PM

Quote:

Originally Posted by madmax25

Changing the boot order in BIOS doesn't work either.
I tried several times. No chance.

After changing the order, it says, it is changed, but it doesn't affect GRUB.

This in addition to much of what you already tried suggests to me you have a corrupted NVRAM.

Quote:

Code:

...
grub-install /dev/sda
update-grub

Grub-install installs code into hidden portions of a MBR disk. That isn't how Grub-efi works. No code gets installed into boot sectors or MBR sectors in a UEFI environment. All you might get from such an attempt is a rebuild of grub.cfg. It doesn't fix NVRAM, which is what controls how the Grub menu you want gets found and loaded.

Quote:

After the last command, the terminal is telling me:

but I cannot find a file called device.map anywhere.

Grub and grub-efi are very different. Grub-efi doesn't use device.map. Try following the UEFI instructions on https://www.pcsuggest.com/grub-rescu...n_UEFI_systems or https://askubuntu.com/questions/9191...rupt-boot-uefi or just about any result from a web search for corrupt UEFI.

madmax25 · 04-20-2019, 02:31 PM

I gave up on fixing things, which made everything worse, anyway, and formated all my Linux partitions
with a following re-installation of Xubuntu 18.04.2 and Bodhi (this time 5.0, btw.).
Now, in my BIOS, I have only entries for Windows and Ubuntu, which is what it was like, before everything went out of control.
Now, it seems to be working again in the way I'm used to it (I will have a closer look at this later, in order to verify this).

But this leads me to another question:
I remember having issues with eepdater on an earlier attempt to install BL5.0.

I also remember a thread where this was fixed by some kind of a policy rule, but I cannot find this thread anymore.
Can somebody point me to it, please?

EDIT:
I'm talking about the issue, when eepdater is used, a terminal is also opened, which shouldn't happen.

yancek · 04-20-2019, 07:22 PM

Quote:

sudo mount /dev/sda1 /mnt/boot
sudo mount /dev/sda1 /mnt/boot/efi

I guess it doesn't matter as you have now formatted everything but I'm wondering exactly what you expected to happen with the above commands. You mounted sda1 twice to two different mount points. Whatever other problems you might have had, that will never work to accomplish what you wanted. You would have needed to eliminated the first mount above for starters.

I have no idea what 'eepdater' is so can't help with that. Good luck.

madmax25 · 04-20-2019, 08:01 PM

I meant the update tool of Bodhi, but it's not very important.
I can do without by using the terminal to get available updates.

So far it looks like everyting is working again.

It's just that I'm currently busy on reinstalling everything I need.