Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

A Windows Server 2008-based computer that is connected to a storage device over MPIO paths does not restart if the storage device is a boot device, or you lose access to the device if the device is a data volume


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You are running a Windows Server 2008-based computer that is connected to a storage device over some Microsoft Multipath I/O (MPIO) paths.
  • A Microsoft MPIO Device Specific Module is enabled for these MPIO paths.
  • The storage device is configured as an iSCSI boot device or a Storage Area Network (SAN) boot device.
  • You install and then uninstall Windows Server 2008 Service Pack 2.
  • You have installed hotfix 957316 on the Windows Server 2008-based computer.
In this scenario, the computer does not restart if the storage device is a boot device, or you lose access to the device if the device is a data volume.

Note For more information about hotfix 957316, click the following article number to view the article in the Microsoft Knowledge Base:
957316 Disk I/O errors occur after you restore a failed MPIO path on a Windows Server 2008-based computer

↑ Back to the top


Workaround

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

To avoid this problem, install hotfix 967752 before you install Windows Server 2008 Service Pack 2.

Scenario 1


If you have installed Windows Server 2008 Service Pack 2 and then you uninstalled the service pack or if you have not installed Windows Server 2008 Service Pack 2, follow these steps:
  • For the Data Volume
    1. Click Start, click Run, type regedit, and then click OK.
    2. In Registry Editor, locate the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MPDEV
    3. Copy the entries under the MPDEV subkey, and then enter them under the following subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msdsm\Parameters\DsmSupportedDeviceList
    4. Restart the computer, or disable and then enable host bus adapter (HBA).
  • For the Boot Volume
    1. Mask logical unit number (LUN) to another Windows Server 2008-based computer, and then mount the boot volume.
    2. Locate the registry (.reg) files.
    3. Click Start, click Run, type regedit, and then click OK.
    4. In Registry Editor, locate the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MPDEV
    5. Copy and paste the registry data in the registry subkey of step 4 under the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msdsm\Parameters\DsmSupportedDeviceList
    6. Unmount the boot volume, and then unmask the LUN from the Windows Server 2008-based computer.
    7. Mask the LUN to the Windows Server 2008-based computer for SAN Boot.
    8. Restart the computer, and then boot from this LUN.

Scenario 2


If you experience this problem when you prepare for the installation or removal of Windows Server 2008 Service Pack 2, follow these steps:
  • For the Data Volume
    1. Click Start, click Run, type regedit, and then click OK.
    2. In Registry Editor, locate the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MPDEV
    3. Copy and paste the registry data in the registry subkey of step 2 into the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msdsm\Parameters\DsmSupportedDeviceList
    4. Restart the computer, or disable and then enable the host bus adapter (HBA).
  • For the Boot Volume
    1. Mask logical unit number (LUN) to another Windows Server 2008-based computer and then mount the boot volume.
    2. Locate the registry (.reg) files.
    3. Click Start, click Run, type regedit, and then click OK.
    4. In Registry Editor, locate the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MPDEV
    5. Copy and paste the registry data in the registry subkey of step 4 into the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msdsm\Parameters\DsmSupportedDeviceList
    6. Unmount the boot volume, and then unmask the LUN from the Windows Server 2008-based computer.
    7. Mask the LUN to the Windows Server 2008-based computer for SAN Boot.
    8. Restart the computer, boot from this LUN.

      Note When you install Windows Server 2008 SP2, the
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msdsm\Parameters\DsmSupportedDeviceList
      registry subkey is backed up to the following file:
      %windir%\system32\DsmSupportedDeviceList.txt

↑ Back to the top


Resolution

Update information

The following files are available for download from the Microsoft Download Center:

Download the Update for Windows Server 2008 (KB967752) package now.

Download the Update for Windows Server 2008 for Itanium-based Systems (KB967752) package now.

Download the Update for Windows Server 2008 x64 Edition (KB967752) package now.

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Hotfix information

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductMilestoneService branch
    6.0.6000.16xxxWindows VistaRTMGDR
    6.0.6000.20xxxWindows VistaRTMLDR
    6.0.6001.18xxxWindows Vista SP1 and Windows Server 2008 SP1SP1GDR
    6.0.6001.22xxxWindows Vista SP1 and Windows Server 2008 SP1SP1LDR
  • Service Pack 1 is integrated into Windows Server 2008.
  • The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.
For all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Msdsm.infNot Applicable4,47411-Feb-200900:48Not Applicable
Msdsm.sys6.0.6001.2237493,15211-Feb-200905:34x86
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Msdsm.infNot Applicable4,48211-Feb-200900:43Not Applicable
Msdsm.sys6.0.6001.22374112,60811-Feb-200906:03x64
For all supported Itanium-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Msdsm.infNot Applicable4,47810-Feb-200923:46Not Applicable
Msdsm.sys6.0.6001.22374275,93611-Feb-200904:49IA-64

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008

File nameFile versionFile sizeDateTimePlatform
Package_for_kb967752_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,36211-Feb-200914:08Not Applicable
Package_for_kb967752_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42511-Feb-200914:08Not Applicable
Package_for_kb967752_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,41611-Feb-200914:08Not Applicable
Package_for_kb967752_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,41711-Feb-200914:08Not Applicable
Package_for_kb967752_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42011-Feb-200914:08Not Applicable
Package_for_kb967752_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42511-Feb-200914:08Not Applicable
X86_msdsm.inf_31bf3856ad364e35_6.0.6001.22374_none_ca8934fff4de5488.manifestNot Applicable1,66411-Feb-200915:29Not Applicable

Additional files for all supported x64-based versions of Windows Server 2008

File nameFile versionFile sizeDateTimePlatform
Amd64_msdsm.inf_31bf3856ad364e35_6.0.6001.22374_none_26a7d083ad3bc5be.manifestNot Applicable1,66611-Feb-200915:32Not Applicable
Package_for_kb967752_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,37011-Feb-200914:08Not Applicable
Package_for_kb967752_client~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43311-Feb-200914:08Not Applicable
Package_for_kb967752_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,42411-Feb-200914:08Not Applicable
Package_for_kb967752_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,42511-Feb-200914:08Not Applicable
Package_for_kb967752_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,42811-Feb-200914:08Not Applicable
Package_for_kb967752_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43311-Feb-200914:08Not Applicable

Additional files for all supported Itanium-based versions of Windows Server 2008

File nameFile versionFile sizeDateTimePlatform
Ia64_msdsm.inf_31bf3856ad364e35_6.0.6001.22374_none_ca8ad8f5f4dc5d84.manifestNot Applicable1,66511-Feb-200914:08Not Applicable
Package_for_kb967752_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42011-Feb-200914:08Not Applicable
Package_for_kb967752_sc~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42111-Feb-200914:08Not Applicable
Package_for_kb967752_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42411-Feb-200914:08Not Applicable
Package_for_kb967752_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42911-Feb-200914:08Not Applicable

↑ Back to the top


Keywords: atdownload, kbexpertiseinter, kbsurveynew, kbbug, kbfix, kbqfe, KB967752

↑ Back to the top

Article Info
Article ID : 967752
Revision : 4
Created on : 8/28/2009
Published on : 8/28/2009
Exists online : False
Views : 367