RN102 disk1 Degrading after adding new disk for raid1

Question

RN102 fw:6.10.6 with WD-Red 3TB, working 6yrs with spotless logs.
Installed another WD-Red 3TB in slot 2, and changed X-RAID to FLEXRAID = Raid1.
Immediately I got a yellow warning that disk1 was degraded, and resync started, and this lasted approx. 8hrs.
After complete resync I still got the "Degraded" warning, but the volume seems to work OK.
Have tried both restart (+ automaticly full resync again), Scrub and Defrag succesfully, but Disktest stopped with an errorwarning.

What to do?
If no easy out, can I seperate the raid1 and go back to the original single disk, or can I move the new resynced disk to slot1 as master, or do I need to wipe and reinstall both disks (I have backup on another RN102).
Rgds and tks. in advance
Søren H. /Denmark

Marc_V · Answer

shedemand&nbsp;
&nbsp;
Since you are using RAID1, Disk 2 is an exact copy of the 1st. You have to make sure to make a backup of your data before doing anything else. It's good that the resync was completed before Disk 1 failed.We need to check if Disk 1 has errors by going to diskinfo.log or smart_history.log. You can do that by downloading the zip log file from the NAS.
&nbsp;
If you will move the disk bay location, make sure your NAS is off.
&nbsp;
You cannot go back to the previous configuration you have to destroy the volume then set it up again.
&nbsp;
It would be better to check Disk 1 first if it failed. You can take it out and check it on a PC using vendor tools like Seatools to check the drive and request for RMA if it is eligible.
&nbsp;
If there's no issue with the disk or if you have a replacement or it has been replaced, then doing a factory reset is an option to start fresh with both disks inserted. It will be on X-raid RAID1.
&nbsp;
Replacing disk1 with a new 3TB disk is also an option. Otherwise, you will have to set up the healthy drive again to use it as a single drive.
&nbsp;
HTH

StephenB · Answer

sda (the first disk) failed the most recent self test, and is showing read errors in the kernel log (perhaps other places).
&nbsp;
One thing you could try is powering down the NAS, and removing that disk.&nbsp; Then boot the system up in read-only mode, and verify that you can access the data.&nbsp; If you can, the step after that would be to make sure you have a current backup.

shedemand · Answer

Marc_V&nbsp;Tks MarcI'll try various solutions and report back.It may take a couple of weeks, - I'm quite busy at the momentRgdsSøren

shedemand · Answer

Marc_V&nbsp;I have gone through the extended logs, but allthough I haved worked in IT right up to my pension, I do not know exactly what I should be looking for in the logs.So I take the liberty to forward extracts from some of the log-postings on my OneDrive:https://1drv.ms/u/s!Anw_yRjl5NKvisNoMkkgLZ_v59a3Tw?e=2EU0kPIf you wonder why the NAS name is "Cody", the reason is that my first NAS many years ago was a Buffalo-NAS&nbsp; :-)Re backup: I have a continuous backup of Cody on another RN102 placed at a different physical location on my LAN for security reasons (fire, theft), since Cody holds all kinds of personal documents, videos and photos for me and my wife.Thanks in advance for your helpSøren