strongs words for someone thats doesnt seem to even get a smart check running… anyways reported for inappropriate comment
I always check with df first.
I pulled all the files off, wiped it, formatted it, did smart scan, moved everything back, and now it’s back on the Vero automounted with all the other drives, so now its sdd.
osmc@osmc:~$ sudo smartctl -d sat -i /dev/sdd
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: ST5000LM000-2AN170
Serial Number: WCJ1L927
LU WWN Device Id: 5 000c50 0b5b5e2d8
Firmware Version: 0001
User Capacity: 5,000,981,078,016 bytes [5.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5526 rpm
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Thu Sep 26 22:11:44 2019 MST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
At least it’s reporting that SMART is enabled now.
Try running the test without the -C option. I’m not sure exactly how that will change what happens when you run the test.
Also try with the --all option again.
Here’s what I got:
osmc@osmc:~$ sudo smartctl -d sat,12 -t short /dev/sdd
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 1 minutes for test to complete.
Test will complete after Thu Sep 26 22:21:46 2019
Use smartctl -X to abort test.Wait a few minutes, and then run again with --all (instead of -t short).
And the results:
osmc@osmc:~$ sudo smartctl -d sat,12 -a /dev/sdd
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: ST5000LM000-2AN170
Serial Number: WCJ1L927
LU WWN Device Id: 5 000c50 0b5b5e2d8
Firmware Version: 0001
User Capacity: 5,000,981,078,016 bytes [5.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5526 rpm
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Thu Sep 26 22:23:28 2019 MST
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: ( 0) 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: ( 825) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x30a5) SCT Status 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 076 064 006 Pre-fail Always - 38255219
3 Spin_Up_Time 0x0003 097 096 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 579
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 072 060 045 Pre-fail Always - 16411755
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 2198 (249 131 0)
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 238
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
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 098 098 000 Old_age Always - 8590065666
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 057 046 040 Old_age Always - 43 (Min/Max 34/45)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 1
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 290
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 872
194 Temperature_Celsius 0x0022 043 054 000 Old_age Always - 43 (0 23 0 0 0)
195 Hardware_ECC_Recovered 0x001a 076 064 000 Old_age Always - 38255219
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
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 327 (215 244 0)
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 21056737147
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 16402999462
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 2
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 2 occurred at disk power-on lifetime: 2198 hours (91 days + 14 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 00 00 00 00 00 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
00 00 00 00 00 00 00 ff 02:39:06.348 NOP [Abort queued commands]
b0 d4 00 81 4f c2 00 00 02:38:45.718 SMART EXECUTE OFF-LINE IMMEDIATE
b0 d0 01 00 4f c2 00 00 02:38:45.625 SMART READ DATA
ec 00 01 00 00 00 00 00 02:38:45.585 IDENTIFY DEVICE
e7 d5 08 10 79 04 00 00 02:38:44.296 FLUSH CACHE
Error 1 occurred at disk power-on lifetime: 2198 hours (91 days + 14 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 00 00 00 00 00 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
00 00 00 00 00 00 00 ff 02:36:39.299 NOP [Abort queued commands]
b0 d4 00 81 4f c2 00 00 02:36:18.911 SMART EXECUTE OFF-LINE IMMEDIATE
b0 d0 01 00 4f c2 00 00 02:36:18.803 SMART READ DATA
e7 00 01 00 00 00 00 00 02:36:18.765 FLUSH CACHE
ec 00 01 00 00 00 00 00 02:36:18.763 IDENTIFY DEVICE
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% 2198 -
# 2 Short captive Interrupted (host reset) 70% 2198 -
# 3 Short captive Interrupted (host reset) 70% 2198 -
# 4 Short offline Completed without error 00% 2174 -
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.Here’s with --all instead of -t short:
osmc@osmc:~$ sudo smartctl -d sat,12 --all /dev/sdd
smartctl 6.6 2016-05-31 r4324 [aarch64-linux-3.14.29-152-osmc] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: ST5000LM000-2AN170
Serial Number: WCJ1L927
LU WWN Device Id: 5 000c50 0b5b5e2d8
Firmware Version: 0001
User Capacity: 5,000,981,078,016 bytes [5.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5526 rpm
Form Factor: 2.5 inches
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Thu Sep 26 22:28:03 2019 MST
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: ( 0) 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: ( 825) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x30a5) SCT Status 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 076 064 006 Pre-fail Always - 38257099
3 Spin_Up_Time 0x0003 097 096 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 579
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 072 060 045 Pre-fail Always - 16416062
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 2198 (43 231 0)
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 238
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
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 098 098 000 Old_age Always - 8590065666
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 057 046 040 Old_age Always - 43 (Min/Max 34/45)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 1
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 290
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 872
194 Temperature_Celsius 0x0022 043 054 000 Old_age Always - 43 (0 23 0 0 0)
195 Hardware_ECC_Recovered 0x001a 076 064 000 Old_age Always - 38257099
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
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 327 (10 89 0)
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 21056739027
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 16402999462
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 2
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 2 occurred at disk power-on lifetime: 2198 hours (91 days + 14 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 00 00 00 00 00 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
00 00 00 00 00 00 00 ff 02:39:06.348 NOP [Abort queued commands]
b0 d4 00 81 4f c2 00 00 02:38:45.718 SMART EXECUTE OFF-LINE IMMEDIATE
b0 d0 01 00 4f c2 00 00 02:38:45.625 SMART READ DATA
ec 00 01 00 00 00 00 00 02:38:45.585 IDENTIFY DEVICE
e7 d5 08 10 79 04 00 00 02:38:44.296 FLUSH CACHE
Error 1 occurred at disk power-on lifetime: 2198 hours (91 days + 14 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 00 00 00 00 00 Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
00 00 00 00 00 00 00 ff 02:36:39.299 NOP [Abort queued commands]
b0 d4 00 81 4f c2 00 00 02:36:18.911 SMART EXECUTE OFF-LINE IMMEDIATE
b0 d0 01 00 4f c2 00 00 02:36:18.803 SMART READ DATA
e7 00 01 00 00 00 00 00 02:36:18.765 FLUSH CACHE
ec 00 01 00 00 00 00 00 02:36:18.763 IDENTIFY DEVICE
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% 2198 -
# 2 Short captive Interrupted (host reset) 70% 2198 -
# 3 Short captive Interrupted (host reset) 70% 2198 -
# 4 Short offline Completed without error 00% 2174 -
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.So that looks good, the test run at drive hour 2198 passed.
I tried with my internal drive on my Linux Mint laptop with the -C option, and I get:
# 1 Short captive Interrupted (host reset) 70% 25226 -
Seems like the -C option is problematical.
Since the short test passed, try the long test now.
Is the long test potentially destructive to the data?
I know in SeaTools it potentially is.
I don’t believe that it is. From the man page (and it also explains why -C is failing:
long - [ATA] runs SMART Extended Self Test (tens of minutes).
This is a longer and more thorough version of the Short Self
Test described above. Note that this command can be given dur‐
ing normal system operation (unless run in captive mode - see
the ´-C´ option below).Well, according to sudo smartctl -d sat,12 -c /dev/sdd the long test will take ~14 hours, so I’ll wait for an appropriate time for that to be ran.
Thanks a lot for all the help guys, I’m glad we’ve made it this far!
No way to know for sure now, but I’m betting -d sat,12 would have probably worked before even when I couldn’t get it to mount.
The test it self is not destructive. But as it will test the whole disk there is a potential that the disk fails in between which influence the data.
I run an extended offline test on all my disk every week
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 40943 - # 2 Extended offline Completed without error 00% 40775 - # 3 Extended offline Completed without error 00% 40607 - # 4 Extended offline Completed without error 00% 40439 - # 5 Extended offline Completed without error 00% 40271 - # 6 Extended offline Completed without error 00% 40103 - # 7 Extended offline Completed without error 00% 39951 - # 8 Extended offline Completed without error 00% 39783 - # 9 Extended offline Completed without error 00% 39615 - #10 Extended offline Completed without error 00% 39447 - #11 Extended offline Completed without error 00% 39279 - #12 Extended offline Completed without error 00% 39111 - #13 Extended offline Completed without error 00% 38943 - #14 Extended offline Completed without error 00% 38776 - #15 Extended offline Completed without error 00% 38608 - #16 Extended offline Completed without error 00% 38440 - #17 Extended offline Completed without error 00% 38272 - #18 Extended offline Completed without error 00% 38114 - #19 Extended offline Completed without error 00% 37946 - #20 Extended offline Completed without error 00% 37778 - #21 Extended offline Completed without error 00% 37610 -
The short and long drive self tests here are the same as with seatools. In either case the drive test is only a read test and is not destructive. The reason why they many sometimes be viewed as such is because running that test for almost 15hrs stresses the drive and will probably run it fairly warm. If your drive is healthy it will not care. With modern drives this kind of a test is actually good for the drive health because it does not just read the 1’s and 0’s but it reads how strongly they are stored. If it runs across something weak it will move any data and remap proactively for data integrity sake. On most drives this is completely internal to the drive and it does not log or report back what it is doing.
No, in SeaTools if it finds bad sectors it will flag them and data will be lost or corrupted
You can run the test while the drive is in use.
I’m running -t long right now on /dev/sda on the laptop that I’m using as I type.
Bad sectors are sectors that cannot be read. What I was referring to is weak sectors that can currently be read but not as strongly as they should. The two are not the same.
Also if the sector is bad the data is already lost or corrupted, the computer just doesn’t know about it yet.
That is referring to the drive trying to repair a bad sector or leaving it alone. It will try to read it a few times and will play the odds. Most of that is them covering their rear ends. The test does stress the drive. If it is on the edge that test may make it fail. That’s why you keep a backup. If the drive is not healthy it will fail anyway. This kind of a test will just speed it up.
The invoked long SMART test will simply stop in case of a found error; there is no destructive behaviour of the internal disk’s test routine.
But … if you run a long smart test it will most possible end in an “aborted by host” state after some minutes since the disk has to be kept busy before the kernel tries to hibernate the idle USB drive.
For that I let run a tiny script in a second session or background job till the SMART test finished
while true
do
sudo smartctl -d sat,12 -Hc /dev/sdd
sleep 60
done
(-Hc shows the health state and capabilities which includes the Self-test execution status)
After all at least you know whether the disk has any surface issue or not.
1 Like