Server 2012 R2 Hyper-V File Server locking up on data directory or network shares

[Dragnix122507]

Hello everyone,

I have a server that was just recently rebuild running on an HP ProLiant DL380 Gen9 on a full instance of Windows Server 2012 R2 running in a Hyper-V Virtual Machine that seems to be locking up when accessing it's data directory (D Drive in this case). It will operate just fine for a couple hours and then the D Drive will become inaccessible. On occasion we'll also have an issue with the same machine where it cannot be access over the network to the shares it hosts via IP, DNS or any other means but the shares are browse-able locally on the D Drive. The virtual machine is running DFS and replicates with another file server over a VPN on the exact same hardware that has never had this problem. We have been working on this issue now off and on for a few weeks but really need to find a final resolution. We have tried rebuilding the full instance of the Hyper-V vm, letting DFS re-create all the data on the secondary server and moving it even to a different physical piece of hardware that we keep for backup purposes (an older Dell PowerEdge 1950).

On the ProLiant DL380 Gen9 (about one year old today) we have an above board RAID controller and are running eight SAS drives. The RAID 10 ADG is on six of the drives and the primary OS is on the other 2 in a RAID 1.

Any ideas what might be causing this?

Thank you

 

[TurricanII]

It's odd that you have rebuilt the VM and moved it to another host and still have the problem.
Overactive antivirus on the VM?
Anything in the event logs of the VM at the material time?
Network Adapter or Legacy Network Adapter? Remove and re-add one or the other type.
Compare virtual switch settings with the trouble free and troublesome Hyper-V hosts.
Is the virtual server using a static IP address?
Could this be an issue on a managed network switch port - some sort of QoS/smart 'protection'? Any port security (limit on number of allowed MAC addresses)?
Is the host connected to the LAN to a proper switch or could it be patched into some 8 port desktop switch as a bodge?
Any chance of an IP conflict?
SR-IOV enabled?

 

[Markverhyden]

By rebuild, what exactly do you mean? From scratch, meaning everything was manually added back in? Or was a new VM spun up and system state restored from a backup?

 

[Dragnix122507]

By rebuild, what exactly do you mean? From scratch, meaning everything was manually added back in? Or was a new VM spun up and system state restored from a backup?

It was a complete rebuild. We wiped the server, reinstalled Windows Server 2012 R2, re-added to domain (using the same name to replace the old one) and re-added to the DFS group. Then we let it replicate over the weekend.

 

[Dragnix122507]

It's odd that you have rebuilt the VM and moved it to another host and still have the problem.
Overactive antivirus on the VM?
Anything in the event logs of the VM at the material time?
Network Adapter or Legacy Network Adapter? Remove and re-add one or the other type.
Compare virtual switch settings with the trouble free and troublesome Hyper-V hosts.
Is the virtual server using a static IP address?
Could this be an issue on a managed network switch port - some sort of QoS/smart 'protection'? Any port security (limit on number of allowed MAC addresses)?
Is the host connected to the LAN to a proper switch or could it be patched into some 8 port desktop switch as a bodge?
Any chance of an IP conflict?
SR-IOV enabled?

Thanks, we'll try these ideas out ASAP.

 

[YeOldeStonecat]

What NICs are in the host? Broadcoms or a good Intel add-on card?
If the stock onboard Broadcoms...have you disabled VMQ in the NIC settings?