I had a similar situation about three weeks ago, but it wasn't erroring on the same storage group. According to the documentation that I saw, the only fix was to dismount the database and re-mount it. I ended up just rebooting the active node and that cleared up the problem. I have two questions:
Is this the only way to correct this issue?
Why is it happening?
Any assistance with this issue would be appreciated.