Discussion:
[smartmontools-support] how to figure out if the captive short self-test has finished -
shirish शिरीष
2016-08-13 07:21:05 UTC
Permalink
Hi all,

I ran the captive short self-test and it shows up as -

# smartctl --captive -t short /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.6.0-1-amd64] (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
captive mode".
Drive command "Execute SMART Short self-test routine immediately in
captive mode" successful.
Testing has begun.
Please wait 1 minutes for test to complete.
Test will complete after Sat Aug 13 18:07:24 2016

Now should I wait for 5 minutes or something to know if the test is completed ?

Is there a way to see the progress of the test to know where it is at ?
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
Christian Franke
2016-08-13 14:17:57 UTC
Permalink
Post by shirish शिरीष
I ran the captive short self-test and it shows up as -
# smartctl --captive -t short /dev/sdb
...
Sending command: "Execute SMART Short self-test routine immediately in
captive mode".
Drive command "Execute SMART Short self-test routine immediately in
captive mode" successful.
Testing has begun.
Please wait 1 minutes for test to complete.
Test will complete after Sat Aug 13 18:07:24 2016
Now should I wait for 5 minutes or something to know if the test is completed ?
Is there a way to see the progress of the test to know where it is at ?
The captive test has already finished if the ATA command returns and
smartctl prints "Drive command ... successful". The remaining output
lines are misleading if --captive is used.

Note that captive tests are not recommended (see smartctl man page).
Very long captive tests may not work at all because the ATA driver
aborts with timeout.

Thanks,
Christian

Loading...