Re: longtime for extended self-test and status where it is at

shirish wrote:
> I have a 2 TB external USB bus-powered hdd. A Seagate ST2000LM003
> HN-M201RAD  which is also used by Samsung now as Seagate bought
> Samsung some years ago.
>
> I tried -c to figure out how much time it will take to do the extended
> self-test and it shows -
>
> # smartctl -c /dev/sdb
> ...
> Self-test execution status:      (  38)	The self-test routine was interrupted
> 					by the host with a hard or soft reset.
> ...
> Extended self-test routine
> recommended polling time: 	 ( 373) minutes.
> ...
>
> Which basically comes down to 6.5 hours or thereabouts. While this I
> can do this it would be nice if there was a way to check the progress
> once in a while.

During an offline test, the progress is reported by the above "Self-test 
execution status" in 10% steps. The smartd daemon logs this info if -l 
selfteststs is enabled.

Do not use --captive.

Be aware that the USB bridge may abort the test if the drive is not 
accessed frequently, see:
https://www.smartmontools.org/wiki/FAQ#Whyarelongself-testskeepgettinginterrupted

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