we have a windows 2008 r2 hyper-v in a cluster with 4 physical servers connected to an emc san storage. all the suddent the last couple weeks 1 node will not let us migrate and virtual servers to it. we also found we cannot browse the cluster volumes from the node thats having the issue. we get the following error

Cluster Shared Volume 'Volume2' ('Cluster Disk 2') 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.

node 1,3,4 can all connect to the shared volumes (there are 6)

node 2 cannot connect to 2 of the 6 v

Check Disk Management, are the volumes still listed as present? What connectivity are you using? Sounds like a physical connectivity issue to the LUNs or possibly a zoning\masking problem. Are you responsible for the storage? Can you confirm if the host is stating it is in redirected IO mode for the LUNS?

Check Disk Management, are the volumes still listed as present? What connectivity are you using? Sounds like a physical connectivity issue to the LUNs or possibly a zoning\masking problem. Are you responsible for the storage? Can you confirm if the host is stating it is in redirected IO mode for the LUNS?

• Proposed as answer by Steve TH - MSFTMicrosoft employee, Moderator 6 hours 8 minutes ago

Check Disk Management, are the volumes still listed as present? What connectivity are you using? Sounds like a physical connectivity issue to the LUNs or possibly a zoning\masking problem. Are you responsible for the storage? Can you confirm if the host is stating it is in redirected IO mode for the LUNS?

• Proposed as answer by Steve TH - MSFTMicrosoft employee, Moderator Monday, June 29, 2015 1:04 AM

Check Disk Management, are the volumes still listed as present? What connectivity are you using? Sounds like a physical connectivity issue to the LUNs or possibly a zoning\masking problem. Are you responsible for the storage? Can you confirm if the host is stating it is in redirected IO mode for the LUNS?

• Proposed as answer by Steve TH - MSFTMicrosoft employee, Moderator Monday, June 29, 2015 1:04 AM

Check Disk Management, are the volumes still listed as present? What connectivity are you using? Sounds like a physical connectivity issue to the LUNs or possibly a zoning\masking problem. Are you responsible for the storage? Can you confirm if the host is stating it is in redirected IO mode for the LUNS?

• Proposed as answer by Steve TH - MSFTMicrosoft employee, Moderator Monday, June 29, 2015 1:04 AM

Check Disk Management, are the volumes still listed as present? What connectivity are you using? Sounds like a physical connectivity issue to the LUNs or possibly a zoning\masking problem. Are you responsible for the storage? Can you confirm if the host is stating it is in redirected IO mode for the LUNS?

• Proposed as answer by Steve TH - MSFTMicrosoft employee, Moderator Monday, June 29, 2015 1:04 AM
• Marked as answer by Elton_JiMicrosoft contingent staff, Moderator 16 hours 10 minutes ago

Check Disk Management, are the volumes still listed as present? What connectivity are you using? Sounds like a physical connectivity issue to the LUNs or possibly a zoning\masking problem. Are you responsible for the storage? Can you confirm if the host is stating it is in redirected IO mode for the LUNS?

• Proposed as answer by Steve TH - MSFTMicrosoft employee, Moderator Monday, June 29, 2015 1:04 AM
• Marked as answer by Elton_JiMicrosoft contingent staff, Moderator Tuesday, July 07, 2015 3:03 PM

Check Disk Management, are the volumes still listed as present? What connectivity are you using? Sounds like a physical connectivity issue to the LUNs or possibly a zoning\masking problem. Are you responsible for the storage? Can you confirm if the host is stating it is in redirected IO mode for the LUNS?

• Proposed as answer by Steve TH - MSFTMicrosoft employee, Moderator Monday, June 29, 2015 1:04 AM
• Marked as answer by Elton_JiMicrosoft contingent staff, Moderator Tuesday, July 07, 2015 3:03 PM

Check Disk Management, are the volumes still listed as present? What connectivity are you using? Sounds like a physical connectivity issue to the LUNs or possibly a zoning\masking problem. Are you responsible for the storage? Can you confirm if the host is stating it is in redirected IO mode for the LUNS?

• Proposed as answer by Steve TH - MSFTMicrosoft employee, Moderator Monday, June 29, 2015 1:04 AM
• Marked as answer by Elton_JiMicrosoft contingent staff, Moderator Tuesday, July 07, 2015 3:03 PM

Check Disk Management, are the volumes still listed as present? What connectivity are you using? Sounds like a physical connectivity issue to the LUNs or possibly a zoning\masking problem. Are you responsible for the storage? Can you confirm if the host is stating it is in redirected IO mode for the LUNS?

• Proposed as answer by Steve TH - MSFTMicrosoft employee, Moderator Monday, June 29, 2015 1:04 AM
• Marked as answer by Elton_JiMicrosoft contingent staff, Moderator Tuesday, July 07, 2015 3:03 PM

If it is only Node 2 - it could also be a hardware issue - is this FC or iSCSI?

Hi Stonecold,

Is there any update

Best Regards,

Elton JI

yes, found the issue to be the secondary 4port  nic on one of the hyper-v nodes was corrupt. have to remove from devices and the drivers and reinstall clean and rebuilt the team