Opened 4 years ago

Closed 4 years ago

#598 closed defect (worksforme)

Windows hangs after smartd is started

Reported by: david Owned by:
Priority: major Milestone:
Component: smartd Version: 6.4
Keywords: windows Cc:

Description (last modified by Alex Samorukov)

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)

Change History (8)

comment:1 Changed 4 years ago by Alex Samorukov

Description: modified (diff)

comment:2 Changed 4 years ago by Alex Samorukov

Keywords: windows added

comment:3 Changed 4 years ago by Alex Samorukov

Could you please collect and send debug log for the smartd by running it with smartd -d -r ioctl,3 ? Also please check that Raid drivers + Raid FW are up to date.

Last edited 4 years ago by Alex Samorukov (previous) (diff)

comment:4 Changed 4 years ago by Alex Samorukov

Summary: Windows blockingWindows hangs after smartd is started

comment:5 Changed 4 years ago by Christian Franke

Milestone: undecided

Probably a bug in the SAT or CSMI implementation of the Windows driver of the SATA controller.

Which controller is used? The onboard Intel C600?

What is the version number of the (AHCI or IRST?) driver?

Does the same problem occur if single devices are checked with smartctl?

smartctl -x -d sat /dev/sda
smartctl -x -d sat /dev/sdb
smartctl -x /dev/csmi1,1 

comment:6 Changed 4 years ago by david

Thank you for your fast response, I will first check if our drivers are up to date.

comment:7 Changed 4 years ago by david

Hello,

Effectively making updating the driver fixes the problem,

Thank you for your help

comment:8 Changed 4 years ago by Christian Franke

Milestone: undecided
Resolution: worksforme
Status: newclosed

Driver update fixed the problem.

Note: See TracTickets for help on using tickets.