× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

ReadyNAS Duo V2 disk problems

jasonbb
Tutor

ReadyNAS Duo V2 disk problems

Hi guys,

Last week a received an email saying that my second disk had failed so I went and replaced it, I received another email this morning saying "disk failure detected" and another message saying if the disk failed basically replace it straight away, when I got home it was disk 2 again (the new one).  I pulled it out and put it back in, it didn't seem to do anything apart from take the NAS offline, I couldn't do anything to see it so I had no option but kill the power to the NAS to see it again, while it was off I switched the drives in the bays around, once it powered on again the system says everything is ok.

 

I checked the SMART information for both drives and the new one has "raw read error rate" 23, the second drive doesn't show any errors.

 

Disks are 1 x WD Red 2TB & new WD Red 4TB, see attached file for screenshots of the SMART information, I am now not convinced the second drive failed at all.

Disk 1.jpg

Disk 2.jpg

 

Model: ReadyNASRND2110v2|ReadyNAS Duo v2
Message 1 of 6
jasonbb
Tutor

Re: ReadyNAS Duo V2 disk problems

I also just noticed on the status page it says the disks are:  X-RAID2 (Not-Redundant), I searched this and found a page saying pull the first drive and see if you can still access your files, I did this and the NAS went offline again, I restarted it (by killing the power again as it was unresponsive) and RAIDar now says corrupt root.

 

This was my storage device with backups and my iTunes library now I can't even access it.

Message 2 of 6
FramerV
NETGEAR Employee Retired

Re: ReadyNAS Duo V2 disk problems

Hi jasonbb,

 

Just would like to confirm. When you replaced the drive last week, did the re-sync finish?

 

I notice that the 4TB HDD has a Current Pending Sector. That is an indicator that the HDD is going bad or its bad already.

 

Which of the drives did you pull out? The 2TB or the 4TB?

 

Can you also tell mo the current placements of the HDD's within the ReadyNAS.

 

 

Regards,

Message 3 of 6
jasonbb
Tutor

Re: ReadyNAS Duo V2 disk problems

Thanks FramerV,

 

The log indicated the sync finshed around 6 hours later, I received the second email about 5 days after I installed the new disk in bay 2, when I checked the NAS it indicated the new drive had failed, I shut in down and swapped the drives around, the new drive in bay 1 and the older drive in 2 and it restarted ok and everything seemed to be ok execpt when I came across the message saying it was non redundant.

 

I searched that and someone suggested pulling 1 drive out while it was up to see if you could still access the data, off memory I pulled out the new drive in bay 1 and it became un responsive, I ended up killing the power and that's when RAIDr said its currupt.

 

I think its time for a new NAS, it there any way of getting the data off these drives without the NAS?

Message 4 of 6
FramerV
NETGEAR Employee Retired

Re: ReadyNAS Duo V2 disk problems

Hi jasonbb,

 

It might be best if you get in touch with our support group. We do have a data recovery service that you can avail.

 

ReadyNAS: Data Recovery Diagnostics - Scope of Service

 

Contact NETGEAR Support

 

 

Regards,

Message 5 of 6
StephenB
Guru

Re: ReadyNAS Duo V2 disk problems


@FramerV wrote:

 

I notice that the 4TB HDD has a Current Pending Sector. That is an indicator that the HDD is going bad or its bad already.

 

I think that's an over-statement with only 1 current pending sector.  It is a concern that should be watched, but a single bad sector (whether pending or reallocated) does't mean the disk is bad.  

 

The format of the raw read error rate is vendor specific, and without a WDC decoder ring it's hard to tell if its a concern or not.  Unfortunately I've never seen a description of what the raw values mean.  Similarly for seek error rate.

 

That said, we can't rule out a drive issue, and certainly something went wrong.

 

As far as remedial actions you took - you should have powered down before removing disk 1, and then tried rebooting.  My guess is that the corrupt root resulted from pulling the plug, but of course if the system isn't responding you'd have had no other option.

 

Contacting support is the best option.  There are some off-line tools that might be able to access the data (r-linux for windows being a free one you could try).

Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 2134 views
  • 0 kudos
  • 3 in conversation
Announcements