Read-only problem

[mikedhoore]

Space is not the issue, only 5GB in use ...

I'm now looking in to kern.log and find this from the last days before read-only-"crash"

Code:

Apr  1 20:37:12 MDserver64 kernel: [1038414.257579] EXT4-fs (mmcblk0p7): error count since last fsck: 4
Apr  1 20:37:12 MDserver64 kernel: [1038414.266661] EXT4-fs (mmcblk0p7): initial error at time 1520438366: ext4_journal_check_start:56
Apr  1 20:37:12 MDserver64 kernel: [1038414.275943] EXT4-fs (mmcblk0p7): last error at time 1520447884: ext4_remount:4710
Apr  2 20:38:59 MDserver64 kernel: [1124923.760669] EXT4-fs (mmcblk0p7): error count since last fsck: 4
Apr  2 20:38:59 MDserver64 kernel: [1124923.779625] EXT4-fs (mmcblk0p7): initial error at time 1520438366: ext4_journal_check_start:56
Apr  2 20:38:59 MDserver64 kernel: [1124923.798711] EXT4-fs (mmcblk0p7): last error at time 1520447884: ext4_remount:4710
Apr  3 07:34:54 MDserver64 kernel: [1164279.633485] mmcblk0: error -110 sending status command, retrying
Apr  3 07:34:54 MDserver64 kernel: [1164279.664787] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x900
Apr  3 07:34:54 MDserver64 kernel: [1164279.674269] mmcblk0: status not valid, retrying timeout
Apr  3 12:49:29 MDserver64 kernel: [1183155.075634] mmcblk0: error -110 sending status command, retrying
Apr  3 12:49:29 MDserver64 kernel: [1183155.101534] mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x900
Apr  3 12:49:29 MDserver64 kernel: [1183155.120492] mmcblk0: status not valid, retrying timeout

Also here is the startup log (i'm not so good at it :p )
https://pastebin.com/VVdr2fC0

So this is also from today

Code:

Apr  4 17:54:50 MDserver64 kernel: [86809.605166] EXT4-fs (mmcblk0p7): error count since last fsck: 6
Apr  4 17:54:50 MDserver64 kernel: [86809.624101] EXT4-fs (mmcblk0p7): initial error at time 1520438366: ext4_journal_check_start:56
Apr  4 17:54:50 MDserver64 kernel: [86809.643169] EXT4-fs (mmcblk0p7): last error at time 1522763019: ext4_journal_check_start:56