Code:
Self-test execution status: ( 244) Self-test routine in progress...
40% of test remaining.
That suggests to me you need to wait another hours or so for the test to complete.
Self-test execution status: ( 244) Self-test routine in progress...
40% of test remaining.
Perhaps you were thinking of a captive test?In the past I have had disks which would abort a self test if the OS was accessing them. I could have sworn this disk did the same. However, it does seem to successfully run in background.
Why? You can repair sectors manually in normal mode. I suppose whether it's a good idea or not depends on where it is and what it's being used for. The data has gone anyway if the sector's bad, so what have you got to lose?I am not sure how useful it is to run it in background. If faults are found they would have to be fixed in maintenance mode anyway.
Do it in normal mode next time. Then you can use it as normal and not have to worry about the heat. It's really a no-brainer.smartctl -t long /dev/sda (in maintenance mode)
No. It stops when it finds an error or when it's complete (in 234 minutes). You have to ask it...it said 234 min - will it tell me when it has finished
You can run "smartctl -l selftest /dev/sda" (which produces only the output you are interested in) at any point to see how it is getting on. You don't have to wait the whole 4 hours. You already know that there is no point checking before 2 hours though from your previous test.smartctl -a /dev/sda
Do it in normal mode next time. Then you can use it as normal and not have to worry about the heat. It's really a no-brainer.
User Capacity: 1,000,204,886,016 bytes [1.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: Tue Aug 6 23:11:24 2013 BST
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
See vendor-specific Attribute list for marginal Attributes.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 241) Self-test routine in progress...
10% of test remaining.
Total time to complete Offline
data collection: ( 653) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off supp ort.
Suspend Offline collection upon new
command.
No 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: ( 234) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103b) 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 090 088 006 Pre-fail Always - 210125600
3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 095 095 020 Old_age Always - 5456
5 Reallocated_Sector_Ct 0x0033 070 070 036 Pre-fail Always - 1237
7 Seek_Error_Rate 0x000f 083 060 030 Pre-fail Always - 202918235
9 Power_On_Hours 0x0032 090 090 000 Old_age Always - 8919
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 098 098 020 Old_age Always - 2731
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 859
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1
190 Airflow_Temperature_Cel 0x0022 050 028 045 Old_age Always In_th e_past 50 (0 197 57 35)
194 Temperature_Celsius 0x0022 050 072 000 Old_age Always - 50 (0 19 0 0)
195 Hardware_ECC_Recovered 0x001a 033 033 000 Old_age Always - 210125600
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
ATA Error Count: 863 (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 863 occurred at disk power-on lifetime: 8890 hours (370 days + 10 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 00 07 00 00 00 Error: UNC at LBA = 0x00000007 = 7
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 00 00 00 e0 00 00:04:05.950 READ DMA
ec 00 00 07 00 00 a0 00 00:04:05.925 IDENTIFY DEVICE
c8 00 08 00 00 00 e0 00 00:04:04.607 READ DMA
ec 00 00 07 00 00 a0 00 00:04:04.582 IDENTIFY DEVICE
c8 00 08 00 00 00 e0 00 00:04:03.295 READ DMA
Error 862 occurred at disk power-on lifetime: 8890 hours (370 days + 10 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 00 07 00 00 00 Error: UNC at LBA = 0x00000007 = 7
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 00 00 00 e0 00 00:04:04.607 READ DMA
ec 00 00 07 00 00 a0 00 00:04:04.582 IDENTIFY DEVICE
c8 00 08 00 00 00 e0 00 00:04:03.295 READ DMA
ec 00 00 07 00 00 a0 00 00:04:03.270 IDENTIFY DEVICE
c8 00 08 00 00 00 e0 00 00:04:01.972 READ DMA
Error 861 occurred at disk power-on lifetime: 8890 hours (370 days + 10 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 00 07 00 00 00 Error: UNC at LBA = 0x00000007 = 7
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 00 00 00 e0 00 00:04:03.295 READ DMA
ec 00 00 07 00 00 a0 00 00:04:03.270 IDENTIFY DEVICE
c8 00 08 00 00 00 e0 00 00:04:01.972 READ DMA
ec 00 00 07 00 00 a0 00 00:04:01.947 IDENTIFY DEVICE
c8 00 08 00 00 00 e0 00 00:04:00.620 READ DMA
Error 860 occurred at disk power-on lifetime: 8890 hours (370 days + 10 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 00 07 00 00 00 Error: UNC at LBA = 0x00000007 = 7
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 00 00 00 e0 00 00:04:01.972 READ DMA
ec 00 00 07 00 00 a0 00 00:04:01.947 IDENTIFY DEVICE
c8 00 08 00 00 00 e0 00 00:04:00.620 READ DMA
ec 00 00 07 00 00 a0 00 00:04:00.595 IDENTIFY DEVICE
c8 00 08 00 00 00 e0 00 00:03:59.278 READ DMA
Error 859 occurred at disk power-on lifetime: 8890 hours (370 days + 10 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 00 07 00 00 00 Error: UNC at LBA = 0x00000007 = 7
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 00 00 00 e0 00 00:04:00.620 READ DMA
ec 00 00 07 00 00 a0 00 00:04:00.595 IDENTIFY DEVICE
c8 00 08 00 00 00 e0 00 00:03:59.278 READ DMA
b0 d5 01 e0 4f c2 00 00 00:03:59.277 SMART READ LOG
ec 00 00 07 00 00 a0 00 00:03:59.252 IDENTIFY DEVICE
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA _of_first_error
# 1 Extended offline Self-test routine in progress 10% 8919 -
# 2 Extended offline Interrupted (host reset) 00% 8908 -
# 3 Extended offline Interrupted (host reset) 00% 8897 -
# 4 Extended offline Interrupted (host reset) 00% 8895 -
# 5 Extended offline Interrupted (host reset) 00% 8895 -
# 6 Short offline Completed without error 00% 8890 -
# 7 Short offline Completed: read failure 90% 8890 7
# 8 Short offline Completed: read failure 90% 8889 6
# 9 Short offline Completed: read failure 90% 8889 6
#10 Short offline Completed: read failure 90% 8889 6
#11 Short offline Completed: read failure 90% 8889 6
#12 Short offline Completed: read failure 90% 8889 6
#13 Short offline Completed: read failure 90% 8889 6
#14 Short offline Completed: read failure 90% 8889 6
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.
humax#