spare rebuilding after swapping out drive

    • OMV 2.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • spare rebuilding after swapping out drive

      Hi guys,

      I swapped out a drive which was reporting some bad sectors for a new drive.
      The drive started rebuilding fine, but when it was finished it keeps reporting "spare rebuilding"

      I'm not sure what's wrong and Google hasn't brought a solution...
      Do you guys have an idea how to fix this?

      Thanks in advance

      root@openmediavault:~# mdadm --detail /dev/md0
      Display Spoiler

      Version : 1.2
      Creation Time : Fri Nov 20 00:28:55 2015
      Raid Level : raid5
      Array Size : 3905767424 (3724.83 GiB 3999.51 GB)
      Used Dev Size : 1952883712 (1862.42 GiB 1999.75 GB)
      Raid Devices : 3
      Total Devices : 3
      Persistence : Superblock is persistent

      Intent Bitmap : Internal

      Update Time : Thu Sep 1 20:51:47 2016
      State : active, degraded
      Active Devices : 2
      Working Devices : 3
      Failed Devices : 0
      Spare Devices : 1

      Layout : left-symmetric
      Chunk Size : 512K

      Name : manfred:0
      UUID : 051c3493:cd0e06a3:6b8cbbcb:c89c797c
      Events : 14713631

      Number Major Minor RaidDevice State
      4 8 49 0 spare rebuilding /dev/sdd1
      1 8 17 1 active sync /dev/sdb1
      3 8 33 2 active sync /dev/sdc1

      root@openmediavault:~# cat /proc/mdstat
      Display Spoiler

      Personalities : [raid6] [raid5] [raid4]
      md0 : active raid5 sdd1[4] sdb1[1] sdc1[3]
      3905767424 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [_UU]
      bitmap: 0/15 pages [0KB], 65536KB chunk

      unused devices: <none>
    • It appears that the device is busy, but when I try to stop the device it's not part of the raid.

      root@openmediavault:~# mdadm --add /dev/md0 /dev/sdd1
      mdadm: Cannot open /dev/sdd1: Device or resource busy

      root@openmediavault:~# mdadm --stop /dev/sdd1
      mdadm: /dev/sdd1 does not appear to be an md device
    • /dev/sdd1 isn't a mdadm device. It is an array member. So, you can't stop it.

      mdadm --stop /dev/md0
      mdadm --assemble --verbose --force /dev/md0 /dev/sd[bcd]1
      omv 4.1.0 arrakis | 64 bit | 4.14 backports kernel | omvextrasorg 4.1.2 plugins source code and issue tracker -

      Please don't PM for support... Too many PMs!
    • I had to unmount the md0 because a process was using it with "umount -l /dev/md0"
      But now it appears the device does not have a superblock, mounted or not (mount -a) and can't be assembled.

      root@openmediavault:~# mdadm --assemble --verbose --force /dev/md0 /dev/sd[bcd]1
      mdadm: looking for devices for /dev/md0
      mdadm: no RAID superblock on /dev/sdd1
      mdadm: /dev/sdd1 has no superblock - assembly aborted

      root@openmediavault:~# mdadm --add /dev/md0 /dev/sdd1
      mdadm: cannot get array info for /dev/md0
    • Will I be able to recover the array or am I toast?

      I found some commands by Googling but I don't want to lose my data if possible :/

      EDIT: I was able to get the array back up with:
      root@openmediavault:~# mdadm -A --scan
      mdadm: /dev/md0 has been started with 2 drives (out of 3) and 1 rebuilding.

      So now I am back to the beginning, with the one drive stuck in "spare rebuilding /dev/sdc1"-mode

      The post was edited 1 time, last by nubdubdidubdub ().