Monday, January 31, 2011

SDDDSM vs DISK MANAGER&DEVICE MANAGER

For some reason (unknown) after the installation of two VSS hotfixes, (KB940349: http://support.microsoft.com/kb/940349
KB951568: http://support.microsoft.com/kb/951568) all the SAN LUNs (on SVC, using SDDDSM 2.4.0.2 Nov 2009 as multipath software) stopped to appear on the Disk Manager. Although they were visible on the Device Manager.

System Event log : shows event ID 271
Event Type: Information
Event Source: PlugPlayManager
Event Category: None
Event ID: 271
Date: 01/30/2011
Time: 1:35:54 AM
User: N/A
Computer: MLISINVWPORDBD1
Description:
The Plug and Play operation cannot be completed because a device driver is preventing the device from stopping. The name of the device driver is listed as the vetoing service name below.

Vetoed device: MPIO\DISK&VEN_IBM&PROD_2145&REV_0000\1&7F6AC24&0&3630303530373638303138453033333230303030303030303030303030343634
Vetoing device: STORAGE\Volume\1&3735c57b&0&LDM#{5abb1f7e-8a56-11df-b068-806e6f6e6963}
Vetoing service name: FileSystem\Ntfs
Veto type 6: PNP_VetoDevice

When Windows attempts to install, upgrade, remove, or reconfigure a device, it queries the driver responsible for that device to confirm that the operation can be performed. If any of these drivers denies permission (query-removal veto), then the computer must be restarted in order to complete the operation.

User Action
Restart your computer.
---------------------------------------------------------------------------------
datapath query device worked fine :



---------------------------------------------------------------------------------
Tried to uninstall the hotfixes but didn't work.
Tried to update the HBA Drivers but didn't work.
---------------------------------------------------------------------------------
Until we saw the properties of the multipath disk at the device manager:


And this is how it looks on another server that the SAN LUNs were visible at the Disk Management:




SOLUTION: UNINSTALL SDDDSM and INSTALL A NEW VERSION OF SDDDSM.

It worked fine.

Update: check the version of dmadmin.exe if it's not the one from year 2008 then update it and try again.
The newer version of SDDDSM we installed was 2.4.3

0 comments:

Post a Comment