| Author |
 Topic  |
|
|
timberk
Old Timer
USA
535 Posts
Status: offline |
|
|
joe_elway
Honorable But Hopeless Addict
Ireland
6369 Posts
Status: offline |
|
|
timberk
Old Timer
USA
535 Posts
Status: offline |
 Posted - 05/29/2009 : 11:05:15 AM
|
Agreed, it is worrying. I was attempting to install Service Pack 2 on my production Hyper-V host when this error pops up:
quote:
The Windows Installer has detected that this system is configured with MPIO and that there are devices supported by the Microsoft Device Specific Module (MSDSM). If you 1) install Service Pack 2 (SP2) before installing update KB967752 (http://go.microsoft.com/fwlink/?LinkId=142875) and then 2) uninstall the service pack, you will lose access to the MSDSM-supported devices. In addition, your system will experience a system bugcheck error if the system is also booted from these MSDSM-supported devices. To correct this problem, install update KB967752 (http://go.microsoft.com/fwlink/?LinkId=142875) before installing SP2.
You'd think that Hotfix 967752 would have been included in the Service Pack.
~tb |
 |
|
|
joe_elway
Honorable But Hopeless Addict
Ireland
6369 Posts
Status: offline |
|
|
timberk
Old Timer
USA
535 Posts
Status: offline |
Posted - 05/29/2009 : 11:57:56 AM
|
After installing Hotfix 967752, I was able to get Service Pack 2 successfully installed (I think)on my Hyper-V host. It took two reboots though, which is one more than every other SP 2 install I've done.
~tb |
Edited by - timberk on 05/29/2009 11:59:17 AM |
|
|
|
wlazara
Honorable But Hopeless Addict
USA
2035 Posts
Status: offline |
Posted - 05/30/2009 : 7:01:18 PM
|
| Yikes. I've been really wary of installing SP2 on any machines just yet. |
-Wes Lazara |
|
|
|
joe_elway
Honorable But Hopeless Addict
Ireland
6369 Posts
Status: offline |
|
|
joe_elway
Honorable But Hopeless Addict
Ireland
6369 Posts
Status: offline |
Posted - 07/07/2009 : 07:42:29 AM
|
I recently updated and tested.
1) VMM 2008 has a problem with hosts on different SP's. It won't allow you to failover VM's and this probably affects Pro Tips. The VMM team was notified via the MVP newsgroups. You can still use the Failover Clustering MMC to manually and automatically move VM's. I checked and this is supported.
2) I didn't apply the MPIO SP2 updates above.
3) I tested MPIO during a PDU swapout in blade and SAN racks. This brough down either side of the fibre network, one at a time. MPIO wokred without a hitch on our HP BL460 G1 blades with Brocade HBA mezzanine cards. The firmwares were last updated in Nov 2008.
I hate the Emulex ones because I had over 25% failure rate in 2-3 months ina 128 blade farm. I understand they still regularly fail since I left there at the end of 2007. |
Aidan Finn
MCSE, MVP (Virtual Machine: Systems Administration)
IT Blog: http://www.aidanfinn.com
My Photography: http://www.aidanfinnphoto.com/
Windows User Group - Ireland: http://ws-ugi.spaces.live.com
Twitter: http://twitter.com/joe_elway |
|
|
|
jerseyphil
Welcome Newcomer
United Kingdom
1 Posts
Status: offline |
Posted - 10/07/2009 : 07:44:21 AM
|
Im experiencing the issue above with Windows 2008 SP2 in an MPIO environment.
I applied the patch before SP2 (http://support.microsoft.com/kb/957316/) but following the system reboot connectivity to the SAN was lost.
Does anyone have any further input on this issue?
|
|
|
|
timberk
Old Timer
USA
535 Posts
Status: offline |
Posted - 10/07/2009 : 10:39:24 AM
|
Hello jerseyphil,
Did you export the registry key, as described in kb957316?
quote:
When you apply this hotfix to the system with the MPIO claimed Disk drives, you have to follow these Steps:
1. Export the following registry key:
HKLM\System\CurrentControlSet\Services\MSDSM\Parameters
2. Install the hotfix.
3.Import the following saved registry key:
HKLM\System\CurrentControlSet\Services\MSDSM\Parameters
What do the Event Logs have to say?
~tb |
|
|
|
mikesic
Welcome Newcomer
1 Posts
Status: offline |
Posted - 10/23/2009 : 1:11:33 PM
|
Article 967752 is confusing:
"To avoid this problem, install hotfix 967752 before you install Windows Server 2008 Service Pack 2."
Fine, so far so good.
It then goes on about registry fixes below. So which is it? Install hotfix AND make registry fixes (and pray!), or install hotfix OR make registry changes?
"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
Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MPDEV
Copy the entries under the MPDEV subkey, and then enter them under the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msdsm\Parameters\DsmSupportedDeviceList
Restart the computer, or disable and then enable host bus adapter (HBA).
For the Boot Volume
Mask logical unit number (LUN) to another Windows Server 2008-based computer, and then mount the boot volume.
Locate the registry (.reg) files.
Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MPDEV
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
Unmount the boot volume, and then unmask the LUN from the Windows Server 2008-based computer.
Mask the LUN to the Windows Server 2008-based computer for SAN Boot.
Restart the computer, and then boot from this LUN." |
|
|
| |
Topic |
|
Windows Server 2008 SP2 and MPIO issue and fix
