xapi seems to broken after a Power Failure
-
@olivierlambert It also failed with the same error
[22:46 xcp-ng-ksu-secondary ~]# xe vdi-copy uuid=cb81808d-69c3-43a1-bc3e-c6c3b0f61a39 sr-uuid=7a50c3d0-cce3-f98f-5685-664b02ff542f
The VDI copy action has failed
<extra>: End_of_file -
So your VHD might be corrupted. You should use
vhd-utilto see what's going on on this VDI
-
@olivierlambert Hm My Local SR doesn't seems to be in that location I'm still trying to find it
-
@olivierlambert Are there supposed to be a mount point for it? I tried to use cat /proc/mounts but didn't find anything
-
@LunarstarPony There's mount point for my new remote storage and that's pretty much all
-
@olivierlambert Any Idea?
-
@LunarstarPony Apparently that's not the only VDI that can't be moved as well, some does move without any issue some seems no problem at all
-
What's the result of
vhd-utils? -
@olivierlambert same issue for me , after power outage xcp not booting . reinstalled xcp now , i can see the exisiting vm disks on storge . how can i restore the vms or import vm's from the disk file?
-
If it's only the XAPI that was damaged, you can restore metadata from your XO/Pool metadata backup. Alternatively, if you forgot to make metadata backup, you can introduce SR to find back all your previous disks (but you will lose the medata data with it).
