Hi

We have 2 X Windows 2012 Datacenter edition host servers configured with Hyper V clustering. With the cluster on each server there are 2 high available virtual servers which are again clustered and using for Symantec EV and MS SQL 2008 R2 which is working perfectly fine.

Later on these 2 host servers we assigned additional LUNs and configured virtual servers, which are not part of cluster for the development team. We received below error while restarting some of the servers 

Later we removed the attached SCSI controllers (1-3) which are configured on physical drives  I-K and then local virtual servers started successfully. Here we doubt this happened due to the drive letters used by the disks which are now part of clustered shared volumes.

We are looking for advise of configuring independent virtual servers on hosts which are part of Hyper-V cluster

Thanks in Advance

Hi LMS,

"Later we removed the attached SCSI controllers (1-3) which are configured on physical drives  I-K and then local virtual servers started successfully. Here we doubt this happened due to the drive letters used by the disks which are now part of clustered shared volumes. "

If I understand correctly , I-k are pass-through disks , please refer to the items below :

a. Please try to restart the HOST .

b. please try to re-add them to host then attach to VM .

 

"We are looking for advise of configuring independent virtual servers on hosts which are part of Hyper-V cluster"

Personally , you can just add Virtual server via hyper-v manager on one node and store VM files locally .

Best Regards

Elton Ji

Have you checked the disks haven't accidentally been mounted on the host?

Hi LMS,

How are things going ?

Best Regards

Elton Ji

Was deduplication running on the volume that held the virtual machine files?  Were the VMs using shared VHDX?  If so, shared VHDX on deduped drives is not supported and will cause the error you noted.  Stop dedup on the volume, then unoptimize the volume using the following PowerShell commands.

Disable-DedupVolume -Volume "VolumeName"

Start-DedupJob -Volume "VolumeName" -Type Unoptimization

• Edited by Greg_fileonellc Tuesday, March 10, 2015 9:43 PM

I had this problem which was caused by a failed Windows Server backup on the file server hosting the VHDX files. I had to cancel the backup process and then close the VHDX file on 'Open Files' in Computer Management for the file server.