Booting from '[Distro]' failed: Verify it contains/points to a valid 64-bit UEFI OS

Support Linux Support
1

So I updated to the most recent MrChromebox firmware and it seems to have broken booting to Linux off of the internal SSD. Previously I was running Ubuntu but after the firmware update, it just broke and spit out the error mentioned in the title. I can boot multiple different distros from a USB drive. I’ve tried Ubuntu(again), Pop_OS(has a specific bug where it can only see 14.9GB of my storage, but that existed before this, so eh), Debian 13, LMDE 7, Linux Mint, Ultramarine Linux, Aurora, and Zorin, but once I’m done with the installation they all suffer from the same error. Their respective entries appear in the boot menu but result in the error, and if I try to go to the boot manager to boot from a file, the menu is blank.

Seeing how I’m not the only one to encounter this issue in the past day, could this be a bug in the firmware that slipped through the latest release, or is it just a coincidence?

The chromebook I use is an ASUS Chromebook Plus CX34, with the boardname Marasov. If anymore info is needed I’ll respond ASAP.

2

what type of storage does your device have?
what firmware version was working?
did you back up the old firmware before flashing?

3

The storage type is an SSD. GNOME Disk Utility specifically gives it the name of MICRON MT128GBCAV2U31, if that helps.

The last firmware version that was working was the MrChromebox-2503.0 release and updating jumped to the latest 2509.1 release as I missed a couple updates, and sadly I didn’t make a backup before updating. Definitely a good idea in hindsight as it would be shorter than downgrading back to the stock firmware then going back to the Chromebox firmware

4

going back to stock and re-flashing is going to get you exactly where you are now, a pointless waste of effort.

5

Got it. So, is there anything I can do at the moment, or is this a bug in the firmware and I have to wait for it to be fixed?

6
  • you can manually download and flash the older firmware
  • you can flash a debug build and help me debug it
7

Sadly my schedule is a bit too tight for me to reliably help you debug the firmware. Where do I download older firmware images?

8

Alright, after digging for a while longer, I ended up being able to download an older firmware image by looking through sources.sh on your github to see how and where the firmware files are downloaded and then flashed it. Now I’m able to properly boot off of the internal SSD.

9

I would have at least liked to get a boot log from the non-working firmware to see where the issue was =(

10

If you’d like a log, it’s really no trouble for me to install the newer firmware to get a log then downgrade again. I just need to know how to get the log.

11

No, you need flash a debug build for generate the log files.