This should be now resolved. There was an underlying storage issue for the hypervisor. Of course after the issue was resolved the VM's filesystem already went into read-only mode so I had to reboot it, run a required a fsck, then another reboot. It should be all working normally now.

Aside from the data gap/loss, ping me off-list if you see any issues with the server still.