Re: how to figure out if the captive short self-test has finished -

shirish wrote:
> 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


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. http://sdm.link/zohodev2dev