NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN716x
Jan 04, 2023Aspirant
ReadyNAS 716X data- Two volumes after Resync
System: Readynas 716X F/W: 6.10.8 Old HDDs: 6TBx6 (WD Red) New HDD: 8TBx1 (WD Red) Raid 5 (X-Raid) I have recently experienced some issues with my Readynas system. I found out that I had to r...
- Jan 06, 2023
RN716x wrote:
Is it asking for an input here?
root@MaQBaLiNAS:~# cat /etc/mdadm/mdadm.conf
CREATE owner=root group=disk mode=0660 auto=yes
This is the same as the file on my system, so nothing unusual here.
RN716x wrote:
mdadm: NOT forcing event count in /dev/sdc3(3) from 11031 up to 19055
mdadm: You can use --really-force to do that (DANGEROUS)
mdadm: /dev/md/data-0 assembled from 4 drives - not enough to start the array.
mdadm: No arrays found in config file or automaticallyThis is telling you that /dev/sdc3 is missing a lot of writes - so it is seriously behind the other drives in the array.
- You could proceed with --really-force instead of force. You could end up with a lot of data loss/corruption if you do that.
- Another other option is go back to SDA. Power down, remove SDC, insert the SDA. Power up, and try the same mdadm command again, and see if the event count gap is smaller. If you go this route, you should definitely mount the volume as read-only - as we know that SDA is failing, and writes will likely only accelerate that. Also they would increase the event gap between sdc and the rest of the array (making going back to SDC even more risky).
This isn't an obvious decision. SDA likely will have a smaller event gap, but we already know it has unreadable sectors. Plus it might fail when you try to offload data. Still, I think it is likely the best path (with read-only mounting).
A variant of (2) is to clone SDA, and insert the clone. The cloning process will skip over any unreadable sectors on the original. The benefit of the variant is that there will be no bad sectors detected on the clone (which is a mixed blessing, as bad sectors do give you some information on file corruption). The risk is that the original will completely fail during the cloning process.
Either way (1, 2, or 2 variant), you'd copy off as much data as you can, do a factory default with the two new drives installed in place of SDA and SDC. You'd reconfigure the NAS at that point, and then restore the files from the backup.
RN716x
Jan 06, 2023Aspirant
Is it asking for an input here?
root@MaQBaLiNAS:~# cat /etc/mdadm/mdadm.conf
CREATE owner=root group=disk mode=0660 auto=yes
Then
root@MaQBaLiNAS:~# mdadm --assemble --scan --force
mdadm: NOT forcing event count in /dev/sdc3(3) from 11031 up to 19055
mdadm: You can use --really-force to do that (DANGEROUS)
mdadm: /dev/md/data-0 assembled from 4 drives - not enough to start the array.
mdadm: No arrays found in config file or automatically
StephenB
Jan 06, 2023Guru - Experienced User
RN716x wrote:
Is it asking for an input here?
root@MaQBaLiNAS:~# cat /etc/mdadm/mdadm.conf
CREATE owner=root group=disk mode=0660 auto=yes
This is the same as the file on my system, so nothing unusual here.
RN716x wrote:
root@MaQBaLiNAS:~# mdadm --assemble --scan --force
mdadm: NOT forcing event count in /dev/sdc3(3) from 11031 up to 19055
mdadm: You can use --really-force to do that (DANGEROUS)
mdadm: /dev/md/data-0 assembled from 4 drives - not enough to start the array.
mdadm: No arrays found in config file or automatically
This is telling you that /dev/sdc3 is missing a lot of writes - so it is seriously behind the other drives in the array.
- You could proceed with --really-force instead of force. You could end up with a lot of data loss/corruption if you do that.
- Another other option is go back to SDA. Power down, remove SDC, insert the SDA. Power up, and try the same mdadm command again, and see if the event count gap is smaller. If you go this route, you should definitely mount the volume as read-only - as we know that SDA is failing, and writes will likely only accelerate that. Also they would increase the event gap between sdc and the rest of the array (making going back to SDC even more risky).
This isn't an obvious decision. SDA likely will have a smaller event gap, but we already know it has unreadable sectors. Plus it might fail when you try to offload data. Still, I think it is likely the best path (with read-only mounting).
A variant of (2) is to clone SDA, and insert the clone. The cloning process will skip over any unreadable sectors on the original. The benefit of the variant is that there will be no bad sectors detected on the clone (which is a mixed blessing, as bad sectors do give you some information on file corruption). The risk is that the original will completely fail during the cloning process.
Either way (1, 2, or 2 variant), you'd copy off as much data as you can, do a factory default with the two new drives installed in place of SDA and SDC. You'd reconfigure the NAS at that point, and then restore the files from the backup.
- RN716xJan 06, 2023Aspirant
Following option 2, removed sdd, connected sda in read-only. The difference is clearly narrower.
root@MaQBaLiNAS:~# mdadm --assemble --scan --force mdadm: NOT forcing event count in /dev/sda3(0) from 18988 up to 19055 mdadm: You can use --really-force to do that (DANGEROUS) mdadm: /dev/md/data-0 assembled from 4 drives - not enough to start the array. mdadm: No arrays found in config file or automatically root@MaQBaLiNAS:~# mdadm --assemble --scan --really-force mdadm: forcing event count in /dev/sda3(0) from 18988 upto 19055 mdadm: /dev/md/data-0 assembled from 5 drives - not enough to start the array. mdadm: No arrays found in config file or automatically
- RN716xJan 06, 2023Aspirant
Quick update after restarting the Nas. Not sure if trying to reconnect sdd to resync would be a good option, hoping to have better redundancy till offload the data.
- StephenBJan 06, 2023Guru - Experienced User
RN716x wrote:
Quick update after restarting the Nas. Not sure if trying to reconnect sdd to resync would be a good option, hoping to have better redundancy till offload the data.
I'm glad it finally mounted.
Don't add any more drives - that will start a resync process that will stress the failing one. If you push it over the edge trying to get redundancy, then you will lose all your data. Remember this whole mess started when disk errors on sda caused the resync to fail.
Just offload everything you can as quickly as you can - using what space you have now to get things started.
- StephenBJan 09, 2023Guru - Experienced User
I'm glad you got the data off. It's very nerve-wracking when multiple disks are having problems.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!