Had a 2003 Server VM go down because of a network/SAN connectivity issue. Upon starting the VM back up, it got stuck at the Windows splash screen indefinitely.
Tried booting into safe mode and got stuck on ACPITABL.DAT
Connected VM to 2003 Server ISO and booted off that
Hit R for recovery
Sat at Examining disk for 10-15 minutes
Finally got in and ran a checkdisk
SOLUTION: Ended up being an iSCSI disk that was connected to the VM in Hyper-V that was causing it to hang. When the iSCSI disk was unmounted, server booted up fine and it was remounted.
Broadcom has known issues with dropping connections in HyperV which is what HP uses in their FlexLOM cards which was resolved in version 16.8, we are on 16.4
Latest version is 220.127.116.11 from 10/2015
We have an Exchange environment on an HP Proliant DL380p Gen8. The VM’s came from old physical servers that were relocated to another site, ever since they were virtualized and put onto new hardware, there have been random network issues. We could ping between all Exchange servers one minute, next minute, cant ping anything.
Found an article on Microsoft site about a bug in Broadcom Chipset with HyperV and Server 2012 R2. Looked up the HP FlexLOM card, and sure enough, it uses BCM5719 chipset, one of the affected chipsets. Also the driver we are using is 16.4 and the issue was resolved in 16.8.
Had an issue over the weekend, one of our mailbox servers kept bluescreening. This particular VM has the C: and D: on storage iSCSI SAN.
Tried running checkdisk on C: and it bluescreened as well. HyperV manager shows the error “Cannot connect to virtual machine configuration storage”
The D: drive is showing uninitialized in disk management, and gives an error when trying to initialize.
Started getting “Windows – Delayed Write Failed” messages. Compression is not turned on on the HyperV servers local storage.
The iSCSI connections are provided by HP Lefthand SAN, 2 node cluster. One of the SAN nodes went down yesterday.
HP Lefthand Support Phone Number
putty into SAN node : port 16022
2 Lefthand SAN nodes
Each has a single 100mbit link….
When we brought SAN2 back online state, issue was resolved
My assumption is that the SAN couldn’t replicate fast enough with the load they have with Exchange on them, plus replicate the changes to the other SAN node, so they were out of sync when the 1 SAN node went down thus causing issues.
Backup Exec was not removing previous backup checkpoints and caused storage to fill causing VM’s to pause on that storage volume.
Ran the following command to remove old backup checkpoints and merge them to free up space to allow VM’s to resume.
Launch Powershell as Administrator on VMhost
Get-VMSnapshot -VMName ‘nameofvm’ -ComputerName ‘nameofVMhost’ | Remove-VMSnapshot