If you are having issues with Hyper-V and KB 31661606 you might have a headache coming. If you patched your servers like we did you installed this patch on your Hyper-V hosts along with your Hyper-V guests. So what's wrong with that you say?
If you install this KB it will upgrade the version of the Integration Components for your Hyper-V Server which we have seen happen in the past. The catch is if you have this KB on your guest you will not be able to install the integration components on it. You will probably see error 14101 pop up. This is because the integration components and the patch are trying to update the same file and version. This means you can not have both of them installed on your Guest VM's. You are going to have to pick on or the other for now.......
To install the integration components, uninstall KB 31661606 from your guest VM and reboot. If you still have the install error which my guess is you will, you will also have to run this command to clean things up and reboot again. *Warning this step can take a while to run, so go grab some caffeine, your going to have a lot of work to do*
dism /online /cleanup-image /startcomponentcleanup
Once the integration components are installed you will not be able to install the KB again. It will either time out on Windows Update or if you try to download the patch and run it manually it will fail.
Hopefully Microsoft will come out with a fix soon, and hopefully it will not change the integration components again this soon for the fix.
Needless to say, MY BRAIN HERTZ.......................
Wednesday, June 29, 2016
Wednesday, May 18, 2016
Server 2003 VM - Hyper-V Guest Shutdown service wont start
No matter what I did I could not get the Hyper-V guest shutdown service to start on a Windows 2003 R2 Hyper-V guest running on a Windows 2012R2 cluster. The integration components were up to date and all of the devices were present in the guest's Device manager. I didn't want to force an uninstall of the Integration components if that is even possible so I kept digging.
To get it working I had to add edit the registry HKEY_Local_Machine\software\Microsoft\Windows NT\Current Version\SvcHost locate the ICService key and edit it adding vmicguestinterface. If it is already there you may have a different problem. After adding it I removed the Microsoft Hyper-V Guest Shutdown device from the server and rebooted. After the reboot it was re-detected and installed and the service was able to be started again!!!
Needless to say, MY BRAIN HERTZ
Friday, April 3, 2015
SAS Cabling for upgrading a Cisco UCS-C240M3 RAID controller Card from LSI 8110-4i back to a LSI 9266-8i
After a miserable fail with the LSA 8110-4i card in our Cisco C240M3 servers it was time to revert back to the original LSI 9266-8i cards. There are two main reasons for this first, no drivers from Cisco for Server 2012 R2 and apparent discontinue of the card in general.
This should be pretty simple right lets check the RAID Controller Considerations first.
Under Raid Controller cabling its seems straight forward and simple. I have 24 drives and a PCI-Style Card. SAS port 1 on the expander goes to SAS port 1 on the card and SAS port 2 on the expander goes to SAS port 2. SIMPLE!!!!!!! lets do it.
When we try to cable this up the Cisco Motherboard is clearly marked and we are ready to go, lets plug in the card and were done.. WAIT!!! the card is not marked SAS1 and SAS2 its marked J5A1 and J5B1. So time to get out the LSI product guide.
Yup just as I suspected the guide states the same so which is SAS1 and SAS2?
Looking further into the document we find that J5A1 supports SAS ports 0-3 and J5B1 supports SAS ports 4-7. We also find that the 9266-4i card does not have J5B1. So to me that J5A1 = SAS1 and J5B1=SAS2. Since this was a critical server with my ass on the line I contacted Cisco Support and after a few hours on the phone it was confirmed that my assumptions were correct.
Needless to say, MY BRAIN HERTZ
This should be pretty simple right lets check the RAID Controller Considerations first.
Under Raid Controller cabling its seems straight forward and simple. I have 24 drives and a PCI-Style Card. SAS port 1 on the expander goes to SAS port 1 on the card and SAS port 2 on the expander goes to SAS port 2. SIMPLE!!!!!!! lets do it.
When we try to cable this up the Cisco Motherboard is clearly marked and we are ready to go, lets plug in the card and were done.. WAIT!!! the card is not marked SAS1 and SAS2 its marked J5A1 and J5B1. So time to get out the LSI product guide.
Yup just as I suspected the guide states the same so which is SAS1 and SAS2?
Looking further into the document we find that J5A1 supports SAS ports 0-3 and J5B1 supports SAS ports 4-7. We also find that the 9266-4i card does not have J5B1. So to me that J5A1 = SAS1 and J5B1=SAS2. Since this was a critical server with my ass on the line I contacted Cisco Support and after a few hours on the phone it was confirmed that my assumptions were correct.
Tuesday, April 1, 2014
SAS Cabling for upgrading a Cisco UCS-C240M3 RAID controller Card from LSI 9266-8i to a LSI 8110-4i
Today my brain hertz because of the lack of documentation for the cabling of a LSI SAS 8110-4i RAID Card on a Cisco C240M3 Server running 24 SFF Drives.
First lets read the documentation that I was able to find:
Make sure to note from the Install and Service Guide:
I went to connect the 2 SAS cables to the new card 8110 and Houston we have a problem........ There is only one SAS Port on the new card and I had 2 cables to connect. There was no information in the documentation about a single SAS port or how this is supposed to be connected, so now what??
I opened a new support request with Cisco (John/Patrick this was not you, I opened a separate case for this issue as it was not related to our case) and they said to cable it the way the 9266 card was cabled, well that isn't going to work as I explained that is not possible and I am still waiting for an answer on that one...... No time to wait, we had another server that was purchased with the 8110 card in it, during a maintenance window I popped the server open and found the following for how to properly cable this card.
Needless to say, MY BRAIN HERTZ
First lets read the documentation that I was able to find:
- Installation and Service Guide
- RAID Controller Considerations
Make sure to note from the Install and Service Guide:
LSI Nytro MegaRAID 8110-4i Considerations
- This card is not supported with the SFF 16-drive direct-connect backplane version of the server.
- This card is supported only in slot 3 of the server.
- This card is supported only with the Red Hat Enterprise Linux 6.3 OS.
- This card is supported only in dual-CPU configurations.
- This card is supported only in servers that have Intel E5-2600 Series processors
(not Intel E5-2600 v2 Series processors). - This card is supported only with hard disk drives (not solid state drives).
- This card cannot coexist with any installed GPU card.
- This card cannot coexist with multiple RAID controllers.
I went to connect the 2 SAS cables to the new card 8110 and Houston we have a problem........ There is only one SAS Port on the new card and I had 2 cables to connect. There was no information in the documentation about a single SAS port or how this is supposed to be connected, so now what??
I opened a new support request with Cisco (John/Patrick this was not you, I opened a separate case for this issue as it was not related to our case) and they said to cable it the way the 9266 card was cabled, well that isn't going to work as I explained that is not possible and I am still waiting for an answer on that one...... No time to wait, we had another server that was purchased with the 8110 card in it, during a maintenance window I popped the server open and found the following for how to properly cable this card.
- 8110 Card SAS Port 1 - Connects to Expander SAS Port 1
- Expander SAS Port 2 - Connects to Embedded RAID SAS Port 1
Needless to say, MY BRAIN HERTZ
Subscribe to:
Posts (Atom)