Hello, I hope someone here can help. I've been pulling my hair out for days now on this and it just gets more bizarre the more I find.
The naked problem is that 2 of 4 disks from my Storage Spaces array (striping with parity) on my Windows 10 machine, after 2 years of flawless operation, started hanging any disk operation in any program so long as they were connected. For example Disk Manager will not load until I disconnect them. Same with PowerShell, Storage Spaces, or even Explorer. The moment I disconnect them, though, everything loads fine. If I plug them back in, I get the same behavior. Queue my rising stress levels. This was working fine for a long time, now this?
Initially I thought it was the Sabrent 4 bay dock where I was keeping the 2 problem disks going bad. So I removed it from the equation (connecting all 4 disks via USB). But then when I added a new drive to the pool, it started doing the same thing, having no interaction with the dock. The other weird thing is these problem disks (now 3 of the 5 total) are the same brand and model, ADATA HV620s. Weirder yet, Get-PhysicalDisk returns an OK/Healthy operational/health status for all drives. And Get-StoragePool returns the same.
Fast forward to my first actionable finding from digging into the issue: I discovered that the three problematic disks all had the same UniqueID: 5000000000000001, indicating a signature collision. Which I found to be a simple enough fix changing the UID with the right guidance, but only for standalone drives. I'm concerned to do it to a disk that's part of a Storage Spaces array, for fear of creating bigger problems. What should I do here? I've seen quite a few people online having this problem with Storage Spaces and UniqueID in various configurations, most years ago, but no real answers that I've found.
Happy to share info. Can anyone help?