@vaewyn There is an emergency transition to new master xe command. Also, make sure all your hosts are properly time syncronized to each other or there can be pool issues.
Try first:
xe pool-designate-new-master host-uuid=<new-master-uuid>
If that fails, you will need to run on the slave server:
xe pool-emergency-transition-to-master
Ambassadors
People talking about XCP-ng/XO around them
Posts
-
RE: Can't designate new master on XO source pool
-
RE: Unable to update XOA
@fred974 Hi !
Do you see anything red in XOA check ? (XOA > Support) ?
-
RE: Booting to Dracut (I trusted ChatGPT)
(BTW you don't have any backup from XOA ? If you have backup, you can just register a new XOA, connect to you remote and restore everything, it will be much simpler)
-
RE: Booting to Dracut (I trusted ChatGPT)
If I was in your place, I would do:
- Disconnect all USB used as SR
- Reinstall XCP-ng
- if you have only a few VMs, my option would be just to redeploy XOA, REATTACH the SR (not create, REATTACH, be careful, a create will wipe your disk)
- Recreate VMs, attach the VDI, boot from here
- if you have to many VM, directly after deploying XOA restore your metadata backup, it should be repluging the SR and create PDB at least (but it's been a while since I didn't use the metadata)
In any case, backup everything, especially the VDI (.vhd). If you have the VDI, you can work around with the rest
-
RE: Booting to Dracut (I trusted ChatGPT)
@nuentes You can reinstall without wiping the SR. Just plug the ISO, it will ask you if you want a clean install or a reinstall
