SMART says "bad" drive

Vidaeus · 16. Februar 2016

So I'm new to OMV and file servers. I have 2x Samsung 2TB drives I have taken from a previous synology NAS to add to my new custom built NAS. These are a couple years old. The Smart status is set to red one one of them and I don't know why. The other one is green. Can anyone point me in the right direction? Should I be concerned about something? Planning to use these 2x drives as a RAID mirror.

Spoiler anzeigen

smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-4-amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint F4 EG (AF)
Device Model: SAMSUNG HD204UI
Serial Number: S2H7J90B625748
LU WWN Device Id: 5 0024e9 2057bc13f
Firmware Version: 1AQ10001
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 6
Local Time is: Tue Feb 16 10:56:53 2016 AEDT

==> WARNING: Using smartmontools or hdparm with this
drive may result in data loss due to a firmware bug.
****** THIS DRIVE MAY OR MAY NOT BE AFFECTED! ******
Buggy and fixed firmware report same version number!
See the following web pages for details:
http://knowledge.seagate.com/articles/en_US/FAQ/223571en
http://www.smartmontools.org/wiki/SamsungF4EGBadBlocks

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: (0x80) Offline data collection activity
was never started.
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: (20520) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 100 100 051 - 39
2 Throughput_Performance -OS--K 252 252 000 - 0
3 Spin_Up_Time PO---K 066 065 025 - 10375
4 Start_Stop_Count -O--CK 099 099 000 - 1795
5 Reallocated_Sector_Ct PO--CK 252 252 010 - 0
7 Seek_Error_Rate -OSR-K 252 252 051 - 0
8 Seek_Time_Performance --S--K 252 252 015 - 0
9 Power_On_Hours -O--CK 100 100 000 - 36028
10 Spin_Retry_Count -O--CK 252 252 051 - 0
11 Calibration_Retry_Count -O--CK 252 252 000 - 0
12 Power_Cycle_Count -O--CK 100 100 000 - 37
181 Program_Fail_Cnt_Total -O---K 091 091 000 - 207109729
191 G-Sense_Error_Rate -O---K 100 100 000 - 3
192 Power-Off_Retract_Count -O---K 252 252 000 - 0
194 Temperature_Celsius -O---- 064 056 000 - 28 (Min/Max 14/44)
195 Hardware_ECC_Recovered -O-RCK 100 100 000 - 0
196 Reallocated_Event_Count -O--CK 252 252 000 - 0
197 Current_Pending_Sector -O--CK 100 100 000 - 1
198 Offline_Uncorrectable ----CK 252 252 000 - 0
199 UDMA_CRC_Error_Count -OS-CK 200 200 000 - 0
200 Multi_Zone_Error_Rate -O-R-K 100 100 000 - 15
223 Load_Retry_Count -O--CK 252 252 000 - 0
225 Load_Cycle_Count -O--CK 100 100 000 - 1796
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning

General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
GP/S Log at address 0x00 has 1 sectors [Log Directory]
SMART Log at address 0x01 has 1 sectors [Summary SMART error log]
SMART Log at address 0x02 has 2 sectors [Comprehensive SMART error log]
GP Log at address 0x03 has 2 sectors [Ext. Comprehensive SMART error log]
SMART Log at address 0x06 has 1 sectors [SMART self-test log]
GP Log at address 0x07 has 2 sectors [Extended self-test log]
GP Log at address 0x08 has 2 sectors [Power Conditions]
SMART Log at address 0x09 has 1 sectors [Selective self-test log]
GP Log at address 0x10 has 1 sectors [NCQ Command Error]
GP Log at address 0x11 has 1 sectors [SATA Phy Event Counters]
GP/S Log at address 0x80 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x81 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x82 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x83 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x84 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x85 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x86 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x87 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x88 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x89 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8a has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8b has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8c has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8d has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8e has 16 sectors [Host vendor specific log]
GP/S Log at address 0x8f has 16 sectors [Host vendor specific log]
GP/S Log at address 0x90 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x91 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x92 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x93 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x94 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x95 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x96 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x97 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x98 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x99 has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9a has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9b has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9c has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9d has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9e has 16 sectors [Host vendor specific log]
GP/S Log at address 0x9f has 16 sectors [Host vendor specific log]
GP/S Log at address 0xe0 has 1 sectors [SCT Command/Status]
GP/S Log at address 0xe1 has 1 sectors [SCT Data Transfer]

