About this tag
The tag 'lost communication' on WindowsForum.com covers issues where storage disks in Hyper-V or clustered environments, such as ThinkAgile nodes, enter a 'lost communication' state. Discussions focus on troubleshooting steps using PowerShell commands like Get-PhysicalDisk and Set-PhysicalDisk to identify and retire affected disks, remove them from Storage Pools, and reset unrecognized drives. Common solutions involve setting the disk status to Retired and using Remove-PhysicalDisk to clear the error. The tag is relevant for IT professionals managing Storage Spaces Direct (S2D) or Hyper-V clusters dealing with disk communication failures.
-
G
disk on hyper v in "romeving and retired" state
Hello, after adding disks to a clustered ThinkAgile node, we have the disks in a "lost communication" state. We tried several solutions without success below are the steps we tried First, create an array of the disks that are failing or failed. $disk = get-physicaldisk | where-object...- gatta
- Thread
- clustered node disk disk management failed disks hyper-v lost communication operational powershell storage pool troubleshooting
- Replies: 5
- Forum: Virtualization