ReadyNas NV+ v2 5.3.9 SLOWWWW

I have gigabit direct connect, via a trendnet 8port hub, using a comcast business modem/router, and a gigabit Netgear WNDR3700 wireless router (though configured as an AP only).

This morning I got another notice that my 4th drive is now failing, though I looked yesterday at the stats on teh drives through the dashboard yesterday and they all showed no errors (as best i can tell), today it's failing.

Is there some kind of health check/scan I can do on the drives? I'm not really in a position to replace 4 hd's out of one paycheck, but these seagates were all bought at once and if they are going to start failing on me like this...

These drives are not heavy usage... maybe 2-3 hours per day use, rest is spent spun down..

*edit*
I upgraded to 5.3.10 t7 (?) beta FW (same results), and I'm doing tests between pc and nas over GBit ethernet. The existing drives are under warranty apparently still, so getting them replaced is no biggie, but with 2 failures in 1 week, i don't have much choice but replace them.

What errors are reported for drive 4?
You need to replace it.
If you wish to verify that it's bad, power down, remove the drive , connect it to a PC and run vendor diagnostics on it ( long or extended tests) If it fails these tests then the company will rma the drive if it's still under warranty.



The resync puts a heavy load on the drives so not unheard of for the resync to expose another problem drive like this.

Just one reason why you should have a backup.

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 10 volume,your volume is still protected if more than half of the disks alive. But another failure of disks been marked may render that volume dead. It is recommended that you replace the failed disk as soon as possible to maintain optimal protection of your volume.
Sun Mar 2 07:07:17 CST 2014
Disk failure detected.
Sun Mar 2 07:07:01 CST 2014
Detected increasing uncorrectable errors[65520] on disk 4 [ST3000DM001-9YN166, W1F0A1AG]. This often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy.
Sun Mar 2 07:07:00 CST 2014
Detected increasing pending sector count[65520] on disk 4 [ST3000DM001-9YN166, W1F0A1AG]. This often indicates an impending failure. Please be prepared to replace this disk to maintain data redundancy.

You are unlucky.
Bottom line is you need to replace that disk too, ASAP.
The problem with the rma process is that it takes too long for situations like yours.

You'll have to buy another drive unfortunately.

yeah. just cleared it with the boss (wife). we are going in when the store opens this morning.

hopefully this will resolve the issues.

the new drive is in, and I got a notice it finished replicating while on the way to work this morning. I checked periodically on the remaining 2 drives, and didn't see any error count increases so far. Since the other two drives were bought at th same time as the two failed ones, i'm debating ordering two more of the WDReds since newegg has them on sale, just in case..

Sensible.
Hope the boss agrees

*Sigh*
New drive in, replicated, expanded storage (4tb instead of 3tb drives), rebooted again, tried to copy across the wire to my PC, and it peaked out at 390k and then proceeded to drop to the 200k/sec again.
:|

*edit*
I ran the seagate tools short test and it found the drive was fine. Running a long test now... Could this be a NAS problem rather than a drive issue?

Thank you for all your help! I ended up having to replace all 4 drives, and now it seems fine. Took a LONG time to rebuild the final drives (36+ hours), but everything seems okay now.

*sigh*. 4 brand new drives, worked fine for a couple days... and now it's back to 300k reads. NAS performance Tester 1.7 did an avg write of 25.2mb for a 400mb file, the reads have been sitting here about 10min and still hasn't displayed the first result.

No errors on the drives have been reported by the NAS on the Config/Details for each drive. Kind of at a loss now for what to do.