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

#124

I’m running Armbian_23.8.3_Rock-5a_bookworm_legacy_5.10.160 on my 5A on the 32GB eMMC and encountering the same issues:

2023-11-22T04:32:30.647396+00:00 rock-5a kernel: [ 3249.196325] blk_update_request: I/O error, dev mmcblk0, sector 1634664 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0
2023-11-22T04:32:30.647469+00:00 rock-5a kernel: [ 3249.196340] blk_update_request: I/O error, dev mmcblk0, sector 1634664 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0
2023-11-22T04:32:30.647477+00:00 rock-5a kernel: [ 3249.196426] Aborting journal on device mmcblk0p1-8.
2023-11-22T04:32:30.660685+00:00 rock-5a kernel: [ 3249.210743] EXT4-fs error (device mmcblk0p1): ext4_journal_check_start:83: Detected aborted journal
2023-11-22T04:32:30.660739+00:00 rock-5a kernel: [ 3249.210752] EXT4-fs (mmcblk0p1): Remounting filesystem read-only
2023-11-22T04:32:30.660742+00:00 rock-5a kernel: [ 3249.210776] EXT4-fs (mmcblk0p1): failed to convert unwritten extents to written extents -- potential data loss!  (inode 279746, error -30)
2023-11-22T04:32:30.660747+00:00 rock-5a kernel: [ 3249.210954] EXT4-fs (mmcblk0p1): failed to convert unwritten extents to written extents -- potential data loss!  (inode 279747, error -30)
2023-11-22T04:32:30.660751+00:00 rock-5a kernel: [ 3249.211016] EXT4-fs (mmcblk0p1): failed to convert unwritten extents to written extents -- potential data loss!  (inode 279748, error -30)
2023-11-22T04:32:30.660755+00:00 rock-5a kernel: [ 3249.211071] EXT4-fs (mmcblk0p1): failed to convert unwritten extents to written extents -- potential data loss!  (inode 279749, error -30)
2023-11-22T04:32:30.661355+00:00 rock-5a kernel: [ 3249.211117] EXT4-fs (mmcblk0p1): failed to convert unwritten extents to written extents -- potential data loss!  (inode 279750, error -30)
2023-11-22T04:32:30.663963+00:00 rock-5a kernel: [ 3249.212815] EXT4-fs (mmcblk0p1): failed to convert unwritten extents to written extents -- potential data loss!  (inode 279852, error -30)
2023-11-22T04:32:30.663997+00:00 rock-5a kernel: [ 3249.212927] EXT4-fs (mmcblk0p1): failed to convert unwritten extents to written extents -- potential data loss!  (inode 279743, error -30)
2023-11-22T04:32:30.664001+00:00 rock-5a kernel: [ 3249.213000] EXT4-fs (mmcblk0p1): failed to convert unwritten extents to written extents -- potential data loss!  (inode 279744, error -30)
2023-11-22T04:32:30.664003+00:00 rock-5a kernel: [ 3249.213101] EXT4-fs (mmcblk0p1): failed to convert unwritten extents to written extents -- potential data loss!  (inode 279745, error -30)

I am seeing this after running for ~10 minutes. I was able to install packages and do some work, but then it suddenly switches to read-only mode. This has happened twice now, the first time I was running Ubuntu so I switched to Armbian to see if that would help.
Anyone else still having issues? Am I running the right version?

#125

There’s a known quirk on rockchip’s emmc controller against certain emmc modules.
You can rebuild the kernel or image with this patch and see if it helps.

3 Likes
#126

I have problem by using 128Go EMMC avec writing image, it don’t boot on ROCK5A, the same image boot in EMMC 64go module.
HELP

#127

There is, in general, no way to fix this, workarounds like the above exist but may fail.

#128

we are trying to reproduce this issue at our office

#129

Hello,
Thanks reply.
have you got a solution ?
Regards