Superorb Posted March 21, 2014 Share Posted March 21, 2014 Amazon has this drive for $150 with free shipping. Normally $175 and lowest price was $169.99 according to the Camel. These drives are excellent for servers and NAS enclosures. http://www.amazon.com/gp/product/B00D1GYO4S Built and tested to provide industry-leading performance for 24x7 NAS applications Includes NASWorks technology to support customized error recovery, advanced power management and vibration tolerance features Designed for home servers or desktop NAS solutions, small-business file sharing, backup server applications Available in 2TB, 3TB and 4TB capacities Always on, 24x7 - 1M hours MTBF Quote Link to comment
garycase Posted March 21, 2014 Share Posted March 21, 2014 Excellent price -- definitely the best I've seen for this NAS unit. Just grabbed a couple for spares Quote Link to comment
Superorb Posted March 21, 2014 Author Share Posted March 21, 2014 If Only I could figure out my random errors during parity checks I'd start buying more drives again. I did figure out the hardware issues with the SATA links being reset, but can't figure out the sync errors. RAM is fine, tested for 72 hours without error. Quote Link to comment
garycase Posted March 21, 2014 Share Posted March 21, 2014 Off topic for this thread ... but if I recall correctly you're always running non-correcting checks, right? So are you sure this isn't just a once-in-a-blue-moon sync error that you're seeing multiple times because you don't correct it?? I NEVER run non-correcting checks ... it's really very simple -- if there's an error, I want it corrected. Quote Link to comment
Superorb Posted March 21, 2014 Author Share Posted March 21, 2014 Off topic for this thread ... but if I recall correctly you're always running non-correcting checks, right? So are you sure this isn't just a once-in-a-blue-moon sync error that you're seeing multiple times because you don't correct it?? I NEVER run non-correcting checks ... it's really very simple -- if there's an error, I want it corrected. Yes, I'm sure. I always copy the addresses of the errors and no two have ever matched. Plus sometimes I'll have 2 errors, then I'll have 30+ errors, then the next time will be 1 or no errors, etc. If it's not memory what could it be? I do get errors past 2TB and my largest data drive is 2TB with parity being 4TB. Quote Link to comment
garycase Posted March 21, 2014 Share Posted March 21, 2014 I do get errors past 2TB and my largest data drive is 2TB with parity being 4TB. Have you tried replacing the parity drive? If you're getting errors past the highest data addresses, then it's got to be either an error on the parity drive; memory; or a controller issue. Sounds like you've already pretty thoroughly tested the RAM and controller ... so I'd try a different parity drive. Quote Link to comment
Superorb Posted March 21, 2014 Author Share Posted March 21, 2014 I do get errors past 2TB and my largest data drive is 2TB with parity being 4TB. Have you tried replacing the parity drive? If you're getting errors past the highest data addresses, then it's got to be either an error on the parity drive; memory; or a controller issue. Sounds like you've already pretty thoroughly tested the RAM and controller ... so I'd try a different parity drive. I did replace the parity drive. I had the same random errors with the old 2TB parity and also with the new 4TB parity drive. I really hate gremlins like this I was throwing around the idea of getting a new SATA card and moving all the drives to the new card since I'm using mobo headers for all 6 drives. Quote Link to comment
CrashnBrn Posted March 21, 2014 Share Posted March 21, 2014 Why don't the WD Red 4TB drop to this price Quote Link to comment
Superorb Posted March 21, 2014 Author Share Posted March 21, 2014 Why don't the WD Red 4TB drop to this price Patience young padawan Quote Link to comment
pkn Posted March 22, 2014 Share Posted March 22, 2014 I NEVER run non-correcting checks ... it's really very simple -- if there's an error, I want it corrected. If the error occurred not on the parity drive, but on data drive, writing "correction" to parity drive will actually make things worse. This is a thing I don't like about unRAID - no "bit-rot" protection. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.