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


    root@openmediavault:~# cat /proc/mdstat

    • Offizieller Beitrag

    It isn't added to the array as an active device. mdadm --add /dev/md0 /dev/sdd1

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • 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

    • Offizieller Beitrag

    /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 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    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

    • Offizieller Beitrag

    What is the output of:


    cat /proc/mdstat
    mdadm --detail --scan --verbose

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • root@openmediavault:~# cat /proc/mdstat
    Personalities : [raid6] [raid5] [raid4]
    md0 : inactive sdc1[4](S) sdb1[3](S)
    3906266112 blocks super 1.2


    unused devices: <none>


    root@openmediavault:~# mdadm --detail --scan --verbose
    mdadm: md device /dev/md0 does not appear to be active.

  • 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

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!