Smart Report - ECC Count

[sfcredfox]

Community,

I have a new 'used' drive that reports errors corrected by ECC. I had not seen this issue on any drives until now. Google research has people saying that errors corrected by ECC are not that serious or may have been a result of the previous system the drive lived in.

Question:
Is this indicative of a soon to fail device?
Should I trust this drive in a pool with production data?

I have attached the smartctl -a report and the system specs on in my signature.

Thanks.

FreeNAS 9.3-Stable 64-bit

Show : Main System

FreeNAS Platform:
SuperMicro 826 (8XDTN+)
(x2) Intel(R) Xeon(R) CPU E5200 @ 2.27GHz
72GB RAM (ECC Always!)
APC3000 UPS (Always!)

Show : Peripherals

Intel Pro 1000 (integrated) for CIFS
(2x) Intel Pro 1000 PT/MT Duals Port (Quad ports for iSCSI)
(2x) Intel 3500 SSD SLOG
IBM M1015 IT Mode HBA (Port 0) -> BPN-SAS2-826EL1 (12 port backplane with expander)
IBM M1015 IT Mode HBA (Port 1) -> SFF-8088 connected -> HP MSA70 3G 25 bay drive enclosure
HP SAS HBA (Port 0) -> SFF-8088 connected -> HP DS2700 6G 25 bay drive enclosure

Show : Pools

Pool1 (VM Datastore) -> 24x 3G 146GB 10K SAS into 12 vDev Mirrors
Pool2 (VM Datastore) -> 10x 6G 300GB 10K SAS into 5 vDev Mirrors (one mirror of 146GB, oops!)
Pool3 (Media Storage) -> 8x 3G 2TB 7200 SATA into 1vDev[Z2]

Show : Network Scheme

Network Infrastructure:
Cisco SG200-26 (26 Port Gigabit Switch)

Four separate vLANs/subnets for iSCSI

• em2 - x.x.101.7/24
• em3 - x.x.102.7/24
• em0 - x.x.103.7/24
• em1 - x.x.104.7/24

Separate vLAN/subnet for CIFS (Always!)

• itb - x.x.0.7/24

 

[jde]

I would recommend doing a complete disk burn-in before putting any data on this disk. It about 5.5 years old and has only had 3 short smart tests - 2 when it was originally put in service, and one more recently. Once you have completed a burn-in including long smart tests, post the -a output. and post the results.

 

[Robert Trevellyan]

Good advice.

If I read it correctly, the drive has only seen 4GB of data throughput, so it was probably mostly idle.

As far as I know, modern hard drives must continuously correct errors, or they simply wouldn't function. Data bits are no longer written discretely, but in waveform chunks, which require clever math to reconstruct, and error correction is an integral part of that.

 

[sfcredfox]

Doesn't look like the data has changed unless I'm missing something key...

I guess I could use dd to burn some data to it in different block sizes for a while and make sure nothing changes throughout that abuse

 

[jde]

I was thinking of a multi-day or multi- week burn-in along these lines. https://forums.freenas.org/index.php?threads/how-to-hard-drive-burn-in-testing.21451/

Be aware that badblocks will destroy any data on the disk, so don't do it if you've already added the disk to your pool.

 

[Robert Trevellyan]

Doesn't look like the data has changed unless I'm missing something key...

Is that the output from smartctl -a? I don't see the usual list of numbered attributes and their values.

 

[sfcredfox]

Is that the output from smartctl -a? I don't see the usual list of numbered attributes and their values.

I know, I expected more info. That was everything smartctl -a kicked out for /dev/da10

 

[Robert Trevellyan]

Does -x deliver more? I have no experience with SAS, maybe this is expected behavior.

 

[Ericloewe]

Doesn't look too unusual for an SAS drive, but I'm not too familiar with the exact layout.