Hi guys,
I recently patched 2-nodes S2D failover cluster.
As it should be done I paused one of the nodes, evicted VMs and restarted the node.
When it was back online the job on the background started (which is what it should be.
However, it ended up with the virtual disk transited into "No Redundancy" operational status.

I run Get-PhysicalDisk and all physical disks were healthy.
The same I got in iDRAC Storage \ Physical Disks.
I tried to perform the steps described here https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/troubleshooting-storage-spaces
It didn't help.
The I came across this article http://kreelbits.blogspot.com/2018/04/s2d-recovering-detached-virtual-disk.html
Unfortunately, following it didn't give any results either.
Finally, I read this article http://kreelbits.blogspot.com/2018/05/the-case-against-2-node-s2d-solutions.html
I run Get-Physical | Get-StorageReliabilityCounter and got this.

Eventually I had to evacuate all VMs to another spare host, reset physical disks, replace those disks with ReadErrorsUncrorrected and rebuild S2D.
Now that it is the past I just have a question why S2D storage is susceptible to the errors marked as ReadErrorsUncorrected in Get-Physical | Get-StorageReliabilityCounter cmdlet output?