Search results

  1. A

    VLAN stop working after upgrade proxmox 5 to 6

    Hi, today i upgrade 2 servers with proxmox 5 to 6 version. After restart server vlan stop working, when i try ifup: sudo ifup enp5s0.4000 RTNETLINK answers: File exists ifup: failed to bring up enp5s0 ifup: could not bring up parent interface enp5s0 Enp5s0 interface working. My config: auto lo...
  2. A

    CT's on LVM disk get bad message error in turn

    After reboot server my issue is not gone (uptime before reboot - 45 days).
  3. A

    CT's on LVM disk get bad message error in turn

    looked in dmidecode - system use ECC. SMART not have any error on disk.
  4. A

    CT's on LVM disk get bad message error in turn

    Hi, i have phyzical hetzner server with proxmox 6.3. Мonth ago i got error https://forum.proxmox.com/threads/backup-lxc-bad-message.80474/ . fsck fix container disk, but the next day another container received an same error. I delete all containers and restore from backup. Everything is working...
  5. A

    [SOLVED] backup lxc: Bad message

    Problem solved, fsck /dev/vg0/vm-101-disk-0 found ~50 inodes error, backup start working after fix with fsck
  6. A

    [SOLVED] backup lxc: Bad message

    Hi! I have 4 LXC on my server, one of them has an error on many files in container while backup, for example: INFO: tar: ./home/user/.vscode-server/bin/485c41f9460bdb831c4da12c132daff275515b51/extensions/ms-vscode.js-debug/src/bootloader.bundle.js: Cannot stat: Bad message Trying run pct fsck...
  7. A

    pct fstrim - can't umount lvm disk

    After hour awaiting umount -f just worked.
  8. A

    pct fstrim - can't umount lvm disk

    Hi! Today i run command pct fstrim 100 on disable lxc container and my ssh connection was disconnected. After reconnect i try fstrim and get error: mount: /var/lib/lxc/100/rootfs: /dev/mapper/vg0-vm--100--disk--0 already mounted on /var/lib/lxc/100/rootfs. Ok, trying umount: # umount -f...
  9. A

    [SOLVED] Backup of VM 100 failed - unable to parse volume ID

    Found this thread https://forum.proxmox.com/threads/unable-to-parse-directory-volume-name-with-pct-create.55373/ apt install pve-container=3.2-2 helped me
  10. A

    [SOLVED] Backup of VM 100 failed - unable to parse volume ID

    Hi! After update from Proxmox 5.4 to 6.2 have problems with backup all LXC containers. All containers use mount points and the error points to them. What a problem with mount point and how i can fix it? pveversion pve-manager/6.2-15/48bd51b6 (running kernel: 5.4.73-1-pve) INFO: create storage...