Hey @ksl28,
instead of:
simply use:
This probably returns you your expected remotes, including a list of the nodes themselves and their types (pre, pbs). The output looks like:
Hope it helps! Afterwards, you can use this data as a...
hi,
this is currently expected behavior, but you can simply remove the token from the pve ui.
it's on our to-do list to remove the token as an opt-in mechanism, since the token may be used by other applications/clients too
Yo can try to use a tool like Clonezilla or Linux dd, if the disk has errors you can use ddrescue
https://clonezilla.org/downloads.php
https://www.gnu.org/software/ddrescue/ddrescue_es.html
You need to add only a cluster, and then all the nodes of the cluster appear. If you add each node of the cluster to PDM you may have duplicated (or x 3or x5 depending on the number of nodes) VM in PDM
Thank you very much for your replies. I can confirm that setting X2APIC, and IOAT DMA to enabled, solved the issue, now kernel 6.17.2-2 boots normally. I do NOT have Secure Boot enabled and SR-IOV is enabled.
My Apologies. I've set this exact config and now works fine
https://forum.proxmox.com/threads/dell-poweredge-r630-reboots-immediately-on-kernel-6-17-2-2-pve-pwr2262-cpu0704-uefi0078.177201/post-821716
Which version of Proxmox do you have at the destination? It will be a problem with the versión of Proxmox at the destination cluster, because live migration is only supported on latest PVE 8 versions
Have you any information on dmesg or journalctl?, it will be a hardware failure, due to ram (memtest is your friend) or even power supply failure not serving the necessary voltage/current to the equipment.
You may setup another PBS instance in a remote location and made a sync Job between the two pbs.
https://pbs.proxmox.com/docs/managing-remotes.html
After this You can setup another pbs storage for the remote pbs
You can try to use the NFS as a removable storage in PBS, if the PBS host dies, you can create a new one, and add the storage again as a removable existent media.
If you use this trick you can access again to your backups.
You can try to boot with a live debian image, and do a copy of the disks in the lvm volume to a external usb or via rsync to a new machine. To find the disks you can use:
pvesm list local-lvm
Then for example:
qemu-img convert -O qcow2...
Thanks, this helped me finding the issue:
Adding the following lines to `/usr/share/perl5/PVE/API2/Storage/Content.pm` to the create function:
use Data::Dumper;
use Sys::Syslog;
syslog('info', Dumper($param));
The call was...