Posts by Darcu

    I pulled the drive out of my NAS and put it to my Desktop PC (have Windows and Linux running there).

    With Windows: can't initialize the drive. Can't format/whipe and when I try to set a New volume I get I/O error (input/output).

    With Linux still the same but SMART says that everything is fine. I am in warranty and I will send it to WesternDigital. Hope that I got a new one. Did not understand why SMART is fine...

    Have to buy a ESD-Bag. I Have read that WD won't accept Warranty without this bag.. So it will take some days

    I backup my RAID.
    So I tried to wipe the drive I got:


    okay thanks for your help so far.

    I think I do this:

    I search for some (external) HDD's (maybe some friends can help) and I will do my Backup seperated in different HDD's. This will take several days and it will cost a lot of time and nerves.

    After that I will wipe /dev/sdd. If this does not help I will reinstall OMV again and try to add the drive again. If this does not help aswell, I will wipe all three drives and set a new RAID. Then BackUp goes to the new RAID.

    I will report..

    you'll have to, and lets hope it works because that is all I can think of

    before i do it:

    I do not understand that the Wiping helps with this problems:

    root@MEDIASERVER:~# mdadm --readwrite /dev/md127
    mdadm: failed to set writable for /dev/md127: Device or resource busy

    root@MEDIASERVER:~# mdadm --stop /dev/md127
    mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process, mounted filesystem or active volume group?


    I am not sure if I understand you right:

    I have written down my SERIAL-No. from the WEBGUI. I search for the SERIAL-No of my "fault-disk" sdd physically and disconnect this drive from SATA-Port and energy?

    What to do next? I am not sure what you mean with wipe the drive. Formatting? Formatting with my DESKTOP PC and after format back to the NAS and add it to array?


    I test all ports using only the omv OS drive. Every Port works. I reach the WEBGUI and did a apt-get update & apt-get upgrade via SSH. Works fine with every PORT :/

    Before I tested the PORT's, I did a S.M.A.R.T. test with sdd:

    If the Ports are okay, it has to be the disk?

    :/ i changed all three SATA-cables for the HDD's but no difference. Still the same error when I try to recover /dev/sdd in the WEBGUI.

    Maybe give it a try to add the disk with the SSH. Is it:

    mdadm --add /dev/md127 /dev/sdd


    Next step would be to change SATA ports on the mainboard, but now I am struggeling:

    For example

    sda --> SATA-Port 1 (works acutally -->OS)

    sdb --> SATA-Port 2 (works acutally)

    sdc --> SATA-Port 3 (works acutally)

    sdd --> SATA-Port 4 (works not)

    e. g. I would try to change sdb to SATA-Port 4 and sdd to SATA-Port 2:

    Maybe SATA-Port 4 is broken and OMV does not recognize sdb but sdd on SATA-Port 2: So sdc is the only disk with is in the RAID, but OMV tries to connect sdd automatical to the RAID, but my data structure on the RAID has changed the last weeks only using sdb & sdc.

    I hope you know what I mean?

    Is it dangerous. My RAID is not a backup. If I loose the RAID, I will loose a lot of data :(

    Another option: Buy a new motherboard?


    no :(

    Should I try to change SATA cable? Or switch SATA-ports on my Motherboard (I have only 4 SATA for my four drives).

    root@MEDIASERVER:~# cat /proc/mdstat
    Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [ra id10]
    md127 : active raid5 sda[0] sdb[1]
    27344500736 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/2] [UU_]
    bitmap: 28/102 pages [112KB], 65536KB chunk
    unused devices: <none>

    after reboot:

    the good news: the Raid is shown again. (it was mounted automatically)

    the bad news: when I try to recover /dsv/sdd via WEBGUI it is the same error than in post #1 --> Failed to write metadata :/

    first of all: Thanks for your fast replies!

    I disabled SMB

    Then i tried to mdadm --stop... and stopped docker. I didn't install docker so far. So couldn't loaded.

    root@MEDIASERVER:~# mdadm --stop /dev/md127
    mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process, mounted filesystem or active volume group ?
    root@MEDIASERVER:~# systemctl stop docker
    Failed to stop docker.service: Unit docker.service not loaded.
    root@MEDIASERVER:~# umount /dev/md127
    root@MEDIASERVER:~# mdadm --stop /dev/md127
    mdadm: stopped /dev/md127
    root@MEDIASERVER:~# mdadm --readwrite /dev/md127
    mdadm: error opening /dev/md127: No such file or directory

    umount and stop seem to work, but now it can't find the directory