franknfurter2
October 16th, 2018, 07:37 PM
Hallo,
a few days ago I did a normal update of my 18.04 LTS Desktop System, which I some weeks ago upgraded from 16 (Flavour Ubuntu Studio). It is a dual boot System with Windows 10 on the same SSD.
When I have restarted it after update, GRUB menu hasn't shown up any more and the only way to start has been via BIOS Menu and the only system starting was Windows. So I had build a Live USB Stick, started from there and run boot-repair tool as mentioned here:
https://help.ubuntu.com/community/Boot-Repair
The default repair button results in message telling me, to switch off SecureBoot. But i did not. I did' a repair anyway which did not work. And after a while i had the idea, that it might have to do with unsigned kernal files. So I moved the newest kernal files in a subfolder under /boot/ and suddenly, I was able to start Ubuntu from SSD again (I do not know anymore, if it was from the BIOS menu or if the GRUB Menu was showing).
Within that system, I installed boot-repair again and started a repair without switching SecureBoot off.
A reboot than shows a new GRUB Menu with a lot of entries. I then copied the newest kernal files (4.15.0-36) back into the /boot folder (4.15.0-36) and run boot-repair again.
Next reboot has show up the GRUB Menu and it was able to start lowlatency kernal 4.15.0-36.
Now, I see three problems:
Why was Boot Loader corrupted and why does it now work with the newest kernal
Why are there so many (mainly Windows) entries in the GRUB menu
How to clean up the menu and the files and subfolders of /boot
You can find the boot-repair system report here (http://paste.ubuntu.com/p/pgmvbFjG6d/)
Which of the files (bkpbootx64.efi, bootx64.efi, fbx64.efi, fwupx64.efi, grubx64.efi, mmx64.efi, shimx64.efi, bootmgfw.efi, bootmgr.efi and memtest.efi) is really needed? Who has installed them?
If someone knows a good How-To which explains all this. Let me know.
So, can someone help me with this?
a few days ago I did a normal update of my 18.04 LTS Desktop System, which I some weeks ago upgraded from 16 (Flavour Ubuntu Studio). It is a dual boot System with Windows 10 on the same SSD.
When I have restarted it after update, GRUB menu hasn't shown up any more and the only way to start has been via BIOS Menu and the only system starting was Windows. So I had build a Live USB Stick, started from there and run boot-repair tool as mentioned here:
https://help.ubuntu.com/community/Boot-Repair
The default repair button results in message telling me, to switch off SecureBoot. But i did not. I did' a repair anyway which did not work. And after a while i had the idea, that it might have to do with unsigned kernal files. So I moved the newest kernal files in a subfolder under /boot/ and suddenly, I was able to start Ubuntu from SSD again (I do not know anymore, if it was from the BIOS menu or if the GRUB Menu was showing).
Within that system, I installed boot-repair again and started a repair without switching SecureBoot off.
A reboot than shows a new GRUB Menu with a lot of entries. I then copied the newest kernal files (4.15.0-36) back into the /boot folder (4.15.0-36) and run boot-repair again.
Next reboot has show up the GRUB Menu and it was able to start lowlatency kernal 4.15.0-36.
Now, I see three problems:
Why was Boot Loader corrupted and why does it now work with the newest kernal
Why are there so many (mainly Windows) entries in the GRUB menu
How to clean up the menu and the files and subfolders of /boot
You can find the boot-repair system report here (http://paste.ubuntu.com/p/pgmvbFjG6d/)
Which of the files (bkpbootx64.efi, bootx64.efi, fbx64.efi, fwupx64.efi, grubx64.efi, mmx64.efi, shimx64.efi, bootmgfw.efi, bootmgr.efi and memtest.efi) is really needed? Who has installed them?
If someone knows a good How-To which explains all this. Let me know.
So, can someone help me with this?