Zimaboard 832 goes read-only

ZimaBoard ZimaBoard - Support
1

I’m having a recurring issue where my file system switches to read-only mode after the board runs for a few minutes.

The first time I noticed this was while trying to install an app via the webGUI, and I got the following error in a brief popup:

{"message": "mkdir /tmp/casaos-compose-app-2205892483: read-only file system" }

Checking the logs via dmesg -w, I see this error being raised constantly:

systemd-journald[270]: Failed to write entry (21 items, 925 bytes), ignoring: Read-only file system

Rebooting the board doesn’t fix the issue.
On reboot, it complains that the file system is corrupted, dropping me into a busybox shell where I have to run fsck:

fsck -y /dev/mmcblk0p2

After the file system check, the system will boot up, but the issue reoccurs shortly after.

I’ve reinstalled the entire system, but the problem persists.

Here are some additional details:

  • OS: CasaOS v0.4.13 (latest)
  • Distro: Debian GNU/Linux 11 (bullseye)

Any ideas on how to resolve this?

2

additional log (when the issue starts)

[  131.427357] mmc0: cache flush error -110
[  131.427372] blk_update_request: I/O error, dev mmcblk0, sector 26499264 op 0x1:(WRITE) flags 0x20
800 phys_seg 1 prio class 0
[  131.427396] Aborting journal on device mmcblk0p2-8.
[  131.484047] EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:83: Detected aborted journ
al
[  131.484059] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
[  131.484696] EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:83: Detected aborted journ
al
[  131.484700] EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:83: Detected aborted journ
al