Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Earlier today, I was running SMART checks on my hard drives and noticed that my HGST 5K3000 drive had logged a number of UNC errors at the same LBA location. How worried should I be and what should I do next? (This drive is in my backup NAS that is used only occasionally unlike the other one that is on 24x7)
smartctl 5.42 2011-10-20 r3458 [armv5tejl-linux-2.6.22.18] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Hitachi Deskstar 5K3000
Device Model: Hitachi HDS5C3020ALA632
Serial Number: ML0220F31GJXSD
LU WWN Device Id: 5 000cca 369d4b43e
Firmware Version: ML6OA5C0
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 4
Local Time is: Sat Oct 11 03:01:58 2014 UTC
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: (0x85) Offline data collection activity
was aborted by an interrupting command from host.
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: (21098) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
SCT capabilities: (0x003d) 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 FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 136 136 054 Pre-fail Offline - 94
3 Spin_Up_Time 0x0007 134 134 024 Pre-fail Always - 405 (Average 410)
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 362
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 44
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 146 146 020 Pre-fail Offline - 29
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 978
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 112
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 362
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 362
194 Temperature_Celsius 0x0002 162 162 000 Old_age Always - 37 (Min/Max 22/41)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 49
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 17
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 5401 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
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.
Error 5401 occurred at disk power-on lifetime: 873 hours (36 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 03 bd b7 63 02 Error: UNC at LBA = 0x0263b7bd = 40089533
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 b0 b8 b7 63 40 00 17:45:40.497 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 17:45:40.497 READ LOG EXT
60 08 b0 b8 b7 63 40 00 17:45:36.934 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 17:45:36.934 READ LOG EXT
60 08 b0 b8 b7 63 40 00 17:45:33.451 READ FPDMA QUEUED
Error 5400 occurred at disk power-on lifetime: 873 hours (36 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 03 bd b7 63 02 Error: UNC at LBA = 0x0263b7bd = 40089533
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 b0 b8 b7 63 40 00 17:45:36.934 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 17:45:36.934 READ LOG EXT
60 08 b0 b8 b7 63 40 00 17:45:33.451 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 17:45:33.451 READ LOG EXT
60 08 b0 b8 b7 63 40 00 17:45:29.870 READ FPDMA QUEUED
Error 5399 occurred at disk power-on lifetime: 873 hours (36 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 03 bd b7 63 02 Error: UNC at LBA = 0x0263b7bd = 40089533
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 b0 b8 b7 63 40 00 17:45:33.451 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 17:45:33.451 READ LOG EXT
60 08 b0 b8 b7 63 40 00 17:45:29.870 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 17:45:19.880 READ LOG EXT
60 08 b0 b8 b7 63 40 00 17:45:16.397 READ FPDMA QUEUED
Error 5398 occurred at disk power-on lifetime: 873 hours (36 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 03 bd b7 63 02 Error: UNC at LBA = 0x0263b7bd = 40089533
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 b0 b8 b7 63 40 00 17:45:29.870 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 17:45:19.880 READ LOG EXT
60 08 b0 b8 b7 63 40 00 17:45:16.397 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 17:45:16.397 READ LOG EXT
60 08 b0 b8 b7 63 40 00 17:45:12.914 READ FPDMA QUEUED
Error 5397 occurred at disk power-on lifetime: 873 hours (36 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 03 bd b7 63 02 Error: UNC at LBA = 0x0263b7bd = 40089533
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 b0 b8 b7 63 40 00 17:45:16.397 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 17:45:16.397 READ LOG EXT
60 08 b0 b8 b7 63 40 00 17:45:12.914 READ FPDMA QUEUED
2f 00 01 10 00 00 00 00 17:45:12.913 READ LOG EXT
60 08 b0 b8 b7 63 40 00 17:45:09.431 READ FPDMA QUEUED
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% 978 -
# 2 Extended offline Aborted by host 90% 322 -
# 3 Short offline Completed without error 00% 322 -
# 4 Short offline Completed without error 00% 5 -
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):
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.Offline
Personally I would not want to count on a drive that is showing so many (more than 1) errors. I'm not a SMART expert but since this is your backup I would replace it. In fact I had a similar issue last week. Once I saw the failure rate (I scan the SMART log automatically every night and send alert emails if errors are found) I bought a 2TB WD Red drive to replace an old 1TB Seagate. I have 3 DNS323s and copy my "critical" files to both drives on one unit as well as once to each of the other units, and to USB sticks on all 3 units (and offsite). RSync gets a good workout in my enviroment.
Added incentive in my case was to finally get my oldest unit updated with 2TB drives as this was the only one that still had a 'small' HDD. Over the years I've had 2 Seagate failures but zero WD.
Offline
While I'm waiting to get a new drive, I took the offending drive out and attached it to my PC, booted Ubuntu from a Live CD and ran fsck. It found and fixed one bad sector. I also ran badblocks and it did not find any.
Since the NAS was down any way, I did the same with the other drive. No fsck or badblocks errors!
Offline