Search results

Hi all I'm having same issue on a Beelink U59 and Proxmox 7.4-17 This is the log Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). Oct 31 01:22:49 pve kernel: r8169 0000:03:00.0 enp3s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10). Oct 31...

@philx21 thanks! it seems that now those errors are not anymore in the syslog

Hi all I'm getting a lot of this error on a Beelink minipc U59 The minipc has one M.2 Sata disk and one SSD internally Oct 19 09:58:10 pve kernel: pcieport 0000:00:1c.6: AER: Multiple Corrected error received: 0000:00:1c.6 Oct 19 09:58:10 pve kernel: pcieport 0000:00:1c.6: PCIe Bus Error...

Thanks @Chris Disabling the storage, has let me remove the LXC/VM I needed to delete!! Strangely, the NFS permissions in OVM is RW as you can see here

Thanks @Chris How can I deactivate the storage? Just removing from Datacenter->Storage? What if I would like to fix the storage permission? I just briefly explain what is my need I have a minipc with an SSD to boot Proxmox and have lvm-thin and also an M.2 disk to have some more space...

Hi all I'm trying to remove a container and a VM that I don't need anymore, but I'm getting this error TASK ERROR: mkdir /mnt/pve/nfs-ovm/template: Permission denied at /usr/share/perl5/PVE/Storage/Plugin.pm line 1374. I've recently installed OVM in a container and followed this guide to have...

Where can I find info regarding hook scripts? What can I assume is that startup delays works only between VMs or LXCs, not between both. So if I have more than one VM, it respects the orders and delay, same in LXCs. Thanks

Hi all Is it possible to start a VM after starting a specific LXC that has also a startup delay? Actually I have set up the VM as start order 3 and a couple of container as start order 1 and 2 and a startup delay of 90 sec each But the VM start as soon as the first container start. Is there...

Sorry für die Google-Übersetzung ins Deutsche... Ich habe das gleiche Problem mit einem QNAP NAS. Wenn Sie einen neuen NAS-Benutzer definieren, wie stellen Sie sicher, dass dieser Benutzer beim Definieren der NFS-Verbindung in Proxmox verwendet wird? Danke

I've tried also to enable SQUASH (ROOT or ALL) on the NAS on the shared folder NFS configuration, but I get new error INFO: starting new backup job: vzdump 104 --compress zstd --remove 0 --storage NFS-QNAP-Proxmox-Backup --mode snapshot --node pve --notes-template '{{guestname}}' ERROR: Backup...

Thanks Fiona This should be done inside Proxmox or on the NAS (in my case) where is located the shared folder? I see that the command during backup is ERROR: Backup of VM 116 failed - command 'set -o pipefail && lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar cpf - --totals...

Hi all I'm having same issue while backuping unprivileged containers after doing the pct mount VMID, I can see that the owner is 100000:100000 root@pve:~# pct mount 104 mounted CT 104 in '/var/lib/lxc/104/rootfs' root@pve:~# ls -al /var/lib/lxc/104/rootfs/etc/ssh/ssh_host_dsa_key -rw------- 1...

Strange because the backup job include a vm and an lxc both on same destination and the vm works, the lxc does not Here is the full log vzdump 106 116 --compress zstd --mode stop --quiet 1 --storage NFS-QNAP-Proxmox-Backup --mailnotification failure --mailto woody4165@gmail.com...

Hi I'm trying to backup an unprivileged lxc and I get an error 116: 2023-06-24 04:49:04 INFO: Starting Backup of VM 116 (lxc) 116: 2023-06-24 04:49:04 INFO: status = running 116: 2023-06-24 04:49:04 INFO: backup mode: stop 116: 2023-06-24 04:49:04 INFO: ionice priority: 7 116: 2023-06-24...

I have a mount point to a NAS folder that was running a integrity check, so not available, and that was causing the error and that was causing the container not to start

Hi something strange is happening here. I haven't made any change to my HW (minipc) nor to my LXC configuration. I have latest Proxmox update (7.4-4) My Docker-Frigate container does not boot anymore and this is the error explicitly configured lxc.apparmor.profile overrides the following...

One more thing When I do a changes in the file /etc/pve/jobs.cfg I noticed that I have to reboot Proxmox to have it updated. Is there any other way?

Thanks Chris! Using backup mode STOP did the trick.

Hi Chris this is the LXC config arch: amd64 cores: 4 description: # Docker LXC%0A ### https://tteck.github.io/Proxmox/%0A <a href='https://ko-fi.com/D1D7EP4GF'><img src='https://img.shields.io/badge/%E2%98%95-Buy me a coffee-red' /></a>%0Amp1%3A...

Hi all I would like to exclude some paths from a LXC backup This is my jobs.cfg related to this LXC vzdump: backup-df0d2766-fe89 schedule 05:00 compress zstd enabled 0 exclude-path /media/frigate/recordings/ /media/frigate/clips/ /dev/mapper/ /dev/fuse/...