Recent content by ahoi_

  1. A

    Single-file restore and LVM

    Having this problem, too. Maybe @t.lamprecht got an idea?
  2. A

    unable to parse worker status

    Alright. For me it was important to check, whether this null byte has been written recently. As I interpret it, it was written right at the beginning and I can remember that the engineer who set up the PBS server mentioned that there was something wrong on the deployment image they used (some...
  3. A

    unable to parse worker status

    Hi Dominik, seems like it has never been rotated: find /var/log/proxmox-backup/ | grep archive /var/log/proxmox-backup/tasks/archive stat /var/log/proxmox-backup/tasks/archive Datei: /var/log/proxmox-backup/tasks/archive Größe: 173157 Blöcke: 344 EA Block: 4096 reguläre...
  4. A

    unable to parse worker status

    Hi, the hardware or the process did never crash, but I updated to PBS 2 yesterday. If I understand that file correctly, it's some kind of archive of all tasks? So the second line would represent something on the very beginning of my PBS-usage?
  5. A

    unable to parse worker status

    Sure. Unfortunately the output is too large for a post, so I attached a text-file.
  6. A

    unable to parse worker status

    Hi Dominik, # proxmox-backup-manager versions --verbose proxmox-backup 2.0-1 running kernel: 5.11.22-1-pve proxmox-backup-server 2.0.4-1 running version: 2.0.4 pve-kernel-helper 7.0-4 pve-kernel-5.11...
  7. A

    Wrong Kernel after upgrade

    Thank you for your support, Thomas. Is there anything I should have an eye on for the next few days or the next update (PBS 3)?
  8. A

    Wrong Kernel after upgrade

    That's very strange. PBS has been installed by engineers in the datacenter and I know they are using some kind of installation image. I am not sure, whether this installation image is something custom-built. For now I succeeded using apt install proxmox-backup and the correct kernel is being...
  9. A

    Wrong Kernel after upgrade

    Hi Thomas, sure. Here we go: # proxmox-backup-manager versions --verbose proxmox-backup unknown running kernel: 5.10.0-7-amd64 proxmox-backup-server 2.0.4-1 running version: 2.0.4 ifupdown2 3.0.0-1+pve5...
  10. A

    unable to parse worker status

    Hello, checking the status of PBS 2 I am getting those errors: root@pb1:/ # systemctl status proxmox-backup-proxy.service proxmox-backup.service ● proxmox-backup-proxy.service - Proxmox Backup API Proxy Server Loaded: loaded (/lib/systemd/system/proxmox-backup-proxy.service; enabled...
  11. A

    Wrong Kernel after upgrade

    Hello everybody, after upgrading to PBS 2 I mentioned that I am using the kernel Linux 5.10.0-7-amd64 #1 SMP Debian 5.10.40-1 (2021-05-28) Proxmox Backup Server should come with it's own Kernel 5.11.x. deb http://ftp.debian.org/debian bullseye main contrib deb http://ftp.debian.org/debian...
  12. A

    Proxmox Backup Server 2.0 released!

    I got the same problem. These is /etc/apt/sources.list deb http://ftp.debian.org/debian bullseye main contrib deb http://ftp.debian.org/debian bullseye-updates main contrib # security updates deb http://security.debian.org/debian-security bullseye-security main contrib ## Dotdeb Packages...
  13. A

    PBS2: proxmox-file-restore failed: Error: mounting 'drive-virtio0.img.fidx/part/["5"]' failed: all mounts failed or no supported file system (500)

    pveversion -v proxmox-ve: 6.4-1 (running kernel: 5.4.124-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.4: 6.4-4 pve-kernel-helper: 6.4-4 pve-kernel-5.4.124-1-pve: 5.4.124-1 pve-kernel-5.4.119-1-pve: 5.4.119-1 ceph-fuse: 14.2.20-pve1 corosync: 3.1.2-pve1 criu: 3.11-3...
  14. A

    PBS2: proxmox-file-restore failed: Error: mounting 'drive-virtio0.img.fidx/part/["5"]' failed: all mounts failed or no supported file system (500)

    Hi @dcsapak But in this case partition 5 should be mountable? fdisk -l Festplatte /dev/vda: 32 GiB, 34359738368 Bytes, 67108864 Sektoren Einheiten: Sektoren von 1 * 512 = 512 Bytes Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes...
  15. A

    PBS2: proxmox-file-restore failed: Error: mounting 'drive-virtio0.img.fidx/part/["5"]' failed: all mounts failed or no supported file system (500)

    Hello, I updated PBS to PBS2 - the update went fine and I was able to create a new backup of a machine that has these mount points: $ df -h Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf udev 982M 0 982M 0% /dev tmpfs 200M 22M...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!