RAID 10 Status Clean, Resyncing (PENDING) (PENDING)?

    • OMV 2.x
    • RAID 10 Status Clean, Resyncing (PENDING) (PENDING)?

      Hey guys. I created a raid array yesterday and let it re sync and have came back to the raid array's status say pending. Does this mean the re sync has failed? My main question is what does this status mean? Am I able to create the file system for the raid array?

      Source Code

      1. Version : 1.2
      2. Creation Time : Tue May 16 20:37:37 2017
      3. Raid Level : raid10
      4. Array Size : 1953262592 (1862.78 GiB 2000.14 GB)
      5. Used Dev Size : 976631296 (931.39 GiB 1000.07 GB)
      6. Raid Devices : 4
      7. Total Devices : 4
      8. Persistence : Superblock is persistent
      9. Update Time : Wed May 17 10:14:54 2017
      10. State : clean, resyncing (PENDING)
      11. Active Devices : 4
      12. Working Devices : 4
      13. Failed Devices : 0
      14. Spare Devices : 0
      15. Layout : near=2
      16. Chunk Size : 512K
      17. Name : screamserver:ScreamRaid (local to host screamserver)
      18. UUID : ddaf6947:8c3f9552:e1ec6bbc:4be83769
      19. Events : 164
      20. Number Major Minor RaidDevice State
      21. 0 8 16 0 active sync /dev/sdb
      22. 1 8 32 1 active sync /dev/sdc
      23. 2 8 0 2 active sync /dev/sda
      24. 3 8 48 3 active sync /dev/sdd
      Display All
    • How to clear up pending resync on RAID array

      This problem can be identified by inspecting kernel ring buffer and array states. Notice that background reconstruction started on the md1 array, but it is in auto-read-only state and resynchronization is pending.

      # dmesg
      [...]
      [ 1.312811] md: md0 stopped.
      [ 1.313511] md: bind<sdb1>
      [ 1.313601] md: bind<sda1>
      [ 1.314335] md: raid1 personality registered for level 1
      [ 1.314572] md/raid1:md0: active with 2 out of 2 mirrors
      [...]
      [ 1.516790] md: md1 stopped.
      [ 1.517457] md: bind<sdb2>
      [ 1.517545] md: bind<sda2>
      [ 1.518947] md/raid1:md1: not clean -- starting background reconstruction
      [ 1.518949] md/raid1:md1: active with 2 out of 2 mirrors
      [...]

      # cat /proc/mdstat
      Personalities : [raid1]
      md1 : active (auto-read-only) raid1 sda2[0] sdb2[1]
      4203104 blocks super 1.2 [2/2] [UU]
      resync=PENDING
      md0 : active raid1 sda1[0] sdb1[1]
      973524352 blocks super 1.2 [2/2] [UU]
      unused devices: <none>

      Execute following command to switch array to read-write state and begin resync process.
      # mdadm --readwrite /dev/md1

      Transition will be immediately visible by inspecting array states.
      # cat /proc/mdstat
      Personalities : [raid1]
      md1 : active raid1 sda2[0] sdb2[1]
      4203104 blocks super 1.2 [2/2] [UU]
      [=>...................] resync = 8.1% (333952/4203104) finish=1.3min speed=47707K/sec
      md0 : active raid1 sda1[0] sdb1[1]
      973524352 blocks super 1.2 [2/2] [UU]
      unused devices: <none>

      The end result can be verified after synchronization process finishes.
      # cat /proc/mdstat
      Personalities : [raid1]
      md1 : active raid1 sda2[0] sdb2[1]
      4203104 blocks super 1.2 [2/2] [UU]
      md0 : active raid1 sda1[0] sdb1[1]
      973524352 blocks super 1.2 [2/2] [UU]
      unused devices: <none>
      Transition messages will be stored in kernel ring buffer.

      # dmesg
      [171485.722209] md: md1 switched to read-write mode.
      [171485.722895] md: resync of RAID array md1
      [171485.722898] md: minimum _guaranteed_ speed: 1000 KB/sec/disk.
      [171485.722901] md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for resync.
      [171485.722905] md: using 128k window, over a total of 4203104k.
      [171558.652298] md: md1: resync done.
      [171558.764453] RAID1 conf printout:
      [171558.764457] --- wd:2 rd:2
      [171558.764460] disk 0, wo:0, o:1, dev:sda2
      [171558.764463] disk 1, wo:0, o:1, dev:sdb2

      fonte: blog.sleeplessbeastie.eu/2015/…ing-resync-on-raid-array/