S2D cluster issue

Question

Hello,
in our company we use Hyper-V Clusters with Storage Spaces Direct (S2D) and quite often we face an issue regarding virtual machines high availability. I'd present two cases in short for example.

1st one:
During the regular monthly Hyper-v cluster OS patching the last node of the cluster lost connection to all its disks after the node restart and based on that the whole storage pool was unavailable that caused virtual machines of the cluster to be offline. Node booted up without disks after update, all cluster shared volumes were unavailable, all virtual machines failed of course.

2nd case on other Hyper-V Cluster:
A disk of the storage pool (consisting of 96 disks in total ) failed, the whole storage pool stucked, all cluster shared volumes were unavailable again, all virtual machines failed.

Does anyone have experience with similar issues or with S2D in general?
We've already opened a MS case for this issue, it has been investigating for one month, but MS hasn't found anything suspicious yet so far.

In most cases the cluster survives similar HW errors and there are no blackouts. But still we have service outages quite often due to errors on S2D.
I understand that HW errors occur from time to time, like disk errors or other HW errors on the server causing the Host to be completely offline. But this is the reason why we use failover clustering, S2D and other technologies to ensure high availability.

Thank you