NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
winger13
Apr 16, 2014Guide
Ready for expansion (RN Pro Pioneer Edition)-Seeking Advice
Hi Everyone. I purchased and setup my Readynas Pro Pioneer around Jan 2010. Aside from one disk issue (increasing errors, which Seagate replaced under warranty) it has been a nice experience. I ...
StephenB
Sep 19, 2014Guru - Experienced User
A reallocated sector occurs after a failed write request. The disk has some spare sectors that it can substitute for the failed ones. Data is not lost, because it is a write request that failed (so the data was available to be rewritten).
Pending sectors are similar, but occur after a failed read request. Those need RAID to repair.
Normally I suggest replacing drives before the reallocated sectors + current pending sectors reaches 50. Usually once the counts start increasing they start going up very quickly.
Pending sectors are similar, but occur after a failed read request. Those need RAID to repair.
Normally I suggest replacing drives before the reallocated sectors + current pending sectors reaches 50. Usually once the counts start increasing they start going up very quickly.
- winger13Nov 30, 2015Guide
To recap, I started a 6-bay device with four 1-TB ST31000528AS's. I then did the following per consulting folks on this thread:
1) added two WD 3TB Reds into the two empty bays .... one month later
2) replaced one failing ST31000528AS w/ another 3TB WD Red
Now I am at three original ST31000528AS's and three WD 3TB Reds
Yesterday, I noticed another original ST31000528AS throwing errors so I ordered another WD 3TB Red today.
Question - Looking at the following SMART scan stats, is this latest ST31000528AS issue occurring prematurely? Note - this disk has been in the RN for about five years, but I only turn on the unit for a few hours per week:
Model: ST31000528AS
Serial: 9VP2PAZ7
Firmware: CC37
SMART Attribute
Spin Up Time 0
Start Stop Count 4916
Reallocated Sector Count 296
Power On Hours 16669
Spin Retry Count 0
Power Cycle Count 1519
Runtime Bad Block 0
End-to-End Error 0
Reported Uncorrect 654
Command Timeout 0
High Fly Writes 7
Airflow Temperature Cel 30
Temperature Celsius 30
Current Pending Sector 0
Offline Uncorrectable 0
UDMA CRC Error Count 0
Head Flying Hours 141622251640319
Total LBAs Written 3921397046
Total LBAs Read 3373346045
ATA Error Count 248- StephenBDec 01, 2015Guru - Experienced User
RAID presents near-identical loads to all the drives (and of course they are in the same chassis). So it is not unusual to see a succession of failures, esp. when all the drives are identical and were installed at the same time. It doesn't always happen that way of course, but it is reasonably common.
Do you know when the reallocated sector count and ATA count started to rise? BTW, if you don't have email alerts configured, you should should set them up.
- winger13Dec 01, 2015Guide
My RN unit had been off one week because I was away on vacation, then I came and turned it on, then off, then on. It was on the second time turned on where when I logged onto check the RN and got the warning messages. So, I guess it occurred within 24-36 hours window.
I will need to check when I turn on the RN unit again, but I had my email warning notifications setup, but for some reason I did not reeive anything this time around.
I understand things go wrong with these drive anytime, but does the disk starting to fail only after 16669 hours (694 days) in the 'reasonable' range? I keep the RN in a 'decent' env and take care of things, generally and expected a year or two more. : (
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!