Power & Source of Big Ideas

NanoPC-T4 errors writing to emmc

Moderators: chensy, FATechsupport

Hi,

I having trouble with my new T4 when I come to writing to the built in emmc memory. I'm trying to create partitions and filesystems on it.

I get errors like below especially when creating filesystem and/or writing files to it. I managed to get ext4 to appear to work by running fsck after mkfs. However copying files just fails.

I'm running ArchLinux (5.16.13-1-aarch64-ARCH).

Any clues or pointers would helpful - thanks.

Code: Select all

[  652.049727] EXT4-fs (mmcblk2p1): warning: mounting fs with errors, running e2fsck is recommended
[  652.051509] EXT4-fs (mmcblk2p1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[  653.553256] mmc2: running CQE recovery
[  653.556827] mmc2: running CQE recovery
[  653.560598] mmc2: running CQE recovery
[  653.565298] mmc2: running CQE recovery
[  653.566582] I/O error, dev mmcblk2, sector 33936 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 0
[  653.569781] mmc2: running CQE recovery
[  653.573905] mmc2: running CQE recovery
[  653.577335] mmc2: running CQE recovery
[  653.579856] I/O error, dev mmcblk2, sector 34960 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 0
[  653.584189] mmc2: running CQE recovery
[  653.587013] mmc2: running CQE recovery
[  653.590482] mmc2: running CQE recovery
[  653.593025] I/O error, dev mmcblk2, sector 37008 op 0x1:(WRITE) flags 0x800 phys_seg 127 prio class 0
[  653.597527] mmc2: running CQE recovery
[  653.600320] mmc2: running CQE recovery
[  653.602177] I/O error, dev mmcblk2, sector 35984 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
[  673.588890] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[  715.763613] mmc2: running CQE recovery
[  715.769298] mmc2: running CQE recovery
[  715.772039] mmc2: running CQE recovery
[  715.773795] I/O error, dev mmcblk2, sector 1081376 op 0x1:(WRITE) flags 0x800 phys_seg 53 prio class 0
[  715.774802] Aborting journal on device mmcblk2p1-8.
[  721.891828] EXT4-fs error (device mmcblk2p1): ext4_journal_check_start:83: comm kworker/u12:2: Detected aborted journal
[  721.893346] EXT4-fs (mmcblk2p1): Remounting filesystem read-only
[  721.893921] EXT4-fs (mmcblk2p1): ext4_writepages: jbd2_start: 9223372036854775807 pages, ino 30; err -30
[  752.751207] EXT4-fs warning (device mmcblk2p1): ext4_clear_journal_err:5575: Filesystem error recorded from previous mount: IO failure
[  752.752316] EXT4-fs warning (device mmcblk2p1): ext4_clear_journal_err:5577: Marking fs in need of filesystem check.
I eventually found a solution or workaround for this problem. It seems to be to with support for HS400 mode. Removing the two HS400 references in the device tree (rk3399-nanopc-t4.dtb) stopped the errors occurring.

There were hints in my investigation that this occurs with recent linux kernels.

Who is online

In total there are 7 users online :: 0 registered, 0 hidden and 7 guests (based on users active over the past 5 minutes)
Most users ever online was 5185 on Wed Jan 22, 2020 1:44 pm

Users browsing this forum: No registered users and 7 guests