17 Unreadable (pending) sectors on new Freenas build

[thatflashcat]

I built this freenas system less than a month ago and woke up this morning to this alert:

This is just one of my 6 drives in raidz2. 17 seems like a rather high count for a drive I just purchased new. What should I do moving forward?

 

[hugovsky]

Replace drive.

 

[thatflashcat]

Replace drive.

Is it really that bad?

 

[Jessep]

Did you do a full drive burn in testing before deployment?

And yes, RMA it.

 

[thatflashcat]

Did you do a full drive burn in testing before deployment?

And yes, RMA it.

I honestly didn't know that was "common" practice. I'm not saying it isn't a good idea but I've heard very little about doing it in my freenas research. I hope I can get a replacement quickly...

 

[danb35]

I've heard very little about doing it in my freenas research.

I suspect that very little of your "freenas research" was conducted here. Consult the resources section for lots of valuable information, including a hard drive troubleshooting guide (which I'd suggest you review and follow before replacing the drive, though I agree that's probably where you're heading).

 

[thatflashcat]

I suspect that very little of your "freenas research" was conducted here. Consult the resources section for lots of valuable information, including a hard drive troubleshooting guide (which I'd suggest you review and follow before replacing the drive, though I agree that's probably where you're heading).

These forums were my main source of help prior to this point. :p I'll work through the troubleshooting guide, thanks.

Edit: Need I run a second SMART long test? smartctl -a /dev/da2 already shows error ID 5 and 197 with values higher than 0.

 

[Jessep]

This is the standard starting point:
https://www.familybrown.org/dokuwiki/doku.php?id=fester:hvalid_hdd

There are other ways to do the equivalent if you would prefer.

NOTE: Keep in mind this method will destroy your data if you do it on all drives, hence why it's normally done before deployment or only on new drives.