Grub Rescue Issue After Last Update [Solved]

[pbear]

To be honest I can't remember which tool I used to make the live usb for this computer. It was either MX Live USB Maker in MX Tools or Etcher. I used both for my 2 computers and the for the full OS usb. Now I can't remember which I used on which. I could for good measure just burn a whole new one and start over, and replace the hard drive. Also, I ran the memory test from the full install usb and it ran perfectly. I forgot to change it from legacy back to UEFI in the bios, though, before I ran it.

Hard drive: Right, as discussed, your symptoms indicate that should be replaced.

Memory test: What happens if you run it from the full install USB drive in UEFI mode? I'm wondering whether there's some quirk with the computer which causes the UEFI mode test to fail. Nothing you can do about it (would suggest some sort of obscure bug in the firmware), but useful to know. Also, would remove the cloud over the live USB, i.e., not a glitch in the burn after all.

Live USB: If you redo, use the MX Live USB Maker. If you run into an issue down the road, better to have used the official OS tool. You can run the app from the full install USB or your 32-bit computer.

[dragonfly]

From the full install usb:
When I go into the bios under the boot menu tab and change boot mode to UEFI, the boot priority option disappears. When exiting bios it goes to an error message, red letters in a white box, "Secure boot image failed to verify with *SECURITY VIOLATION*. Press any key to continue." OK is the only button. Clicking OK brings up the Welcome to MX Linux screen with options, but does not load the software and goes back to error message.

When I select Legacy Support in the boot mode under the boot tab, it brings back the boot priority and allows me to select UEFI First. It does not show the error message and loads the software. It also runs the memory test. Selecting Legacy Support seems to automatically disable secure boot, selecting UEFI enables it. Basically UEFI loads nothing, Legacy Support with UEFI First works (the onscreen images appear slightly smoother), Legacy Support with Legacy First works (the onscreen images appears a touch less smoother). Is it okay to use the mixed option for Legacy Support and UEFI First together, or should it be all legacy? Sole UEFI isn’t working.

I did make another live usb from scratch with a spare usb I had and used the MX tools since I couldn’t remember what I burned the first one with. All these suggestions are great! I am learning a lot.

[pbear]

What you want is UEFI mode with secure boot disabled. You were able to boot in UEFI mode previously (e.g., for the system report), so just a matter of remembering how (or finding it again by trial-and-error).

[dragonfly]

Ok, I will try to find that and set it.

[dragonfly]

Sorry for the delay. I finally had the chance to install the new hard drive and reinstall the OS. From what I can tell it looks like it is not using Legacy. Seems to be working smoothly so far so good-

[pbear]

No worries. There are a couple ways to tell the boot mode. Perhaps the easiest is to look at Quick System Info (on Menu). Boot mode should be the last line on the report. It's also mentioned at the end of the Machine stanza (the second one, after System), which also indicates the firmware date (that's how I knew earlier yours is only five years old).

By the way, knock wood, you have run updates, right? That's where it fell down last time.

[dragonfly]

Glad to report all is going well with the new hard drive and no problems with the updates. Actually, everything is working better than it did before. I learned a lot, including how to be smarter managing my computer system and file back ups. I appreciate the MX Linux community and the patience getting me through this process, and just the smoothness of MX Linux itself. I am able to get my work done again. Thanks!

[pbear]

Congratulations, glad it worked out. Now would be a good time to mark the thread as Solved. I'd say Post #41 is where we decided the hard drive was the problem.

[MikeR]

Two nit-picks:
1. The danger with putting all your trust in Timeshift comes up if/when (hoping never) you have a disk crash. You'll end up with a perfect but unreachable backup.
2. I find that easier than remembering "Raising Elephants..." is "BUSIER" (i.e. more busy) <-- *Backwards*. works for me, but choose your own acronym.