Filesystem modification, read-only filesystem and emmc0 logs
Problem
We have been using numerous Up Squared Boards since 2020. On our Up2Boards, Ubuntu 20.04 is running with kernel version 5.15.0-71-generic. Recenly we had some problem with logs which weren't be written to the storage hardware. I had checked syslog and turned out these belows logs were present, preventing our program from writting.
logs
kernel: [ 453.189298] mmc0: mmc_select_hs400 failed, error -84 kernel: [ 453.189727] mmc0: mmc_hs400_to_hs200 failed, error -110 kernel: [ 543.361872] mmc0: cache flush error -110 kernel: [ 543.361894] blk_update_request: I/O error, dev mmcblk0, sector 60097648 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0 kernel: [ 543.361935] Aborting journal on device mmcblk0p2-8. kernel: [ 543.362313] mmc0: mmc_hs400_to_hs200 failed, error -110 kernel: [ 543.363365] EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:83: comm systemd-journal: Detected aborted journal kernel: [ 543.363435] EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:83: comm rs:main Q:Reg: Detected aborted journal kernel: [ 543.377308] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
HW Specification
CPU
processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 92 model name : Intel(R) Pentium(R) CPU N4200 @ 1.10GHz stepping : 10 microcode : 0x28 cpu MHz : 2267.052 cache size : 1024 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 21 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch cpuid_fault cat_l2 ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust smep erms mpx rdt_a rdseed smap clflushopt intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts md_clear arch_capabilities vmx flags : vnmi preemption_timer posted_intr invvpid ept_x_only ept_ad ept_1gb flexpriority apicv tsc_offset vtpr mtf vapic ept vpid unrestricted_guest vapic_reg vid ple shadow_vmcs bugs : spectre_v1 spectre_v2 spec_store_bypass bogomips : 2188.80 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management:
Memory
total used free shared buff/cache available Mem: 7.6Gi 1.6Gi 4.0Gi 311Mi 2.0Gi 5.5Gi Swap: 2.0Gi 0B 2.0Gi
Disk
Disk /dev/mmcblk0: 58.25 GiB, 62537072640 bytes, 122142720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 2F1E8F6D-CD11-4FAC-A321-4D677EC5FA54 Device Start End Sectors Size Type /dev/mmcblk0p1 2048 1050623 1048576 512M EFI System /dev/mmcblk0p2 1050624 122140671 121090048 57.8G Linux filesystem
Since not every machine has this errors, but from time to time we have faced same issues.
Until today we have followed the process of unmount-mount -> fsck -> reboot. But this seems not the right solution for us.
Could there be any problem with emmc?
Any ideas from who also had encountered the same problem?
Comments
-
Hi @samuel9509
Not sure if there is a problem with emmc.
Could you please provide the serial number (Cxxxx) to me??
Or take a photo of the board.Best Regards,
Harry Chiu -
Hello @HarryChiu
Where could I find the serial number? Can it be achived by command through terminal? -
Hi @samuel9509
There are serial number stickers on the board and packaging box.
Best Regards,
Harry Chiu