5A corrupts eMMC (was 5A does not boot)

#1

I just received my 5A today, plugged in hdmi and power and … nothing. No blue LED, nothing on the screen, no activity as far as I can tell. I also bought a 16G eMMC module onto which I flashed the Dietpi image, zero activity whatsover.

I see the 5B board has a maskrom mode which would then be picked up by the computer to verify the board is not dead, but the 5A has no such feature(?).

Did I get a dead board or did I skip a step?

[updated details]
I’m using the 30W power supply and usb-c cord that raxda sells

Radax Rock 5A 在 Debian bootup
5a not boot with emmc, stack at loading debian
[230801] System Release Notice for ROCK 5A
5a not boot with emmc, stack at loading debian
#2

so you flash the image on the EMMC, which image do you flash,

This this the guide to 5A, you can refer to

#3

Sigh, stupid user error. I mistook the dietpi image for the 5B, not compatible with the 5A. Bloated debian image seems to be booting just fine. Sorry for the false alarm. Thank you.

#4

There is no such thing as bloated Debian. Its Debian image with more or with less starting packages. I guess then bloatware and sales BS must be coming from Dietpi. Point of open source is that work is done together, with common goals and code is reviewed, so BS is not spread really far … here even htop is patched to fool you … why do “developers” needs to patch htop? To support ideology or to add real value? If Debian is bloated, then Dietpi is super bloated.

#5

Don’t mind me, I come from Gentoo where computers have exactly what software I want and nothing more. Given that the stock debian image I’ve just installed for this rockpi 5a clocks in at 5gigs and the last dietpi setup I did was barely 1gig, you’ll have a hard time convincing me there isn’t unnecessary software included with the stock debian image FOR MY USECASE.

Anyways. After writing the B16 Debian image to emmc and booting it, it hangs with ext4 file corruption and the root partition is read-only. Reflashed the emmc a second time, verified the file system before putting it in the 5a, and it still ends up corrupting itself and going read-only on first boot. Just tried reflashing a third time and sure enough, read-only root partition after ext4 corruption on first boot.

1 Like
#6

Buildroot and Yocto is better way for that, but perhaps too complicated from end user perspective … Gentoo is trying to do something else, but I get your point.

If you want nothing more, then you should look what Dietpi provides without shame … Even calling home comes by default.

Comparing desktop images from vendors with server image is a terrible justification. Compare minimal Debian or better minimal Armbian, where Dietpi is taking the value from. Kernel / firmware is everything that is important and they are doing exactly nothing regarding this even they claim “support”. The rest is Debian packages + excessive branding, suspicious scripts / art that has nothing to improve OS functions. If some hardware related function (all what actually matters, the problem you have) works or not, its not related to Dietpi and often not to HW manufacturer (this forum) as hardware interface is not maintained by them.

#7

5A does have maskrom mode, but it’s tricky: you need to short two pins (in fact, holes), and use a USB-A to USB-A cable together with power… More info here.

#8

I’m going to RMA this 5A because it’s clear there’s something wrong. It consistently corrupts the file system on every boot. I’m pretty sure it’s the 5A because I can read & write the eMMC on my pc (through the eMMC-SD card adapter) all day and it doesn’t have any problem. But place the eMMC on the 5A and it’s corrupted.

I’ve even tried the Android image, and it too corrupts the various partitions on first boot (which never completes)

#9

Now this is interesting: I’ve got exactly the same problem with my unit, eMMC file system always gets corrupted on the first boot!
When I use microSD card, everything’s fine though…

#10

Interesting, I’m now trying to boot the 5a off of the eMMC-microSD interface but no luck, never goes blue.

#11

Did you put the SPI flash module back to the eMMC slot? It wouldn’t boot from microSD without it.

#12

I did put it back but are you sure it wont boot without it? I flashed the B16 radxa OS onto a microSD and it boots fine without the SPI module installed. Doesn’t corrupt itself either like the eMMC does.

#13

Oh, OK, maybe it’s only needed to boot from nvme then.

#14

We are trying to reproduce this now.

#15

Been using TF card on 5A just fine until I switched to eMMC and I found similar file system corruption. It usually happens shortly after the system starts, such as when using apt update. The eMMC module works fine on Rock 5B. I also tried the latest kernel “5.10.160-rockchip-rk3588” with no luck.

[  345.286190] blk_update_request: I/O error, dev mmcblk0, sector 14049280 op 0x1:(WRITE) flags 0x4800 phys_seg 32 prio class 0
[  345.337889] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:347: I/O error 10 writing to inode 266834 starting block 1756518)
[  345.338064] Buffer I/O error on device mmcblk0p1, logical block 1752064
[  345.338095] Buffer I/O error on device mmcblk0p1, logical block 1752065
[  345.338101] Buffer I/O error on device mmcblk0p1, logical block 1752066
[  345.338114] Buffer I/O error on device mmcblk0p1, logical block 1752067
[  345.338126] Buffer I/O error on device mmcblk0p1, logical block 1752068
[  345.338138] Buffer I/O error on device mmcblk0p1, logical block 1752069
[  345.338149] Buffer I/O error on device mmcblk0p1, logical block 1752070
[  345.338161] Buffer I/O error on device mmcblk0p1, logical block 1752071
[  345.338174] Buffer I/O error on device mmcblk0p1, logical block 1752072
[  345.338188] Buffer I/O error on device mmcblk0p1, logical block 1752073
#16

It kinda feels like it’s getting corrupted anytime there’s a write operation (those are buffered and cached, of course, which is why it takes a few seconds before queued writes are flushed).

#17

Exactly. The last time it failed was when downloading the linux firmware package.

#18

These are the same error messages that my board was spitting out, usually followed by a message saying the filesystem has been put in read-only mode.

So we seem to have 3 confirmed cases of the 5A corrupting eMMC cards on writes. We still don’t know if it’s a hardware or software issue.

RadxaYuntian, any luck replicating it?

#19

Can someone who has not had problems with their 5A and an eMMC say so?

#20

idk if this was said here already but u do realise that the emmc that comes with the rock 5a is not an freely emmc for storage but an spi flasher thing ?

Meaning you need your own / other emmc to flash in your Rock 5A image.