New LUN Takes A long Time To Format and Errors Out

Question

Good afternoon,<o:p></o:p>
I have a Hyper-V Cluster composed of 4 nodes and these nodes are able to access multiple CSVs (14 in total). I recently requested a new LUN (LUN 15)to be provisioned
to my Hyper-V cluster in the size of 500GB. Here is my problem:<o:p></o:p>
1. Formatting of a 500GB LUN (with quick format selected) should not take more than a few seconds. Instead, the quick format takes about 2hrs if not longer. I have actually
seen it go for half the day.<o:p></o:p>
2. Once the formatting has completed (no errors), taking the formatted LUN offline freezes the Computer Management screen and shows the status (Not Responding). This
will take place for 30 minutes or less and show that the LUN has been taken offline.<o:p></o:p>
3. In the Failover Cluster Manager, detecting the disks takes about 15 minutes. Once the available LUNs have been detected I can add the 500GB LUN to the Disks screen
without any problems.<o:p></o:p>
4. While in the Disks screen, adding the LUN to the Clustered Shared Volumes takes about 5 minutes (too long).<o:p></o:p>
Already seeing that there is a problem, I went ahead and used the Hyper-V Manager to create a 200GB vhd on the new LUN which has been added to the CSV. The bar indicating
the progress of the vhd creation does not display any progress (no green progress bar appears, not even a tiny bit of it) and after 3 hours (more or less) I receive an error, stating that the creation of the vhd failed.
<o:p>NOTE: The vhd shows up in Volume 9 (LUN 15) but I can only bet that it will not work, plus I would not want to work with a vhd file which failed during the
creation process.</o:p>
<o:p>Long story short, I repeated the above steps to see if that was a temporary problem, but it is not. The same problem occurs no matter which Hyper-V cluster
node the operations are performed on. I would like to add, that I tested the creation of a vhd on an already configured LUN and the creation was completed successfully, and within a n expected time frame.</o:p>
NOTE: When LUN 15 errors out, it's status shows "Failed" in the Failover Cluster Manager. This in turn, causes the re-scanning of available disks to take forever (in Computer Management) and it keeps searching. Pretty
much, the fail of one LUN affects the entire functionality of the entire Hyper-V Cluster. 
Errors Listed In Event Details For LUN 15:
1. Cluster Shared Volume 'Volume9' ('Cluster Disk 5') is no longer accessible from this cluster node because of error 'ERROR_TIMEOUT(1460)'. Please troubleshoot this node's connectivity to the storage device and
network connectivity.
Event ID: 5142; Source: Microsoft-Windows Failover Clustering;Task Category: Cluster Shared Volume
2. Cluster Shared Volume 'Volume9' ('Cluster Disk 5') is no longer available on this node because of 'STATUS_IO_TIMEOUT(c00000b5)'. All I/O will temporarily be queued until a path to the volume is reestablished.
Event ID: 5120; Source: Microsoft-Windows Failover Clustering;Task Category: Cluster Shared Volume
3.Cluster resource 'Cluster Disk 5' of type 'Physical Disk' in clustered role '4530acc9-8552-4696-b6c3-636ff8d58c46' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover
Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet. 
Event ID: 1069; Source: Microsoft-Windows Failover Clustering;Task Category: Resource Control Manager
4.
Cluster resource 'Cluster Disk 5' (resource type 'Physical Disk', DLL 'clusres.dll') did not respond to a request in a timely fashion. Cluster health detection will attempt to automatically recover by terminating the Resource Hosting Subsystem (RHS)
process running this resource. This may affect other resources hosted in the same RHS process. The resources will then be restarted. 
The suspect resource 'Cluster Disk 5' will be marked to run in an isolated RHS process to avoid impacting multiple resources in the event that this resource failure occurs again. Please ensure services, applications, or underlying infrastructure
(such as storage or networking) associated with the suspect resource is functioning properly.
Event ID: 1230; Source: Microsoft-Windows FailoverClustering;Task Category: Resource Control Manager
Any and all help will be appreciated!

Answer 1

Hi AquilaXXIII,
What server edition you are using? If you are using 2012r2 as cluster node, please install Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
update first,
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
http://social.technet.microsoft.com/Forums/en-US/f9c1a5f7-4fcf-409a-8d7e-388b85512bfe/new-lun-takes-a-long-time-to-format-and-errors-out?forum=winserv
Before you install the new shared storage please first validation this storage first, you can refer the following KB to validation the new LUN.
Understanding Cluster Validation Tests: Storage
http://technet.microsoft.com/en-us/library/cc771259.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.