SOLVED (Solution: I don't know how to read smart results, and likely bad PSU) Bad drives from the supplier?

[MGYVR]

So I've got an old project that was recently revived and I am getting absolutely horrid results from SMART testing on the drives.

System:
Mobo: SuperMicro H8SGL-F
CPU: Opteron 6168 1.8Ghz 12core
RAM: 32GB ECC
Boot Drives: 2x Generic (Phison) 120GB SATA SSD
Drives: 4x Seagate Constellation ES.2 3TB (ST33000651NS)

This was supposed to be a recycle job for a client, they purchased those hard drives new in mid-2019, but then the project got shelved during the pandemic and the drives just sat in climate controlled storage (in anti-static bags) until a couple months ago when the project was revived and given to me.

This was intended to be a low cost workstation backup server for the client. But according to the SMART results, these seagate drives went from "new" to almost dead in about a month. They are configured in a RAIDZ(1) with lz4 compression (default pool setup otherwise).

The only issue I've been running into with this server has been some random reboots, that made me suspect the old PSU was failing. I was waiting to fully diagnose/replace that until I could find more info as to what's going on with these drives. Data transfers to/from the server during setup and initial testing have been working fine and quite fast given the age of the other hardware (other than when the random reboots strike obviously).

Short SMART results for one of the drives (all 4 are all similar):
--------------------------------------------------------------------------
# smartctl -a /dev/ada2
smartctl 7.2 2021-09-14 r5236 [FreeBSD 13.1-RELEASE-p2 amd64] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Constellation ES.2 (SATA 6Gb/s)
Device Model: ST33000651NS
Serial Number: Z293B2XR
LU WWN Device Id: 5 000c50 04d9f0125
Firmware Version: G009
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Fri Dec 16 11:12:30 2022 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 600) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 443) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x10bd) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 082 063 044 Pre-fail Always - 186014819
3 Spin_Up_Time 0x0003 091 091 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 13
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 065 051 030 Pre-fail Always - 30091589467
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 760
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 13
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 058 046 045 Old_age Always - 42 (Min/Max 33/45)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 6
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 41
194 Temperature_Celsius 0x0022 042 054 000 Old_age Always - 42 (0 24 0 0 0)
195 Hardware_ECC_Recovered 0x001a 022 006 000 Old_age Always - 186014819
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 749 -
# 2 Short offline Completed without error 00% 725 -
# 3 Short offline Completed without error 00% 700 -
# 4 Short offline Completed without error 00% 677 -
# 5 Short offline Completed without error 00% 653 -
# 6 Short offline Completed without error 00% 629 -
# 7 Short offline Completed without error 00% 605 -
# 8 Short offline Completed without error 00% 581 -
# 9 Extended offline Interrupted (host reset) 40% 575 -
#10 Short offline Completed without error 00% 557 -
#11 Short offline Completed without error 00% 533 -
#12 Short offline Completed without error 00% 509 -
#13 Short offline Completed without error 00% 485 -
#14 Short offline Completed without error 00% 461 -
#15 Short offline Completed without error 00% 437 -
#16 Short offline Completed without error 00% 413 -
#17 Short offline Completed without error 00% 389 -
#18 Short offline Completed without error 00% 365 -
#19 Short offline Completed without error 00% 342 -
#20 Short offline Completed without error 00% 318 -
#21 Short offline Completed without error 00% 293 -

So, did the client just get bad drives from the supplier? Obviously we're way out of return/warranty period. I swear that the initial SMART results when I installed these drives were pristine as you would expect from new drives. But I didn't keep any copies of those results and ended up changing things around and reinstalling TrueNAS a few times before I got to this iteration of the server.

Any insight would be appreciated before I convey the bad news about these drives to the client.

I've just never run into this sort of behavior from "new" drives before, so wanted a second opinion before scrapping them.

TIA!

 

[winnielinnie]

No errors logged.

No selftest failures.

Only 13 total power cycles.

What is the concern with the drives? Is it the RAW values for attributes #1, #7, and #195?

I believe for #195 (for Seagate at least?), it's how much time has passed since the last time it had to recover from an ECC error. (Not even sure what unit of time is represented in the RAW value.)

For #1 and #7, it's been fleshed out on these forums before, and I remember something along the lines of "Seagate uses its own internal metrics" to calculate those values.

 

[MGYVR]

No errors logged.

No selftest failures.

Only 13 total power cycles.

What is the concern with the drives? Is it the RAW values for attributes #1, #7, and #195?

I believe for #195 (for Seagate at least?), it's how much time has passed since the last time it had to recover from an ECC error. (Not even sure what unit of time is represented in the RAW value.)

For #1 and #7, it's been fleshed out on these forums before, and I remember something along the lines of "Seagate uses its own internal metrics" to calculate those values.

Mostly #1/#5/#7/#195. I guess I'm just not used to the Seagate reporting. I also have a weird error state in TrueNAS that I've never seen before. I've tried researching it but kept finding scenarios that were different from mine in some regard.

After looking at the smart results I kinda just figured the error states displayed in the UI were the result of the drives being in poor health.

 

[MGYVR]

Edit:
The test results wrapped weird in my console and I was looking at the wrong value for #5...

 

[winnielinnie]

I also have a weird error state in TrueNAS that I've never seen before.

You can check in the terminal itself:
zpool status -v BULK

 

[MGYVR]

You can check in the terminal itself:
zpool status -v BULK

Thanks, I was researching that separately, and was almost there. Checksum errors, permanent failures on a couple of non-essential files in the pool. Cleared; points back to errors probably caused by the random reboots and failing PSU.

Thanks for the help!

 

[winnielinnie]

Thanks, I was researching that separately, and was almost there. Checksum errors, permanent failures on a couple of non-essential files in the pool. Cleared; points back to errors probably caused by the random reboots and failing PSU.

Thanks for the help!

It's still worth to run a complete scrub of the pool anyways. Perhaps run one overnight? (It should automatically clear any obsolete errors as well.)

 

[MGYVR]

It's still worth to run a complete scrub of the pool anyways. Perhaps run one overnight? (It should automatically clear any obsolete errors as well.)

For sure, just did a zpool clear, deleted the corrupted files, and started a scrub. This server is still just in testing. Nothing critical stored anywhere on it. Will see how the scrub goes, replace the PSU and go from there.

Thanks again!