SMART Extended Comprehensive Error Log Version: 1 (2 sectors)
Device Error Count: 1
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Vidaeus · 16. Februar 2016

Spoiler anzeigen

Error 1 [0] occurred at disk power-on lifetime: 18924 hours (788 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 40 00 00 2c f6 79 20 40 00 Error: UNC at LBA = 0x2cf67920 = 754350368

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 a0 00 00 2c f6 78 c0 40 08 00:26:47.505 READ FPDMA QUEUED
60 00 00 00 a0 00 00 2c f6 78 c0 40 08 00:26:47.541 READ FPDMA QUEUED
60 00 00 00 20 00 00 09 5e d1 c0 40 08 00:26:47.541 READ FPDMA QUEUED
60 00 00 00 20 00 00 47 d2 d2 e8 40 08 00:26:47.541 READ FPDMA QUEUED
60 00 00 00 20 00 00 82 ff 32 18 40 08 00:26:47.541 READ FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (2 sectors)
No self-tests have been logged. [To run self-tests, use: smartctl -t]

Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Completed [00% left] (0-65535)
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):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version: 2
SCT Version (vendor specific): 256 (0x0100)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 30 Celsius
Power Cycle Min/Max Temperature: 22/31 Celsius
Lifetime Min/Max Temperature: 14/63 Celsius
Lifetime Average Temperature: 80 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Temperature History Version: 2
Temperature Sampling Period: 5 minutes
Temperature Logging Interval: 5 minutes
Min/Max recommended Temperature: -5/80 Celsius
Min/Max Temperature Limit: -10/85 Celsius
Temperature History Size (Index): 128 (114)

Index Estimated Time Temperature Celsius
115 2016-02-16 00:25 29 **********
116 2016-02-16 00:30 36 *****************
... ..( 5 skipped). .. *****************
122 2016-02-16 01:00 36 *****************
123 2016-02-16 01:05 35 ****************
124 2016-02-16 01:10 36 *****************
... ..( 3 skipped). .. *****************
0 2016-02-16 01:30 36 *****************
1 2016-02-16 01:35 37 ******************
2 2016-02-16 01:40 36 *****************
... ..( 5 skipped). .. *****************
8 2016-02-16 02:10 36 *****************
9 2016-02-16 02:15 35 ****************
10 2016-02-16 02:20 36 *****************
11 2016-02-16 02:25 36 *****************
12 2016-02-16 02:30 35 ****************
13 2016-02-16 02:35 35 ****************
14 2016-02-16 02:40 36 *****************
15 2016-02-16 02:45 36 *****************
16 2016-02-16 02:50 36 *****************
17 2016-02-16 02:55 35 ****************
... ..( 7 skipped). .. ****************
25 2016-02-16 03:35 35 ****************
26 2016-02-16 03:40 25 ******
27 2016-02-16 03:45 27 ********
28 2016-02-16 03:50 28 *********
29 2016-02-16 03:55 29 **********
30 2016-02-16 04:00 31 ************
31 2016-02-16 04:05 32 *************
32 2016-02-16 04:10 33 **************
33 2016-02-16 04:15 34 ***************
... ..( 2 skipped). .. ***************
36 2016-02-16 04:30 34 ***************
37 2016-02-16 04:35 35 ****************
38 2016-02-16 04:40 35 ****************
39 2016-02-16 04:45 35 ****************
40 2016-02-16 04:50 36 *****************
41 2016-02-16 04:55 37 ******************
42 2016-02-16 05:00 36 *****************
43 2016-02-16 05:05 36 *****************
44 2016-02-16 05:10 35 ****************
45 2016-02-16 05:15 36 *****************
... ..( 2 skipped). .. *****************
48 2016-02-16 05:30 36 *****************
49 2016-02-16 05:35 37 ******************
50 2016-02-16 05:40 36 *****************
... ..( 3 skipped). .. *****************
54 2016-02-16 06:00 36 *****************
55 2016-02-16 06:05 37 ******************
56 2016-02-16 06:10 36 *****************
... ..( 6 skipped). .. *****************
63 2016-02-16 06:45 36 *****************
64 2016-02-16 06:50 27 ********
65 2016-02-16 06:55 29 **********
66 2016-02-16 07:00 30 ***********
67 2016-02-16 07:05 32 *************
68 2016-02-16 07:10 33 **************
69 2016-02-16 07:15 34 ***************
70 2016-02-16 07:20 34 ***************
71 2016-02-16 07:25 35 ****************
72 2016-02-16 07:30 35 ****************
73 2016-02-16 07:35 36 *****************
... ..( 2 skipped). .. *****************
76 2016-02-16 07:50 36 *****************
77 2016-02-16 07:55 37 ******************
... ..( 22 skipped). .. ******************
100 2016-02-16 09:50 37 ******************
101 2016-02-16 09:55 38 *******************
102 2016-02-16 10:00 37 ******************
... ..( 5 skipped). .. ******************
108 2016-02-16 10:30 37 ******************
109 2016-02-16 10:35 36 *****************
110 2016-02-16 10:40 26 *******
111 2016-02-16 10:45 24 *****
112 2016-02-16 10:50 27 ********
113 2016-02-16 10:55 29 **********
114 2016-02-16 11:00 30 ***********

