Hi everyone,
A few days ago, my Raid 6 array turn in read-only mode, but stay clean.
dmesg gave me this:
Code
Aborting journal on device md0-8.
EXT4-fs error (device md0): ext4_journal_check_start:61: Detected aborted journal
EXT4-fs (md0): Remounting filesystem read-only
EXT4-fs error (device md0): ext4_journal_check_start:61: Detected aborted journalcat /proc/mdstat
Code
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
md0 : active raid6 sdn[1] sdm[6] sdl[11] sdj[0] sdk[10] sdh[9] sdi[12] sdg[7] sde[3] sdf[2] sdd[4]
26371215360 blocks super 1.2 level 6, 512k chunk, algorithm 2 [11/11] [UUUUUUUUUUU]
bitmap: 1/22 pages [4KB], 65536KB chunk
unused devices: <none>mdadm -D /dev/md0
Code
/dev/md0:
Version : 1.2
Creation Time : Tue Oct 22 20:48:02 2019
Raid Level : raid6
Array Size : 26371215360 (25149.55 GiB 27004.12 GB)
Used Dev Size : 2930135040 (2794.39 GiB 3000.46 GB)
Raid Devices : 11
Total Devices : 11
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Tue Mar 10 02:00:11 2020
State : clean
Active Devices : 11
Working Devices : 11
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Name : BigNAS:Stock (local to host BigNAS)
UUID : 9977ac4c:8a43bc3d:6f19fabb:3e9def45
Events : 67193
Number Major Minor RaidDevice State
0 8 144 0 active sync /dev/sdj
1 8 208 1 active sync /dev/sdn
2 8 80 2 active sync /dev/sdf
3 8 64 3 active sync /dev/sde
4 8 48 4 active sync /dev/sdd
11 8 176 5 active sync /dev/sdl
6 8 192 6 active sync /dev/sdm
7 8 96 7 active sync /dev/sdg
12 8 128 8 active sync /dev/sdi
9 8 112 9 active sync /dev/sdh
10 8 160 10 active sync /dev/sdkOn this array, I have only one ext4 partition (named Stock) .
df -Th | grep "^/dev"
Code
/dev/sdc1 ext4 79G 7.6G 67G 11% /
/dev/sdb1 ext4 234G 19G 216G 8% /srv/dev-disk-by-label-AppData
/dev/sda1 ext4 2.7T 23G 2.7T 1% /srv/dev-disk-by-label-Downloads
/dev/md0 ext4 25T 14T 12T 55% /srv/dev-disk-by-label-Stock
So, after some search, I run
e2fsck -fy /dev/md0
Code
e2fsck 1.44.5 (15-Dec-2018)
Warning! /dev/md0 is mounted.
Stock: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (2977662371, counted=2974215716).
Fix? yes
Free inodes count wrong (411474438, counted=411474417).
Fix? yes
Stock: ***** FILE SYSTEM WAS MODIFIED *****
Stock: 577039/412051456 files (3.9% non-contiguous), 3618588124/6592803840 blocksAfter a reboot, everything is good. My Raid array is clean, my filesystem is writable.
Every HDD of this array is good on Smart Status.
But after a random time, it turn on read-only and I have to remake e2fsck and reboot.
I have this error about 1 time a day, so it's not very practical...
Is there a way to fix this??