View Single Post
  #6  
Old November 19th 18, 11:34 PM posted to comp.sys.ibm.pc.hardware.storage
VanguardLH[_2_]
external usenet poster
 
Posts: 1,453
Default SMART Self-test duplicate logs?

Tom Del Rosso wrote:

I thought smartmontools output was easily recognizable. Of course it
uses the scheduler. Can the tests overlap? You start it once and it
will abort if there is a reboot, but then it doesn't restart by itself,
and if it did restart the 'power-on-hours' column would show a higher
number.


My guess for your unidentified OS is that it is a Linux variant.
Windows users can visit this newsgroup, too. Perhaps SmartMon is
included, by default, in the the Linux distros. It isn't in Windows, so
the number of Windows users that use Smartmon is small and of that small
populace not all would recognize the output was from Smartmon.

I don't have a Linux box to check the options in its scheduler. In
another reply, you said there was a prompt that the job was already
running ("try to start a second test it refuses with message a test is
already running"). I'm assuming that is a message from Smartmon itself
refusing to start another process for itself rather than a message from
the scheduler of trying to run a 2nd copy of a scheduled job.

You get doubled Smartmon logs (presumably for the same scheduled job).
In each log, is one hard disk specified for getting tested, or does
Smartmon let you specify a range, list, or to scan all discovered disks?

From what I saw in the man pages for -t (tests), "Note also that if a
computer is shutdown or power cycled during a self-test, no harm should
result. The self-test will either be aborted or will resume
automatically." There is a "pending" argument to the -t switch.

Is the log reporting an aborted [long] test?

https://www.smartmontools.org/wiki/F...inginterrupted

There's nothing at the end of a Smartmon log to indicate why testing was
stopped or aborted which would would indicated the cause of a subsequent
Smartmon log?