Recent content by JohnTanner

Hi, I'm facing the same issue out of the blue. My data backup runs every week and the pool is roughly 30Tb big, usual backup size is around 900Gb. Since this week, the backups for this particular job fails with: HTTP/2.0 connection failed catalog upload error - channel closed Error: pipelined...

Thank you very much for replying to such an old thread! To be honest, no, because I just rebuilt my server about a year ago. One of the reasons were some failed experiments like this one and a new setup where the boot pool is a zfs mirror instead of a singular device.

I'm having the same problem and I can't seem to find a solution for this. Any ideas? pveversion -v

I ended up solving this differently but the double asterisk thing is a valuable information, thank you for that

Hi there, 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)...

Hello everyone, 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...

No one any ideas?

Hello everyone, 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'...

No unfortunately I didn't follow that guide... But how do I find out which drive was the failed one? Because I do not remember which one "failed" :(

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...

Hello everyone, 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[30492]: lxc status update error: metrics send error 'proxmox': failed to send metrics: Connection refused pvestatd[30492]: qemu status...