You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GSmartControl version: [Are you using the latest released version or git?] 1.1.4
OS: [e.g. openSUSE Linux 15.4] Manjaro
Is your feature request related to a problem? Please describe.
If I leave a USB external WD disk attached for a while and then try to see its smart info, it shows a message box saying that it is getting the info, and then it fails and show the following:
If I click the left button, it says
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.31-2-MANJARO] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error device will be ready soon
If this is a USB connected device, look at the various --device=TYPE variants
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
It only works if I right-click the drive and select "re-read data".
Describe the solution you'd like
When it fails to retrieve the info, maybe GsmartControl can automatically try re-read the data?
The text was updated successfully, but these errors were encountered:
Hi,
Can you please try to run smartctl manually when the drive is asleep, and re-run it immediately a few times to see how long it takes for the drive to wake up?
You can check which commands GSmartControl executes in Exection Log.
Version and Environment
Is your feature request related to a problem? Please describe.
If I leave a USB external WD disk attached for a while and then try to see its smart info, it shows a message box saying that it is getting the info, and then it fails and show the following:
If I click the left button, it says
It only works if I right-click the drive and select "re-read data".
Describe the solution you'd like
When it fails to retrieve the info, maybe GsmartControl can automatically try re-read the data?
The text was updated successfully, but these errors were encountered: