System Details
- Device: Boten
- OS: Linux
- Firmware Type: UEFI Full ROM
- Firmware Version: MrChromebox-2606.1 (07/14/2026)
- Internal storage type: eMMC
Summary of the Issue
When trying to boot an OS from a microSD card I get some random errors from the linux kernel. This is not the case when booting it through an USB adapter or on a different chromebook (ASUS Apel). I can also boot an OS normally from the eMMC disk but this gives me limited storage
Steps to Reproduce
-
Install the ROM software.
-
Put a microSD card in the computer slot.
-
Try booting an OS from the microSD card.
Expected Behavior
Linux should boot from the SD card.
ERROR: device ‘UUID=d4558f43-dfbd-4a7d-85a0-3fbd19c033f4' not found. Skipping fsck.
mount: /new_root: can't find UUID=d4558f43-dfbd-4a7d-85a0-3fbd19c033f4.
ERROR: Failed to mount 'UUID=d4558f43-dfbd-4a7d-85a0-3fbd19c033f4' on real root
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
The errors I get btw.
booting from SD is hit or miss, too many variables. the edk2 SD driver is 1/10th of the size of the Linux one, due to all the device-specific quirks.
1 Like
ah alright thanks, so i assume i just can’t do much about this? btw grub loads just fine and the reader also works later on in linux. i also have an issue with side volume buttons but ig it may also just be impossible.
if grub loads fine from the SD card, then edk2/firmware isn’t an issue. most likely your initrd doesn’t have SD card support, and so it can’t find the root fs