Mmc failure possible?

Industrial
1

Hello.
From some days, an ARM device with node-red give me some error because of EROFS error during write on mmc card.
I see on journal the evolution in EXT4-fs functionality.
The following are the relative lines from the installation to now.

After some days :
Oct 04 17:11:15 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
Oct 04 17:11:15 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
One month later :
Nov 06 17:51:49 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): INFO: recovery required on readonly filesystem
Nov 06 17:51:49 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): write access will be enabled during recovery
Nov 06 17:51:49 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): orphan cleanup on readonly fs
Nov 06 17:51:49 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): 1 orphan inode deleted
Nov 06 17:51:49 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): recovery complete
Nov 06 17:51:49 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
Nov 06 17:51:49 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
Some days ago :
Apr 01 10:04:43 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): INFO: recovery required on readonly filesystem
Apr 01 10:04:43 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): write access will be enabled during recovery
Apr 01 10:04:43 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): recovery complete
Apr 01 10:04:43 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
Apr 01 10:04:43 iot-sthm25 kernel: EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
Apr 01 10:04:49 iot-sthm25 kernel: EXT4-fs error (device mmcblk0p1): htree_dirblock_to_tree:1003: inode #50303: comm dbus-daemon: Directory block>

You think that can be a mmc failure? Change the mmc can be a solution?
BR

2

Do those appear after the power is suddenly removed?
If not then replace it.

3

Hello.
The last line :
kernel: EXT4-fs error (device mmcblk0p1): htree_dirblock_to_tree:1003: inode #50303: comm dbus-daemon: Directory block>
appears continuosly when system runs.
I look to journal because now is not possible write files from node-red.
It is not possible also to modify node programs because of this error :
"Error saving flows: EROFS: read-only file system, unlink '/root/.node-red/.flows.json.backup'"
"Error: EROFS: read-only file system, unlink '/root/.node-red/.flows.json.backup'"
This happens because after mmc failure all unit became read only, probably for defective mmc.
BR

4

Always have a space card to hand, it is the first thing to check.

5

Or a spare card.
This isn't the Artemis forums @TotallyInformation :wink:

1 Like
6

Haha, rushing a reply as I went off to cook tea. :smiley:

Still, I'm sure that the Artemis crew have plenty of spare space cards!

2 Likes