Our scenario is a 6 node cluster Windows Server 2016 DataCenter with full SSD S2D
We have already had some episodes in which a volume in a cluster pool goes offline, after what we suspect to be an internal maintenance procedure (which happens every day at arround 6:30 AM).
We have to remove the pool from the cluster, remove the volumes and then, from inside System Manager - > File Services (in one of the nodes), assign the virtual disk (marked as failed) and then select 'virtual disk repair'.
We have had to 'repeat' the repair for some times (maybe 6 or 7, it goes from 0% to 100% but stays 'failed') until it really gets fixed.
But today, we have done this for 'hundreds' of times with no result, untill some 3 hours. With our hopes already gone, .... bingo, healthy at last.
We don't know if it's the three hours, the hundreds of iterations or what, and have no way of knowing.
Has somebody had a similar experience, and/or knows what is really happening with the repair?
Thanks in advance for any advice!
Ismael