Autochk fails on fibre attached MSA1000 disks

[Harvey Smith]

I have 3 Proliant DL380 G5 servers with AE311A fibre cards and Smart Array P800 controller. Each has an MSA1000 directly attached via fibre.

Setting the disks to dirty using fsutil (eg fsutil dirty set c:) should invoke a chkdsk at reboot and it does for all of the disks attached to the P800 controller. However none of the disks attached to the AE311A fibre channel card run a autocheck when the server reboots. Running fsutil dirty query after the server reboots shows that the disks are still marked dirty. Manually performing a chkdsk /f works.

Autocheck is not disabled for any disks reg value HKLM\system\currentcontrolset\control\session manager\BootExecute is set to autocheck autochk *

All servers have Windows server 2003 R2 SP2 installed. Each server has had the firmware patched to 7.90 and PSP 7.90 is installed. No additional software is installed.

AE311A BIOS is 1.16
Smart Array P800 firmware is 4.06
MSA 1000 firmware is 5.20.

Does anybody have any solutions to this problem?

[James ~ Happy Dude]

Hello Harvey,

Refer:
http://support.microsoft.com/kb/160963
Does this helps ?

Regards.

[Harvey Smith]

Unfortunately not - I have done some further testing and the same problem does not happen with a DL380 G5 fitted with a Smart Array P400 controller, using the same fibre channel card and MSA1000. I need to check the firmware and updates applied to the DL380 G5 with the P400 controller but, I am suspicious that this behaviour is linked to the P800 controller.

[Harvey Smith]

I have discovered that the problem is caused by the HP NC-Series Multifunction driver for windows server included in PSP v.7.90 cp007676.exe (3.4.10.0). With this driver installed the autocheck will not work with fibre attached disks. Rolling back the driver to either cp007290.exe (3.0.7.0) from PSP 7.80 or cp007020.exe (2.8.18.0) from PSP 7.70 fixes the problem.

(NOTE: The driver cp007290.exe prevents the server being shutdown correctly, it will automatically reboot instead of shutting down with this driver installed)

[Harvey Smith]

The driver for the NC373i multifunction network card 3.4.10.0 is the cause of the problem. I have rolled back to to 2.8.18.0 driver.