Boot-repair ran twice- why is my screen still black after grub menu?
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Boot-repair ran twice- why is my screen still black after grub menu?
Please help!
I think as a result of installing new Intel graphics software on my ubuntu-mate 16.04 lts system I get a black screen after the grub menu.
I created a live boot-repair disk and ran it twice.
ok thanks. But if this IS the issue (I have 2 separate SSD's one has Windows 10 installed so I am wondering if boot-repair was confused?)
how does a boot loader suddenly go missing?
I need to know for future reference and hopefully prevent happening again
Your boot repair output shows that you have Ubuntu installed using UEFI/GPT. When using UEFI, you do not need nor should you have any code in the MBR. The BIOS needs to be set to boot UEFI and it will then look to the EFI partition. Your boot repair output shows a 1TB drive on which you have Ubuntu and a 120GB drive which looks like it could be a Live Ubuntu system. The only possible sign of windows is the messed up partition sda4. Was that a windows or is windows on another drive? The efi partition on the 1TB drive shows only Ubuntu efi files although there are references at the bottom of the script to windows EFI files. With windows, you do need to use UEFI if you have GPT partitions. You might get a better understanding of this at the Ubuntu documentation site below.
Thanks. If I've messed up the partitioning, just curious then why everything was fine for several weeks. Could my full root partition have something to do with my issue?
A full root partition will almost always be a problem to boot. You could use a Live DVD/flash drive to mount sda3 and see if there are directories/files you can remove. You haven't clarified where your windows is/was. The only possible partition for windows would be sda4 but there is no way to know if that was it. Did you have windows on another hard drive? If you had windows on another physical drive, did you have a separate EFI partition on that drive because there are no windows EFI files showing on the main (1TB) drive although they are referenced in the boot repair output. You also have an entry for windows in the grub.cfg file on sda3 showing it on "/dev/nvme0n1p2" which would be an SSD drive. There is nothing in the boot repair output showing this drive.
You're using GPT on the 1TB drive so you need to have your computer booting EFI for windows. Have you set the SSD to first boot priority as suggested at the bottom of the boot repair output?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.