Hello,
today i received the 32gb eMMC module. I installed armbian on it (the build for the 4b as indicated on the armbian website). unfortunately fter a short time i get input output errors and the filesystem turns read only.
yes the problem will come back after a reflash of the emmc moduke. it just needs a few write operations like a apt upgrade.
it does not occur with a micro sd card.
i tried to migrate to nvme with armbian-install as alternative, but there systemd fails on boot with some stupidity and ends in an emergency shell.
I’m using a 33w usb-c PD adapter as power supply.
Is there somehow a debian minimal image officialle from radxa? i could only finde the xfce version, so i had to look for armbian
I’m having this issue as well, also on Armbian running the latest stable everything. It means you can’t install the OS from the SSD to emmc module due to the data corruption that occurs.
Hi, having the same issue with 2 Rock 4SEs with 32gb emmcs. Have tried both official images Debian and Armbian trunk from Radxa and armbian images direct from armbian. Under heavy load emmcs start erroring and eventually kernel remounts rootfs as read only. Can reduce errors by reducing CPU clock speed, but this is not a solution. Both sbcs work perfectly fine with same images running off microsd cards. Quite frustrating, have spent a decent number of hours trying to resolve issue.
I have the same issues with rock 4 se and 64GB emmc.
It boots after the freshly imaged debian/ubuntu/armbian etc images, but after it, when I try to install the graphical environment with tasksel it dies.
Is there any solution for that? I need the emmc boot, without it it is useless for me.
[ 74.111070] hdmi-audio-codec hdmi-audio-codec.6.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22
[ 461.374685] blk_update_request: I/O error, dev mmcblk1, sector 3179520 op 0x1:(WRITE) flags 0x4000 phys_seg 8 prio class 0
[ 461.375863] EXT4-fs warning (device mmcblk1p2): ext4_end_bio:345: I/O error 10 writing to inode 46288 starting block 397824)
[ 461.376118] Buffer I/O error on device mmcblk1p2, logical block 389120
[ 461.376928] Buffer I/O error on device mmcblk1p2, logical block 389121
[ 461.377697] Buffer I/O error on device mmcblk1p2, logical block 389122
[ 461.378506] Buffer I/O error on device mmcblk1p2, logical block 389123
[ 461.379277] Buffer I/O error on device mmcblk1p2, logical block 389124
[ 461.380056] Buffer I/O error on device mmcblk1p2, logical block 389125
[ 461.380824] Buffer I/O error on device mmcblk1p2, logical block 389126
[ 461.381591] Buffer I/O error on device mmcblk1p2, logical block 389127
[ 461.382402] Buffer I/O error on device mmcblk1p2, logical block 389128
[ 461.383176] Buffer I/O error on device mmcblk1p2, logical block 389129
[ 470.090454] blk_update_request: I/O error, dev mmcblk1, sector 3342336 op 0x1:(WRITE) flags 0x4800 phys_seg 11 prio class 0
[ 470.091818] EXT4-fs warning (device mmcblk1p2): ext4_end_bio:345: I/O error 10 writing to inode 46867 starting block 417931)
[ 470.092000] buffer_io_error: 502 callbacks suppressed
[ 470.092008] Buffer I/O error on device mmcblk1p2, logical block 409600
[ 470.092814] Buffer I/O error on device mmcblk1p2, logical block 409601
[ 470.093595] Buffer I/O error on device mmcblk1p2, logical block 409602
Then with tasksel select XFCe environment. And let the system try to install all thing. (If it is stuck at playmout, then just kill the install processes and continue with the given dpkg commant bye the system if you try to run apt-get -f install)
As other commenters have said, easy to reproduce, just run a larger apt upgrade or firmware upgrade through armbian-config. Another way I’ve found to reproduce the error is to simulate heavy write operations using dd command. dd if=/dev/zero of=/tmp/test1.img bs=1G count=5 oflag=dsync for example.
I also encountered this EMMC problem with Kernel 6.1.22 both on a RockPi 4B v1.4 and RockPi 4SE. The same image worked just fine on a RockPi 4B+ v1.73. The 4B+ uses an on-board EMMC module whereas the two failing boards use external EMMCs.
I tried to follow @abws’s advice first reverting the seemingly offending commits and in another attempt cherry-picking the commits mentioned in [1]. But in both cases the problem persists.
However, using the patch from [2] that limits EMMC max clock frequency to 150MHz solved the issue for me. Instead of patching the kernel device tree, setting max-frequency in a separate DT overlay is also viable.
I have to amend my own statement. I just bought a new Foresee 64GB eMMC module, flashed one of my images and booted up a RockPi 4b V1.4. Despite using an overlay to limit EMMC max clock frequency I see spurious TCN for tag errors and get lots of filesystem errors.
I tried some other patches, e.g. to disable eMMC command queue mode, but the problem persists.
Does Radxa see these errors with their provided images?
If not, does Radxa apply any special patches to get eMMC reliably working? I searched the Radxa Github repos for a while but didn’t see any obvious patches for the eMMC related device tree or drivers.
Edit: I tested all kernels from 6.1.22 to 6.1.27 and 6.3. They all have this issue.
exactamente por que usas el modulo emmc de 32 gb algun proyecto pesado? para comensar con algunos proyectos creo que basta y sobra con las memorias microSD