Manual checkup on software raid1

  • Greetings everyone,


    I am planning on upgrading the storage capacity of my omv-server. But before I do that I would like to run a check on my software raid1 mirror (ext4) that contains all my data files. Yes I know that the current setup is generally frowned upon. That’s why my upgrade will be a btrfs raid1 or a snapraid setup. Btw, the mirror hasn’t failed me thus far.


    Anyways is it safe to perform a fsck on a active array or perhaps another way? Do I need to specify additional parameters in the command:


    sudo fsck /dev/md0


    The array is currently clean:


    Version : 1.2

    Creation Time : Tue Mar 23 21:14:02 2021

    Raid Level : raid1

    Array Size : 2930134464 (2794.39 GiB 3000.46 GB)

    Used Dev Size : 2930134464 (2794.39 GiB 3000.46 GB)

    Raid Devices : 2

    Total Devices : 2

    Persistence : Superblock is persistent


    Intent Bitmap : Internal


    Update Time : Sun Aug 29 17:33:23 2021

    State : clean

    Active Devices : 2

    Working Devices : 2

    Failed Devices : 0

    Spare Devices : 0


    Consistency Policy : bitmap


    Name : openmediavault:DataRaid1 (local to host openmediavault)

    UUID : 0fc23ec2:e1cbd729:96af3181:7854fba8

    Events : 6695


    Number Major Minor RaidDevice State

    0 8 0 0 active sync /dev/sda

    1 8 16 1 active sync /dev/sdb



    Thank you for the help.

  • Yes I know that the current setup is generally frowned upon

    It's never frowned upon, the question is why, when the a simpler option is to use one drive for data and the second as a backup.

    But before I do that I would like to run a check on my software raid1 mirror

    Why? are you experiencing file system problems, this would be unnecessary

    or a snapraid setup

    If your data files are 'in use' on a regular basis then snapraid is not an option.

    Raid is not a backup! Would you go skydiving without a parachute?

  • I am aware of that option nowadays. To use sync for backing up the main data drive periodically to another drive.


    No filesystem problems experienced. I meant it as a precautionary measure before moving the data over the new array. By coincidence one of my wd red 3TB disks start to make clicking an clunking sounds this morning! Kind of freaky that this happened just after I posted something here. I did a comparison of the smart values:


    WD-WCC4N1LL838J

    SMART Attributes Data Structure revision number: 16

    Vendor Specific SMART Attributes with Thresholds:

    ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE

    1 Raw_Read_Error_Rate POSR-K 200 200 051 - 0

    3 Spin_Up_Time POS--K 179 177 021 - 6008

    4 Start_Stop_Count -O--CK 100 100 000 - 102

    5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0

    7 Seek_Error_Rate -OSR-K 200 200 000 - 0

    9 Power_On_Hours -O--CK 074 074 000 - 19246

    10 Spin_Retry_Count -O--CK 100 100 000 - 0

    11 Calibration_Retry_Count -O--CK 100 253 000 - 0

    12 Power_Cycle_Count -O--CK 100 100 000 - 87

    192 Power-Off_Retract_Count -O--CK 200 200 000 - 56

    193 Load_Cycle_Count -O--CK 167 167 000 - 100876

    194 Temperature_Celsius -O---K 118 108 000 - 32

    196 Reallocated_Event_Count -O--CK 200 200 000 - 0

    197 Current_Pending_Sector -O--CK 200 200 000 - 0

    198 Offline_Uncorrectable ----CK 200 200 000 - 0

    199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0

    200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 0



    WD-WCC4N3ANT71D

    SMART Attributes Data Structure revision number: 16

    Vendor Specific SMART Attributes with Thresholds:

    ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE

    1 Raw_Read_Error_Rate POSR-K 200 200 051 - 6

    3 Spin_Up_Time POS--K 181 176 021 - 5950

    4 Start_Stop_Count -O--CK 091 091 000 - 9586

    5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0

    7 Seek_Error_Rate -OSR-K 200 200 000 - 0

    9 Power_On_Hours -O--CK 074 074 000 - 19297

    10 Spin_Retry_Count -O--CK 100 100 000 - 0

    11 Calibration_Retry_Count -O--CK 100 253 000 - 0

    12 Power_Cycle_Count -O--CK 100 100 000 - 94

    192 Power-Off_Retract_Count -O--CK 200 200 000 - 61

    193 Load_Cycle_Count -O--CK 172 172 000 - 85551

    194 Temperature_Celsius -O---K 117 106 000 - 33

    196 Reallocated_Event_Count -O--CK 200 200 000 - 0

    197 Current_Pending_Sector -O--CK 200 200 000 - 0

    198 Offline_Uncorrectable ----CK 200 200 000 - 0

    199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0

    200 Multi_Zone_Error_Rate ---R-- 200 200 000 - 1



    Start_Stop_count on the first disk is 102, on the second it is 9586. Given all the symptoms this drive is going to fail soon right?


    I've decided to go btrfs raid1 with the new 4 TB Ironwolfs. Thank you for you reply.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!