SCT Error Recovery Control:
Read: Disabled
Write: Disabled

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 4 0 Command failed due to ICRC error
0x0002 4 0 R_ERR response for data FIS
0x0003 4 0 R_ERR response for device-to-host data FIS
0x0004 4 0 R_ERR response for host-to-device data FIS
0x0005 4 0 R_ERR response for non-data FIS
0x0006 4 0 R_ERR response for device-to-host non-data FIS
0x0007 4 0 R_ERR response for host-to-device non-data FIS
0x0008 4 0 Device-to-host non-data FIS retries
0x0009 4 4 Transition from drive PhyRdy to drive PhyNRdy
0x000a 4 3 Device-to-host register FISes sent due to a COMRESET
0x000b 4 0 CRC errors within host-to-device FIS
0x000d 4 0 Non-CRC errors within host-to-device FIS
0x000f 4 0 R_ERR response for host-to-device data FIS, CRC
0x0010 4 0 R_ERR response for host-to-device data FIS, non-CRC
0x0012 4 0 R_ERR response for host-to-device non-data FIS, CRC
0x0013 4 0 R_ERR response for host-to-device non-data FIS, non-CRC
0x8e00 4 0 Vendor specific
0x8e01 4 0 Vendor specific
0x8e02 4 0 Vendor specific
0x8e03 4 0 Vendor specific
0x8e04 4 0 Vendor specific
0x8e05 4 0 Vendor specific
0x8e06 4 0 Vendor specific
0x8e07 4 0 Vendor specific
0x8e08 4 0 Vendor specific
0x8e09 4 0 Vendor specific
0x8e0a 4 0 Vendor specific
0x8e0b 4 0 Vendor specific
0x8e0c 4 0 Vendor specific
0x8e0d 4 0 Vendor specific
0x8e0e 4 0 Vendor specific
0x8e0f 4 0 Vendor specific
0x8e10 4 0 Vendor specific
0x8e11 4 0 Vendor specific

subzero79 · 16. Februar 2016

That's a new feature and it probably needs some polishing. The red flag might be because the current pending sector, maybe it should be yellow just a warning to observe the values in the next days. Check in the few days the reallocated sector count starts increasing.

In general before a disk starts getting uncorrectable sectors, the disk reallocates bads ones to spare ones. This is a warning, during that period you should of course purchase a new replacement unit before the uncorrectable errors happens, otherwise it leads to data corruption.

So again observe in the new days the values 5,197 and 198 which are the most important ones. Read the backblaze blog if you want interesting information about smart.

Vidaeus · 16. Februar 2016

OK, thanks for the info. Any suggestions for SMART tests to add into the schedule? Like a daily short test, weekly long test for each drive or something like that? Is that even necessary?

subzero79 · 16. Februar 2016

Zitat von Vidaeus

Any suggestions for SMART tests to add into the schedule? Like a daily short test, weekly long test for each drive or something like that? Is that even necessary?

My personal opinion is they are useless....the drive could have 1000 bad sectors, the smart test will pass anyway. I focus on observing the smart values, at least once a month, like I said those three values. Read the backblaze blog

votdev · 16. Februar 2016

With the next package version the tooltip of the LED icon in the device list will show a detailed description of the error. See https://sourceforge.net/p/openmediavault/code/2147.

Vidaeus · 17. Februar 2016

Cool, thanks good to know.

Jetzt mitmachen!