Custom Query (1560 matches)

I observed that when smartd is polling for SMART data, Windows sometimes spins up a disk that is powered down even when “-n standby” is used in smartd.conf. The log will report that the disk is in standby mode and checks are suspended. Still you can hear that the disk is starting.

I found that this behavior is caused by smartd when opening the (physical) disk device. Smartd opens the disk asking for full read and write permissions by default. (Only when it does not have admin rights, it opens the disk with ‘0’ permissions.) But opening with full read and write permissions sometimes results in Windows spinning up the disk, most likely to consolidate Windows’ internal state with the disk. However, to query the disk’s power state, you only need a handle to query the drive’s metadata, without any read or write permissions.

The attached patch adds a new function to the base class ‘smart_device’: ‘check_os_powermode()’. The generic default implementation returns true to indicate power up or undetermined. The Win32 implementation uses Windows’ GetDevicePowerState API, and returns false when the OS indicates that the device is in low-power state. However, the point is when the ‘smart_device’ is not already opened, ‘check_os_powermode()’ opens the device temporarily using ‘0’ permissions to open only a handle for querying device metadata, and so prevents the disk from spinning up. (Even when admin rights would be available.)

Hello,

6.4.1 blocks the T3600 DELL PC (over the keyboard response) when the service starts, when the auto -d option is specified in the smartd.conf

If the debug (smartd -d) below

smartd 6.4 2015-06-04 r4109 [x86_64-w64-mingw32-win7-sp1] (sf-6.4-1)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

Opened configuration file C:/Program Files/SmartMon.old/smartd.conf
Configuration file C:/Program Files/SmartMon.old/smartd.conf was parsed, found DEVICESCAN, scanning devices
Device: /dev/sda [SAT], opened
Device: /dev/sda [SAT], WDC WD5000AAKX-75U6AA0, S/N:WD-WCC2EU802806, WWN:5-0014ee-2b29c36c5, FW:19.01H19, 500 GB
Device: /dev/sda [SAT], found in smartd database: Western Digital Blue
Device: /dev/sda [SAT], not capable of SMART Health Status check
CHECK POWER MODE: incomplete response, ATA output registers missing
Device: /dev/sda [SAT], no ATA CHECK POWER STATUS support, ignoring -n Directive
Device: /dev/sda [SAT], is SMART capable. Adding to "monitor" list.
Device: /dev/sdb [SAT], opened
Device: /dev/sdb [SAT], WDC WD5000AAKX-75U6AA0, S/N:WD-WCC2EU614318, WWN:5-0014ee-207f17163, FW:19.01H19, 500 GB
Device: /dev/sdb [SAT], found in smartd database: Western Digital Blue
Device: /dev/sdb [SAT], not capable of SMART Health Status check
CHECK POWER MODE: incomplete response, ATA output registers missing
Device: /dev/sdb [SAT], no ATA CHECK POWER STATUS support, ignoring -n Directive
Device: /dev/sdb [SAT], is SMART capable. Adding to "monitor" list.
Device: /dev/csmi0,0, opened
Device: /dev/csmi0,0, packet devices [this device CD/DVD] not SMART capable
Unable to register ATA device /dev/csmi0,0 at line 1 of file C:/Program Files/SmartMon.old/smartd.conf
Device: /dev/csmi1,0, opened
Device: /dev/csmi1,0, not ATA, no IDENTIFY DEVICE Structure
Unable to register ATA device /dev/csmi1,0 at line 1 of file C:/Program Files/SmartMon.old/smartd.conf
Device: /dev/csmi1,1, opened
Device: /dev/csmi1,1, WDC WD5000AAKX-75U6AA0, S/N:WD-WCC2EU614318, WWN:5-0014ee-207f17163, FW:19.01H19, 500 GB
Device: /dev/csmi1,1, found in smartd database: Western Digital Blue
Device: /dev/csmi1,1, is SMART capable. Adding to "monitor" list.
Monitoring 3 ATA and 0 SCSI devices
Device: /dev/sda [SAT], opened ATA device

After this line is completely blocked windows, windows of a sudden stop is needed to stop :(

If the ATA option is indicated in the smartd.conf, the drives are not recognized (it has no windows blocking)

When I try to execute the update-smart-drivedb.ps1 script in a Powershell or Command Prompt CLI (running as Administrator or not) I receive the error:

& : The term 'gpg.exe gpg.exe' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At update-smart-drivedb.ps1:500 char:16
+   $($input | & $cmdobj @args 2>&1) | %{ $_.ToString() }
+                ~~~~~~~
    + CategoryInfo          : ObjectNotFound: (gpg.exe gpg.exe:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

update-smart-drivedb.ps1 version 5515 2023-07-24 12:58:25Z from smartmontools 7.4, on Windows 10 22H2 64-bit, Powershell 10.0.19041.3636. gpg.exe is in $PATH and works.