Custom Query (1560 matches)

The duration of the long (extended) self-test is reported as 7 minutes. Running the long self-test with smartctl (under linux) indeed takes 7 minutes. Running the extended self test under W7 with Data Lifeguard Diagnostics took about 4 hours and 30 minutes (same disk of course).

I also see that the conveyance test has the same recommended duration as the short self-test, which is unusual. I didn't run these tests on either systems.

Is this a bug in smartctl or in the disk?

By email, we saw that at 7am o'clock the script was unable to perform any tests for the / dev / sda disk; only for others.

By re-executing the script, the test was performed.

Because the first attempt was not possible? Is there any way to log more deeply to find out the cause?

The result of test at 7am o'clock

SMART Self-test log structure revision number 0 Warning: ATA Specification requires self-test log structure revision number = 1 No self-tests have been logged. [To run self-tests, use: smartctl -t]

The command on script: /usr/sbin/smartctl -i -l selftest -l error -H -t short {devices}

Thanks for replys

Hello support team,

I had install suse linux enterprise on my machine, however smartd not running. Status:

 ● smartd.service - Self Monitoring and Reporting Technology (SMART) Daemon
   Loaded: loaded (/usr/lib/systemd/system/smartd.service; enabled; vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Wed 2019-06-26 09:12:13 +07; 1h 26min ago
           ConditionVirtualization=false was not met
     Docs: man:smartd(8)
           man:smartd.conf(5)

So, what can i do to fix this? Please tell me. Thank,