Announcement

**Qqmike** · Nov 23, 2016, 11:03 AM

Some ideas and comments:

Not sure what that filesystem error is, do you know? sda5

I'm surprised Boot-Repair didn't repair the boot!

Strategy: Somehow, get booted into Kubuntu; once there, re-install GRUB2 from the Kubuntu Konsole command line by running two commands:
sudo grub-install
sudo update-grub

To get booted into Kubuntu, perhaps try Rod Smith's popular and useful little program called rEFInd. For tips and links, see my
https://www.kubuntuforums.net/showth...l=1#post372221
Btw, rEFInd is an excellent program to install or keep handy (like on a live CD or USB), just in case you find yourself with booting problems.

Another way to re-install GRUB2 is from a live CD/DVD/USB. For tips on that, see my
https://www.kubuntuforums.net/showth...l=1#post374017
Thus, you would run a live Kubuntu DVD/USB, and from that live session, using Konsole you would run commands to chroot into the not-working Kubuntu (on your hard drive) and re-install GRUB in that live session. Then re-boot the PC to see if, in fact, you did successfully re-install GRUBs from your live DVD/USB session.

I think I'd try rEFInd first, but it's up to you. Again, I'm surprised Boot-Repair didn't work because Boot-Repair simply re-installs GRUB2 for you in its live session, just like you would, say, using chroot (as I mentioned above).

My general how-to on UEFI booting (and fixing problems) is
https://www.kubuntuforums.net/showth...l=1#post379977

(Op-ed ... Seems that Windows is often the culprit in these matters ... but we already know that, right?

I'll try to be around, but may be off getting things ready for a holiday here (Thanksgiving), will try to check in as much as possible; and there are several guys here proficient in fixing these things, too.))

**vinnywright** · Nov 23, 2016, 03:57 PM

it looks to me ,,,,,and just my guess mind you .

that at least 2 things have happend hear ,,,,first you installed windows second ,,,,,this is sure to ruin your linux install if it's on the same drive and it's the boot drive,,, windows will wipe grub out as part of it's install .

AND some how your linux install partition /sda5 got corrupted and cant be mounted ,,,and because it could not be mounted the Boot-Repair USB could not fix it ,,

I ,,,, would use a Gparted cd/USB and recreate the partition on sda5 (no resizing) reformat it and then reinstall linux to it ,,,,,,,,,,,or wait and see if someone knows some trick to rewrite the partition table and potentially save the data .

VINNY

**Callisto** · Nov 23, 2016, 04:11 PM

@Qqmike: thanks for the links! I have been trying to fix it with rEFInd, but no luck so far. Will check more in detail the others links you gave me and see what happens. I agree with what you say about boot-repair: for what I have read, it fixes dual boot every time, but in my case it just does not work. I saw that sda5 is the partition where kubuntu is installed, why is broken, I do not know.

@vinnywright: thanks for your message. No, I installed Kubuntu after Windows. I learned the hard way many years ago, best thing is to install Kubuntu after Windows. I am not so worry about the data, as it is a fresh Kubuntu installation, I could erase the partition and try again.

**Callisto** · Nov 23, 2016, 05:04 PM

Ok, it is fixed! I think running rEFInd helped, since it copied the files to the /boot/efi directory. But afterwards, it was still booting directly to Windows. I noticed that withing the BIOS there was an option to point out the correct file for the efi booting. I selected the /EFI/ubuntu/shimx64.efi, gave it a name, and in the boot order, selected that option as first. And voila, it went to grub and I could select my OS. Still, strange repair-boot didn't not fix that. I guess it depends on the brand of the laptop?

Thanks guys!

**Qqmike** · Nov 23, 2016, 05:12 PM

Agree with Vinny -- best to fix that broken Linux partition.

rEFInd, when booted, will show you ALL the bootable partitions/OSs it sees in the computer's UEFI firmware line-up. Sometimes it is not obvious what those choices represent, but you can guess at them until you get though the list of the top 5 choices offered in rEFInd's boot menu. If it saw a valid Linux entry in the UEFI boot choices, it would certainly offer it to you, as Linux's boot files are easy to spot.

Sounds like that broken filesystem is preventing a good installation of GRUB2 files, or the links from your Kubuntu OS to the GRUB UEFI boot files (in the ESP--EFI System Partition, I think sda2--105 MB System Partition that was set up by Windows (which is OK that Windows set it up for your computer, no problems with Windows doing that)).

**Qqmike** · Nov 23, 2016, 05:15 PM

Ok, it is fixed!

Great! (We cross-posted, Posts #5 and #6) Something confused Boot-Repair--it does happen, for sure. And you correctly used your UEFI firmware to identify a UEFI-bootable choice: good work!

**Callisto** · Nov 23, 2016, 05:22 PM

Thanks for your help! Your links on all the EFI/UEFI stuff really helped. Will keep them for future references, just in case

**Qqmike** · Nov 24, 2016, 04:43 PM

Still, strange repair-boot didn't not fix that. I guess it depends on the brand of the laptop?

Different laptops makers may provide their own versions of UEFI firmware; and some firmware is defintely buggy or quirky or even non-functioning at times, or not very accommodating. I have found ASUS to be excellent for their UEFI firmware. I have no personal experience with Acer.

Also, you can look at the ESP, the EFI System Partition, and see what has been put in there by someone, someone like the PC maker or the Windows OS.

Your ESP is sda2, and you can see all sorts of stuff, where OEM refers to Acer:

Code:

 /dev/sda2 1,230,848 1,435,647 204,800 [B]EFI System partition[/B]
 ...
 ...
 File system: vfat
Boot sector type: Windows 8/2012: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: 
Boot files: /EFI/Boot/bootx64.efi /EFI/ubuntu/MokManager.efi 
/EFI/ubuntu/fwupx64.efi /EFI/ubuntu/grubx64.efi 
/EFI/ubuntu/shimx64.efi 
/EFI/Microsoft/Boot/bootmgfw.efi 
/EFI/Microsoft/Boot/bootmgr.efi 
/EFI/Microsoft/Boot/memtest.efi 
/EFI/[B]OEM[/B]/Boot/bootmgfw.efi /EFI/OEM/Boot/bootmgr.efi 
/EFI/[B]OEM[/B]/Boot/memtest.efi 
/boot-sav/log/2016-11-21__12h46boot-repair11/sda2/bootx
64.efi 
/boot-sav/log/2016-11-21__13h06boot-repair14/sda2/bootx
64.efi

Also, the maker may have placed a certain ordering on the boot managers/boot loaders listed in the ESP. You can use efibootmgr -v to see the ordering (as per my how-to I linked to above); and you can change that boot order yourself.

So, yes, the PC maker is involved in how your UEFI firmware works. But using tools like efibootmgr and rEFInd, and some tricks discussed in my how-to and elsewhere (e.g., Rod Smith's website), you have a lot of control over how your PC boots.

Announcement

No Grub after Kubuntu Installation

No Grub after Kubuntu Installation

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment