NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 ...
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
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.
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. : (
winger13 wrote:
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. : (
Well, there's not much the NAS can do that would create bad sectors on a drive. Vibration is a potentially a factor, and possibly drive temps.
I had a run of failures on seagates some years ago (most not in RAID arrays), and switched to WDC - which have been reliable for me. But of course others have had different experiences.
However, I also expect 4-5 years life from a disk drive (and of course always want more) - getting only two is disappointing.
I found time today to swap out bad Disk 1 (the 1TB 5-yr+ old Seagate (only powered on less than 2 years, however) ) with a new WD Red 3TB. This time, Instead of cold-swapping as I did with all my previous disk upgrades (place new disks in while RNAS unit was shut off, then powering it on to start the rebuild/sync process), I decided to try hot-swapping.
Below is the log of what happened. Everything seemed fine until 30 mins into removing the bad drive, the system shut itself down. I initially saw the first message (at 17:30 when I pulled the drive out) stating that the system will auto shut down in 30 mins to protect the rest of the system. However, I ignored that message figuring once I popped the new 3TB into Bay 1, all would be good to go.
So, why did the system continue to shut down at 18:00 (30 mins later) ?
BTW - I am running Firmware: RAIDiator 4.2.27 , unsure if this has anything to do with this.
Download All Logs Severity Date Message 
Fri Dec 4 18:02:22 PST 2015 System is up. 
Fri Dec 4 18:00:27 PST 2015 The disk on channel 1 has failed. Shutting down the system to prevent possible data loss resulting from additional failed drives. Fri Dec 4 17:33:34 PST 2015 Data volume will be rebuilt with disk 1. Fri Dec 4 17:31:25 PST 2015 New disk detected. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time. [Disk 1] Fri Dec 4 17:30:25 PST 2015 The disk on channel 1 has failed. The NAS will automatically shutdown in 30 minutes to prevent possible data loss resulting from additional failed drives. 
Fri Dec 4 17:30:19 PST 2015 If the failed disk is used in a RAID level 1, 5, or X-RAID volume, please note that volume is now unprotected, and an additional disk failure may render that volume dead. If this disk is a part of a RAID 6 volume, your volume is still protected if this is your first failure. A 2nd disk failure will make your volume unprotected. If this disk is a part of a RAID 10 volume, a failure of this disk's mirror partner will render the volume dead. It is recommended that you replace the failed disk as soon as possible to maintain optimal protection of your volume. Fri Dec 4 17:30:19 PST 2015 Disk failure detected. Fri Dec 4 17:29:57 PST 2015 A disk was removed from the ReadyNAS. Fri Dec 4 17:29:57 PST 2015 Disk removal detected. [Disk 1]
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
