November 8, 20187 yr I've seen this happen to others where it ends up being a fluke or a cable that flickered...Received a red X on a drive from the array (~4000 errors in a row), pulled the drive, and have been testing this thing to the max (HDTune full error scan, and Preclear script)...and still nothing really shows wrong with it. Was it a fluke that I can just preclear and put back into the array? Should I trust it? I attached a crystaldiskinfo smart report. The errors occurred during a parity check...the only thing that I can think of was my tunables supposedly were creating log errors being set too high. Could this be what kicked the drive out? I do run on an Areca card that did call the drive/volume failure. This drive would be my first 5TB to go bad (it's only a few years old). I do run dual parity and have two precleared replacements. Any Advice?
November 8, 20187 yr Community Expert Please post the diagnostics instead, but the disk look fine, at list the partial attributes that appear on the screenshot.
Archived
This topic is now archived and is closed to further replies.