This post is more than 5 years old
1 Rookie
•
61 Posts
0
55454
November 30th, 2012 18:00
PS6100XS and Hyper-V Server 2012 cluster: migrating storage between LUNs corrupts VM
Well I'm stumped! Been banging my head against this all week. Basically, moving a clustered VM between LUNs on the EqualLogic array corrupts the VM. Here's my setup:
- SAN 1: PS6100XS 6.0.1 firmware, 2 LUNs configured as CSV, 1 as Quarum disk
- SAN 2: FreeNAS 8.3.0, 2 LUNs (ZFS-formatted, for what it's worth)
- Server 1: Dell R310 running Windows Server 2012 with Hyper-V feature installed. 4 NICs: 2 teamed for LAN traffic, 2 for iSCSI with HIT KIT 4.5 configured for MPIO.
- Server 2: Old SuperMicro box running Windows Server 2012 with Hyper-V feature installed. 2 NICs: 1 for LAN traffic, 1 for iSCSI with HIT KIT 4.5 installed
- Cluster created and all validation tests passed
Here's what DOES work:
- Moving a VM between any LUNs if there's no activity on the VHDX
- Moving a VM from any LUN on the EqualLogic to any LUN on the FreeNAS or vice-versa
- Moving a VM between LUNs on the FreeNAS
- Moving a VM between LUNs on the EqualLogic BEFORE I created the cluster (just using Hyper-V Manager, not the Failover Cluster Manager)
Here's what kills the VM everytime:
- Create a VM via the Failover Cluster Manager - doesn't matter which node owns the storage or the VM - tried all combinations
- Take an active, powered-on VM and move it from one EqualLogic LUN to another EqualLogic LUN. The move reports success, but the VM will bluescreen at the end of the move and will no longer be able to boot. It's basically fried.
BTW, I've also tried disabling one of the iSCSI NICs on the R310 - that doesn't help either. Any ideas? I've got a case going with Dell EqualLogic support, but so far they've been stumped. Anyone got something like this working yet?
0 events found
No Events found!
jakesterpdx
1 Rookie
•
61 Posts
1
December 7th, 2012 13:00
Ok, after Dell tried about 5 different times to tell me my configuration was unsupported (they actually claimed that EPA software wasn't supported!) I finally got someone that gave me a workaround: disabling ODX by changing the reg key HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\FilterSupportedFeaturesMode from 0 to 1. Doing this "fixes" it, but it also takes away one of the coolest features of Server 2012 + EqualLogic: ODX! With ODX enabled, I can move 20GB in < 1 sec. With it disabled, it takes around 2 minutes, depending on network congestion.
hkraal
1 Rookie
•
41 Posts
0
December 3rd, 2012 02:00
No answer but in case you've missed it; It's seem like other people have the same problem:
Men.community.dell.com/.../19477315.aspx
FSGuest
7 Posts
0
April 3rd, 2013 16:00
Jakesterpdx, have you tried to install 2796995? I just want to know if ODX works after you installing 2796995 metioned above.
jakesterpdx
1 Rookie
•
61 Posts
1
April 3rd, 2013 17:00
Yes, it's working fine for us, too. That said - be sure to test with a throwaway VM the first time!