I want to restore a directory from a backup and all its containing subdirectories + all files.
So far I have tried:
find Victor\ Bart\ \-\ Retro\ Machines --select
restore-selected "/path/to/Victor Bart - Retro Machines" (path on original host where it was and is supposed to go again)...
for three days now, my PVE host has had some weird issues with backups.
Some containers take over 2 hours instead of only 17 minutes as normally while VM backups cause a backup output like:
INFO: trying to get global lock - waiting...
ERROR: can't acquire lock...
I honestly don't really know or remember how i got myself into this situation.
What i remember is: quite some time ago (early/mid 2020) I installed Ceph on my now only PVE node to take a look at it.
After some time I uninstalled it; most likely with apt as i wasn't aware of...
Ok i think i have broken the pool now as the proxmox boot tool continiously gives me this error, no matter what device path i choose:
invalid vdev specification
the following errors must be manually repaired:
/dev/disk/by-id/dm-name-35000cca050abc524-part3 is part of active pool 'rpool'...
About the system setup:
All 3 nodes are running on a DL380 Gen9, sda and sdb are unused SSDs.
The external storage is a multipathed iSCSI target on a HP MSA 2040 and contains all VM/CT data.
And lastly yes, the problematic node was setup with a ZFS RAID1 and one of the SSDs disappeared quite...
"stuck" or non-working node:
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with uefi
WARN: /dev/disk/by-uuid/D6CF-1F28 does not exist - clean '/etc/kernel/proxmox-boot-uuids'! - skipping
D6D0-5D81 is configured with: uefi (versions...
for some nefarious reason, one of my nodes (3 node cluster with external VM storage) will not boot into a newer kernel after kernel version 5.4.78. While booting up, the only options in the Proxmox-boot tool screen are kernel verison 5.4.78 and 5.4.73. An ls in /boot however...
Did anyone else find a solution?
i have the same issue but pvestatd gives me the following errors and no pfSense or anything similar is deployed:
pvestatd: lxc status update error: metrics send error 'proxmox': failed to send metrics: Connection refused
pvestatd: qemu status...
No, not really
I just used the API key for verification and did nothing else with any certificates. And I just assumed the validity of the PBS certs because I didn’t change them and they were renewed during the install (obviously)
The fingerprint was also only ever saved in the storage.conf...
Thanks for the fast reply!
i tried it and yes, that indeed fixes the problem.
However, I’m wondering why I now suddenly need the fingerprint in the script because this wasn’t necessary before the reinstall. Could you maybe explain that?
Thanks again for the solution!
the other day I had to reinstall my Proxmox backup server. The only thing I migrated from the old installation to the new one is the datastore.cfg file. VM and CT Backups work Fine, but this morning my scripts for backing up data in my ZFS storage pool threw an error that I...
Yesterday i replaced my motherboard to use a new CPU for my Proxmox Backup Server.
Therefore, the Network interface names changed and PCIe devices. No big deal, i made some changes to access the web interface.
However this morning i got an email from my PVE server that the...
I just tried that and am baffled.
For some reason, this seemed to have fixed this.
Do you have an idea why that is? It works with the same IPv6 configuration in Ubuntu and worked some time ago in Debian 10 as well, that’s why I’m so confused.