Mint Failure and on reboot stuck on grub.

Brian Alex

Member
Joined
Feb 28, 2025
Messages
82
Reaction score
51
Credits
790
Hello. This morning I went to use my Mint 22.3 (fully updated). I have "sleep" turned off so it was on the screen-saver automation. Pressing a key I was able to see the desktop (although It seemed washed out in appearance) but when I double-clicked an icon, nothing happened. I rebooted and was presented with the usual dual-boot menu with Mint the default (top) selection. I clicked "enter" as usual but nothing happened. I tried to move the selection down just to see if the keyboard was maybe not engaged and it was not. I could not change the selection. Since this is a wireless KB, I tried hard-wiring a different KB but still no action from the up or down keys.I shut it down by momentarily pressing the power button and proceeded to unplug the tower, press the " ON" button, plug it back in and press the ON button only to experience the same stuck and unresponsive grub menu. It was at this point that I realized I was Fd and that I would probably need to test out my recovery skills using a USB install stick, somehow access the system and get to the TimeShift program. I have close to zero confidence in doing this even though I have a "Back-up" (deja Dup) [edit: I see this is not a system BU tool] and an external TS USB. I was thinking this was going to be a long Easter Sunday. But then I had the idea that maybe if I left it in the boot menu long enough it would somehow work through the problem and boot in a much delayed manor. Viola, it finally did boot.
So just now I did a TS back 2 days and all is right, apparently. I have noticed lately (and currently I think) that occasionally when I double click a DT icon I get "opening (whatever). you can stop this by clicking cancel below" or some such. Also occasionally nothing happens at this point and I need to right click the icon and select "open with Firefox".

I have a few questions; 1) If this or some other issue occurs in the future, how exactly can I use journalctl or other means to figure out what is wrong? A good reference maybe if explanation is too difficult. 2) If I have to boot from a USB, how do I then access the TS on the root system of get the external USB TS to restore to the root system. Has anyone else seen this behavior or have some insight into this? Thanks -BA
 
Last edited:


Too early for me : what is a DT icon?
 
Dual boot...there's your problem.
1775432333464.gif
 
Dual boot...there's your problem. View attachment 31223
It doesn't really need to be (dual-boot) since I already chose Mint over Ubuntu. I just haven't figured out how to safely remove Ubuntu and the grub entry. If that is indeed a factor in this then I will hit the search engine and lose it forthwith. Thanks
 
Last edited:
I don't have problems because I never dual boot...in my Tower I have two SSDs...one has Mint Cinnamon 22.1...the other Cinnamon 22.2 with zero problems.

I also never upgrade...I always do a clean install for the same reasons. If I want to run another distro or windoze on the same drive...I use Virtualbox.
1775440428328.png

A VM is a file not a Drive and is isolated and safe.
1775440624035.gif
 
Thanks Bob. I think I'll do the same as you. I really do like this Linux Mint and I thought I was royally screwed this early AM. Maybe it was working through a fsck? If so, it would have been nice to have some sort of notification of this. Next time I'll just wait.
 
Maybe it was working through a fsck?
That will only happen if you put it in place.

You can enable a fsck to happen at boot time....but usually only necessary if you are having problems.

problems and Mint 22.3 are usually a contradiction....at the very most they rarely happen.

Just be sure of your installation procedure and the manner in which you make the usb stick bootable.
 
There is absolutely no problem with running dual-boot or more with Linux distros, I am living proof.

On this rig (Dell Inspiron laptop), I run 43 distros on the /dev/sda drive, 12 on the /dev/sdb drive, and 33 on the /dev/sdc drive, for a total of 88.

If, however, the dual-boot is with one Linux and one Windows, there can be issues whereby Windows does not like sharing with Linux.

The only extra precaution I take is having an ESP (EFI System Partition) on each drive - /dev/sda1, /dev/sdb1, and /dev/sdc1. In that way, I can drop in or drop out drives, and not lose functionality.

If you wish to dual (or more) boot, and/or be able to access Timeshift snapshots when a distro is on the fritz, I can help there, too.

Just sing out.

Cheers

Wizard
 
Yeah, I figured that, Bob...and lol, you jumped in with the quip before the OP explained he was talking all Linux. :)

Give yourself a wagging finger.

Wiz
 


Follow Linux.org

Members online


Top