szklion.blogg.se

99 Drives Total – 1 boot drive – 5 Failed Drives = 93. I had a total of 5 x drives that were in a state of Lost Communication, so that left me with the following calculation. In your case, if you have other additional drives, you have to account for this. In my case, there was only 1 x drive for the boot drive, so the count was +1. NOTE: When you run the above command remember it adds the boot drive from the node you are running it on. I had a total of 7 x Nodes with 4 x Cache Drives and 10 x HDD Drives = 98 Drives Get-PhysicalDisk | Where-Object operationalstatus -eq ok | Measure-Object

When dealing with a lot of drives in a Storage Spaces Direct Cluster, I find it handy to get a count of the drives that are working and the drives that are broken. Get-StorageSubsystem clu* | Get-StorageHealthReport I also wanted to run a Storage Health Report Get-StorageFaultDomain -Type StorageScaleUnit | Where-Object | Disable-StorageMaintenanceModeĮverything seemed ok, and when I checked with Get-Physical Disk, the drives were still stuck in a “Lost Communication State.”īefore trying to Retire and Reset the disks, I wanted to check the status of the Virtual Disks I then tried to see if it was an issue with the disks being stuck in Storage Maintenance Mode which is a known bug right now if you have installed the June or later cumulative updated. I wanted to check what hotfix level that the customer was on which was July 2018. Get-StorageSubSystem clu* | Get-StorageHealthAction The next thing to check was the Storage Health Actions Here is the output that we had when we first looked at things à There are over 90 + disks in this cluster, so the output is a bit long. The reason for this is that Storage Spaces Direct had already removed them from the pool and they were showing up missing from Failover Cluster Manager and in a Lost Communication status when running

Interestingly enough the cluster itself was reporting healthy, and all the associated Virtual Disks and Volumes were also reporting healthy. Everything has been running great over the past six months until a few of his drives had started to report a “Lost Communication” Warning. Today I was working with a friend that is running a Seven Node Storage Spaces Direct cluster on Lenovo Hardware.