smartctl -a /dev/ada0 output , does this mean my drive is failing badly ?

[Simon Bingham]

does this mean my drive is failing badly ?

smartctl -t long /dev/ada0

Many hours later ......


smartctl -a /dev/ada0

Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 47
3 Spin_Up_Time 0x0027 194 183 021 Pre-fail Always - 7258
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 120
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 045 045 000 Old_age Always - 40396
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 120
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 94
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 218
194 Temperature_Celsius 0x0022 118 102 000 Old_age Always - 34
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 3

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 Extended offline Completed: read failure 90% 40335 32042232

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):


Regards

Simon

 

[Alecmascot]

I would change it.

 

[jlpellet]

Based on the smart data shown, the drive is over 4 years old & shows 1 pending sector. As I understand it, this means the drive has a single block in use that it cannot get a successful write confirmation from. I understand this to mean that the drive likely has used up the spare sectors that are initially provisioned on the drive. You should expect this number to increase & sometimes it does so rapidly. I've seen, on my systems, this go from 1-5 to 20 in a week and stay at 1-2 for weeks. There are several suggestions on line about how to "fix" this by, essentially, forcing the drive to rewrite the sector or mark it bad. YMMV but it has not worked for me. For me, replacing an old drive is preferred over losing it an active pool. I don't see any information about the pool but I run Z2 pools & have never had a pool data loss from this error. Hope this helps.

 

[Simon Bingham]

Based on the smart data shown, the drive is over 4 years old & shows 1 pending sector. As I understand it, this means the drive has a single block in use that it cannot get a successful write confirmation from. I understand this to mean that the drive likely has used up the spare sectors that are initially provisioned on the drive. You should expect this number to increase & sometimes it does so rapidly. I've seen, on my systems, this go from 1-5 to 20 in a week and stay at 1-2 for weeks. There are several suggestions on line about how to "fix" this by, essentially, forcing the drive to rewrite the sector or mark it bad. YMMV but it has not worked for me. For me, replacing an old drive is preferred over losing it an active pool. I don't see any information about the pool but I run Z2 pools & have never had a pool data loss from this error. Hope this helps.

Thankyou I think I will spend the money !! I had set the drive to shut down as this NAS probably only get used once a week, but it looks now the SMART feature might have been waking the drive every 30 mins anyway. which would undoubtedly be worst than leaving it running.

 

[joeschmuck]

does this mean my drive is failing badly ?

Yes, the Extended Test failed to complete. If it is still under warranty then you have grounds to have it replaced.

To explain the errors:

# 1 Extended offline Completed: read failure 90% 40335 32042232

This is your primary failure indication, the test must complete and right now LBA 32042230 is unreadable. It doesn't mean there is data there but the SMART Extended test reads the entire surface of the drive platters, if it cannot read it then you get a message like yours.

ID 5 and 196 = 0 so you have no actual hard sectors reallocated.
ID 197 = 1 so you have an incident in which you could not read a sector but eventually it was readable. If it could not be read then you would have ID 196 greater than 0.
ID 200 = 3 which is not always bad for some drives but some drives it indicates a problem. Unfortunately you did not provide your drive model number so I can't say if this is a problem or not. That is the same at ID 1 = 47 which in general is not a problem but some drive models will report 0 unless there is an error, some will report large values.

When you check your SMART data if ID 1 is changing significantly (into the thousands and millions, then back to low numbers) you can disregard it. This is a function of a read ahead buffer in the drive and if you did not ask for that data, the counter increases. It's not a problem if that happens. If this value is normally = 0 then it's a problem indicator when not a zero value.

If this is your full output from smartctl -a /dev/ada0 then you are not running routine SMART Short and Long tests. I suspect you cut some data out. Please note, posting all the data is okay. But for this problem, it's a failing drive.

Be careful buying a new drive, stay away from SMR drives.