After a system crash I needed to restart a VM, call it ID x, after one of the other nodes in the DRBD9 cluster derped out. Now, node 1 derped out, and the VM was running on node 2, the issue being that restarting the VM on either node returns a KVM-error: Could not open '/dev/drbd/by-res/vm-x-disk-1/0': Permission denied. The output of 'drbdadm status' is also remarkable, for some reason vm-x-disk-1 is outdated on node 1 and 2 but 3 is set to 'StandAlone'. So why does it say that the data is outdated even though the VM was running on a node that was never offline? Does this mean the data got corrupted by the other node derping out or is it save to say that the data on node 2 is still the up to date data, and if so, how do I let DRBD know that it is (cause I'm assuming that would fix the issue)?