Volume dead after disk replacement

[kenneth84]

So I got a message I had a faulty disk, so i replaced the disk.

The new disk start syncing and finished (Volume: Volume data is resynced.).
a few moments later i get the message the disk 1 is offline and 3 goes from online to resync (see screenshots).

After a reboot all the disk seem to work ok but my volume is gone.

Is there a way to try and restore the volume, in older post there is mentioned to be able to get payed support but i don't get the option to activate it for my NAS if i try to purchase a contract i get the message no contracts available

added screenshots of the logs and the paid support issue

[kenneth84]

added extra screenshots

[Marc_V]

@kenneth84

Welcome to the Community!

Were you able to download the logs? It would be best to contact Support since you got your volume inactive but we need to make sure your drives are all healthy by checking the logs or by doing a disk check. 

You may want to try contacting them via Phone as well. I will PM you the number

HTH

[kenneth84]

@Marc_V 
Yes I have the logs,

I've put them here

<redacted>

So do i best to contact support through phone strait away or do want to look at the logs yourself?

[StephenB]

---

@kenneth84 wrote:

I've put them here

---

Don't post them publicly (there is some information leakage).  I've redacted your link.

You can send a private message to @Marc_V using the envelope icon in the upper right of the forum page..  Include a link to this thread and also your dropbox link.

FWIW, the WD30EFAX is an SMR disk, which might be part of the problem here.

I did take a look at the log zip before I redacted the link.  While I can't see what caused the rapid toggle between ONLINE to RESYNC on sdc, I am seeing the errors on disk 1. There are a lot of errors like this in kernel.log:

Sep 23 21:19:47 ReadyNas6 kernel: md/raid:md127: read error not correctable (sector 5648173648 on sda3).
Sep 23 21:19:47 ReadyNas6 kernel: md/raid:md127: read error not correctable (sector 5648173656 on sda3).
Sep 23 21:19:47 ReadyNas6 kernel: md/raid:md127: read error not correctable (sector 5648173664 on sda3).
Sep 23 21:19:47 ReadyNas6 kernel: md/raid:md127: read error not correctable (sector 5648173672 on sda3).
Sep 23 21:19:47 ReadyNas6 kernel: md/raid:md127: read error not correctable (sector 5648173680 on sda3).
Sep 23 21:19:47 ReadyNas6 kernel: md/raid:md127: read error not correctable (sector 5648173688 on sda3).
Sep 23 21:19:47 ReadyNas6 kernel: md/raid:md127: read error not correctable (sector 5648173696 on sda3).
Sep 23 21:19:47 ReadyNas6 kernel: md/raid:md127: read error not correctable (sector 5648173704 on sda3).
Sep 23 21:19:47 ReadyNas6 kernel: md/raid:md127: read error not correctable (sector 5648173712 on sda3).
Sep 23 21:19:47 ReadyNas6 kernel: md/raid:md127: read error not correctable (sector 5648173720 on sda3).

These run until Sep 23 21:21:16.

So it looks like the combination of the resync/online issue with disk 3 combined with the errors on disk 1 took your volume off-line.  Disk 3 dropped out briefly (making the volume temporarily degraded), and disk 1 failed while it was degraded (making it dead).

Marc_V might be able to find more clues in the log zip.