Good morning,
Proxmox is working on a main server, replicated to a second one, with a quorum to know if the main is really down.
We have backup server in another place.
We had a blackout on last sunday.
Since then, my vm template (102.0), which has switch to the second server, is locked there.
First, I had message :
I've check on the forum and other help sites as I couldn't fixe the replication job error.
I've found this : "pvesr delete 102.0 --force"
Bad idead, I suppose.
I had then this issue :
I've tried a lot of things as zfs create data-zfs/vm-102-disk-0, or zfs snapshot data-zfs/vm-102-disk-0@__replicate_102-1_1746496819__...
Finally, I decided to restore a backup of the vm. As soon as the vm has been restored, the migration started nicely.
BUT
The vm has this :
-
When the others have, for exemple, this :
Do you know how can I totally fixe this please ?
Best regards
Proxmox is working on a main server, replicated to a second one, with a quorum to know if the main is really down.
We have backup server in another place.
We had a blackout on last sunday.
Since then, my vm template (102.0), which has switch to the second server, is locked there.
First, I had message :
Code:
task started by HA resource agent
2025-05-05 18:00:53 ERROR: migration aborted (duration 00:00:00): refusing to migrate replicated VM whose replication job is marked for removal
TASK ERROR: migration abortedI've check on the forum and other help sites as I couldn't fixe the replication job error.
I've found this : "pvesr delete 102.0 --force"
Bad idead, I suppose.
I had then this issue :
Code:
task started by HA resource agent
2025-05-05 18:13:34 starting migration of VM 102 to node 'node0-pve' (192.0.0.23)
2025-05-05 18:13:34 found local disk 'data-zfs:vm-102-disk-0' (attached)
2025-05-05 18:13:34 can't migrate local disk 'data-zfs:vm-102-disk-0': zfs error: cannot open 'data-zfs/vm-102-disk-0': dataset does not exist
2025-05-05 18:13:34 ERROR: Problem found while scanning volumes - can't migrate VM - check log
2025-05-05 18:13:34 aborting phase 1 - cleanup resources
2025-05-05 18:13:34 ERROR: migration aborted (duration 00:00:01): Problem found while scanning volumes - can't migrate VM - check log
TASK ERROR: migration abortedI've tried a lot of things as zfs create data-zfs/vm-102-disk-0, or zfs snapshot data-zfs/vm-102-disk-0@__replicate_102-1_1746496819__...
Finally, I decided to restore a backup of the vm. As soon as the vm has been restored, the migration started nicely.
BUT
The vm has this :
Code:
NAME PROPERTY VALUE SOURCE
data-zfs/vm-102-disk-0 mountpoint /data-zfs/vm-102-disk-0 default
data-zfs/vm-102-disk-1 mountpoint -When the others have, for exemple, this :
Code:
NAME PROPERTY VALUE SOURCE
data-zfs/vm-104-disk-0 mountpoint - -
data-zfs/vm-104-disk-0@__replicate_104-0_1746511219__ mountpoint - -
data-zfs/vm-104-disk-0@__replicate_104-1_1746511221__ mountpoint - -Do you know how can I totally fixe this please ?
Best regards