Some devices can't find rootfs when booting from eMMC
I am not sure if this is actually a kernel issue or if it's something weird in uboot, but I will place it here, so I don't have to replicate it to all uboot packages of devices affected.
Some devices show something like this when booting from eMMC:
:: running hook [udev]
:: Triggering uevents..
:: running hook [plymouth]
:: performing fsck on '/dev/mmcblk2p2'
:: running hook udev]
:: Triggering uevents..
:: running hook [plymouth]
:: performing fsck on '/dev/mmcblk2p2':
fsck.ext2: Input/output error while trying to open /dev/mmcblk2p2:
The superblock could not be read or does not describe a valid
filesystem.
If the device is valid and it really contains an
filesystem (and not swap or ufs or something else), then it
is corrupt, and you might try running e2fsck with an alternate
e2fsck -b 8193 (device)
or
e2fsck -b 32768 ‹device>
ERROR: fsck failed on
* /dev/mmcblk2n2
:: mounting
' /dev/mmcblk2n2
on real root
mount: /new root: can't read superblock on /dev/mncblk2p2.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off
[rootfs ]#_
indicating that it can't find the root partition to read. The exact same images works without issue when booted from SD card on the same device.
This is a list of devices known, or suspected, to have this issue:
- RockPro64
- Rock Pi 4 B (and likely also C model)
- Radxa Zero
- Quartz64 Model A
- Pinebook Pro (might on new installs, but it works fine on an updated install)