Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 run a triple boot system: Mint 17, 18.3 and Windows 10 on a self-assembled desktop PC.
I have a constant problem on startup. I get a screen that says Grub cannot find my master drive and offers up rescue mode. Has anyone got any ideas what is causing this?
I have not changed any settings and the only thing I have done recently is to update my Mint 17 software.
Define "constant" - 100% of the time, or intermittently. How do you proceed to a usable system ?.
How many disks are involved - are any external (USB) disks ?. Go here, and do as it says, then post the RESULTS.txt
I had a similar problem but not caused the same way. For you, you said "after upgrade"; for me, it was "after new install".
In fact, I can still MAKE the problem happen because I managed a "work-around" - and haven't bothered to sort it out yet.
I believe it happens (for me, at least) because I installed distros with grub boot on the partitions on a UEFI booting system.
For me, the work-around is to immediately press ESC at boot. This drops me into the BIOS boot screen. I can choose one of the installed distros (for me, Antix, MX, ROSA (not Mint Rosa - ROSA10), Windows).
One of the distros will take me to it's GRUB boot list. From that list I can choose any distro to boot.
That Grub will auto-boot without problem from then on.
(If I pick a badly configured grub boot it will give me the Grub rescue error, just as you describe.)
No arguments from Members about this as a solution. This is only a work-around that works consistently - until some other measure can be applied.
My workaround is to select F12 (Gigabyte board) enter BIOS and re-select the PM drive. In effect I do not change anything, save and reboot.....this seems to work.
This morning I have switched on my PC and it has gone to the Grub menu as normal.
Colorpurple21859 & Boombaby - Your point re: USB is a good one. I did have a USB card and reader attached last week, so this might have had something to do with it. I'll monitor it and let you know how it goes - thanks.
Last edited by Gemmstone4291; 08-03-2018 at 01:00 AM.
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
Rep:
When you install a second Linux distro to bare metal, do not install grub. Rather, after the install, boot into the first Linux and run 'update-grub'. That will put the new Linux in the boot menu of grub.
Otherwise, each distro will be messing around with grub on upgrades.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.