Search results

apt remove linux-image-amd64 && apt upgrade From your link help me, thanks https://forum.proxmox.com/threads/pve-firmware-conflicts-firmware-linux-free.53806/

When i try to install last linux-image $ sudo apt install linux-image-amd64 Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: proxmox-kernel-helper Use 'sudo apt...

$ apt list --installed linux-image* Listing... Done linux-image-4.19.0-17-amd64/now 4.19.194-3 amd64 [installed,local] linux-image-4.19.0-25-amd64/now 4.19.289-2 amd64 [installed,local] linux-image-amd64/now 4.19+105+deb10u20 amd64 [installed,upgradable to: 5.10.191-1] $ apt list --installed...

$ sudo apt update Get:1 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB] Get:2 http://deb.debian.org/debian bullseye InRelease [116 kB] Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB] Hit:4...

I not have subscription, added # to `pve-enterprise`, same problem after apt update && apt dist-upgrade. I saw intresting, proxmox 6 use python2.7? When i run: apt -o Debug::pkgProblemResolver=yes remove python2.7 got strange list packages: The following packages will be REMOVED...

/etc/apt/sources.list deb http://mirror.hetzner.de/debian/packages bullseye main contrib non-free deb http://mirror.hetzner.de/debian/security bullseye-security main contrib non-free deb http://mirror.hetzner.de/debian/packages bullseye-updates main contrib non-free deb...

Hi, have problem with upgrade os. When i try to do apt dist-upgrade: W: (pve-apt-hook) !! WARNING !! W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'! W: (pve-apt-hook) W: (pve-apt-hook) If you really want to permanently remove 'proxmox-ve' from your system, run...

Hi! Cant restore VM from backups - tested on 2 proxmox servers, get same errors: restore vma archive: zstd -q -d -c /mnt/pve/linus-backup/dump/vzdump-qemu-1002-2022_12_02-06_02_08.vma.zst | vma extract -v -r /var/tmp/vzdumptmp32353.fifo - /var/tmp/vzdumptmp32353 CFG: size: 420 name...

After add ip to vmbr1 nothing changes. But if i add route in proxmox and no set ip to vmbr1 i can ping proxmox host and host can ping container. But no ping to 8.8.8.8. Maybe need add something to iptables? sudo ip route add 157.XXX.XXX.109/32 dev vmbr1

Container cant ping to 8.8.8.8. Config: arch: amd64 cores: 1 hostname: test-ip memory: 1024 net0: name=eth0,bridge=vmbr1,gw=157.XXX.XXX.65,hwaddr=00:50:56:00:81:86,ip=157.XXX.XXX.109/26,type=veth ostype: ubuntu rootfs: pve-twin:vm-108-disk-0,size=8G swap: 512 unprivileged: 1

Hi! I have 2 public ip on hetzner. One for host and one for container. I have vmbr0 where hosted vm behind NAT host ip. And i create vmbr1 for second public ip. But i not have ping from container to host and host cant ping container. How i can add ip to CT? In container configuration: ip...

New information. I recreate vlan from web interface, restart server. Config vlan: auto enp5s0.2000 iface enp5s0.2000 inet static address 10.2.0.1/8 mtu 1400 Interface worked, not have any error on restart networking service or ifup\ifdown, but not have ping in network to any...

Yes, server rebooted. $ pveversion -v proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve) pve-manager: 6.3-3 (running version: 6.3-3/eee5f901) pve-kernel-5.4: 6.3-3 pve-kernel-helper: 6.3-3 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-4.15: 5.4-19 pve-kernel-4.15.18-30-pve: 4.15.18-58...

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

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

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

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

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

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

After hour awaiting umount -f just worked.