Recent content by alc

After some testing, I think that my particular issue where the snapshot will not update and keep using some old "ghost-snapshot" only occurs when the exact same name is used. Comments seem to have no influence. Here is how this was tested (actions here start after the actions described in the...

I've had the same issue and removing the wrong 'parent' line indeed solves the GUI issue. But the next snapshot I've made didn't work. I did the snapshot and immediately Rolled back for testing, and it did NOT rollback to the last snapshot but to the one that was deleted last before the bug...

Two more details : I think that all VM's that don't backup are Clones of a single W10 VM. The original does backup fine. There are the two aformentioned active VM's that don't backup, but 3 others that are not in production (and thus not in scheduled backups) won't backup either, if I launch a...

Yes there are ACL's but there is also another VM on the same host, with the same 'local drive' config. and the same backup settings that backs up every night without issues to the same NFS storage. But again, doesn't the original error log point to the Firewall one way or another ? Because that...

Also note that disabling or deleting all Firewall rules didn't change anything. And here is a pastebin link to the Backup log, just in case : https://pastebin.com/ACzChayV

Anything you need. Here is some information : - TrueNAS is CORE version 12.0-U8.1 - NFS share has 'MapAll User : root' and only allows access to PVE IP's. Other options are default. - Storage (aka 'pool') options are as follows (on that particular pool being shared to PVE) :

Ok thanks, I've tested most options mentioned in the "DATA AND METADATA..." section of 'man 5 nfs' (in the Proxmox VE server), without success. My procedure was the following : - Edit storage.cfg, adding an 'options <option>' line to the desired storage entry - Unmount the target storage with...

Hi fabian, The target storage is indeed on a TrueNAS, but exposed via NFS. I've added the option in /etc/pve/storage.cfg anyways but I'm guessing the option may not apply to NFS. Re-running a backup manually for one of these VM's failed with the same error after the edit (but note that I didn't...

Since creating two W10 VM's, they couldn't backup for days with the same error : (Example VM '106') : 106 W10x32-G01 FAILED 00:00:00 unable to open file '/mnt/pve/nasa-backup2/dump/vzdump-qemu-106-2022_11_21-02_10_37.tmp/qemu-server.fw.tmp.3577369' - Operation not permitted Couldn't find...

Hey, this is just an exploratory thread, I'm trying to get a hint of what is happening. Quick explanation of the situation : Many of my VM's use a TrueNAS server over NFS (v3) to store their service's data (nextcloud, moodle, e-mails...). I am troubleshooting slow response times for a service...

No luck either. I still get 4 alert messages from my TrueNAS everynight because my AD (VM) disconnects during every daily backup, which did not happen before version 7 of proxmox.

Likewise : after re-installing qemu-agent exactly the same thing happened last night

I'll check this and will update after tonight's backups

I have a very similar issue, which I discovered because the repeated Message from syslogd@dc1 at Dec 3 05:28:11 ... kernel:[992745.113396] watchdog: BUG: soft lockup - CPU#1 stuck for 30s! [kworker/1:1:29984] errors on my Domain Controller caused disconnections on some clients, that caused...

I just pulled the sata cable from 'sda' on a fresh ZFS RAID1 testing box, and it doesn't seem to send out any message, although 'zpool status' gives DEGRADED. But the box still runs smoothly, hooray for the RAID/ZFS :D EDIT : After re-connecting the HDD and re-adding it to the pool ('zpool...