Search results

Hi athompson3117, I have done a similar setup for my secondary PBS, but I've used ISCSI as the target, which is presented to the PBS as a block device, just like a drive. That does improve the performance but in regular use I use the sync feature to pull the backups from the primary PBS.

Well I finally got the boltclt list -a to identify my devices after going through all my config and ensuring that nothing related was actually blacklisted from the attempts at iGPU passthrough. Now I can enroll my device OK, it shows enabled but no syspath domain. root@pve-5:~# boltctl enroll...

Reconnecting a PBS to a backup datastore, is not a simple process, it's not like connecting to an SMB/NFS share, believe me, I've done it, and even 1st time connecting to an external datastore is not a simple process because the PBS needs complete ownership of the store.! If you do go down that...

Have you checked for the latest USB4 update from ASUS.? (it appears to be separate from the BIOS firmware) I'm having a problem with a USB4 egpu dock, which I've worked on for weeks, and my system (Aoostar WTR MAX), uses the same USB4 controller, the ASM4242. ASUS recently released a firmware...

Hi exaveal, The question should not be, is it possible, but how would you recover should the host die when it is hosting both the PVS & PBS.??? I'm assuming that you are not backing up the full 12TB of Proxmox VM's/LXC's along with the media data? The backup of the media data should be a...

Sorry @Impact I was writing my reply as yours came in. I did try a second backup, but it was still crawling the entire 2TB of that folder, even if it didn't upload anything to the PBS. The Only way I could exclude it was to take the folder out of the root folder completely, and for that I...

Just a heads up on this backup issue. After a couple of days of digging into the fault, I found that I could exclude the offending folder (meilisearch) from the backup, but then the app wouldn't start after restore. So the dev made a change to scan for the folder on start-up and restore from a...

Thanks for the heads-up, I was not aware of that option. However, I stopped a quick test backup at 35 mins, assuming that the 'metadata' setting might shorten the time, it wouldn't be by much. Having identified the offending folder, I'm still struggling with excluding it from the backup task...

Gemini is mixing old and new passthrough data, and it will never work following any AI's advice. I have passed through the AMD 780m GPU to Windows 11 and it requires a meticulous process to function correctly. Passthrough requires the correct GPU rom file dump, (possibly for the audio device...

For anyone else following this, I think I've got to the root of the problem. The issue is application specific, in that the CT app generates a 2.TB sparse file found by running the following command run inside the container: ~# find / -xdev -type f -size +10G -exec ls -lh {} \; Results in...

I guess you know that USB connected drives can be temperamental in ANY server system, that's why they are not recommended. You might be better off setting up the USB drive as a networked share and then bind mounting the share into the LXC, that way the LXC doesn't have to deal with any dropouts...

Hi Chris, Thanks for your input, I used ncdu to check for the large sparse file but the only one I could find of anything like 2TB was the kcore file, which as 120TB & normal as far as I can tell. I did change this CT from unprivileged to privileged, so the error looks similar to the fault...

That is not true, not lately anyway. They are not as good as Intel or NVidia, but that doesn't mean that it won't work. The writer states that it's a mini PC, so unless it can support an external eGPU that won't help.

I'll try that, but this can't possibly be due to the mount points, the logs state that they are excluded, the 2TB size doesn't correspond to any of the mounted shares. Plus if I run a manual backup to an SMB share this error doesn't occur, it only occurs with the PBS backups (and I tried to 2...

Ah, thank you, I didn't notice that task history. Here is the relevant logs: INFO: Starting Backup of VM 405 (lxc) INFO: Backup started at 2025-12-31 02:44:53 INFO: status = running INFO: CT Name: tunarr INFO: including mount point rootfs ('/') in backup INFO: excluding bind mount point mp0...

You are welcome to try any of the multitude of LXC file servers, I just didn't have a good time with them myself (and got tired of working though the config only to find some part didn't work as I expected), especially with USB drives. In the Proxmox templates there is a Turnkey LXC File...

Sorry, I don't know where to get the logs from the pve, the node is a member of a cluster.

Hi Impact, Details as per request: The backup log is way too large so here is the start, and the end I have already posted: 2026-01-05T05:03:01+00:00: starting new backup reader datastore 'Backup': "/backup" 2026-01-05T05:03:01+00:00: protocol upgrade done 2026-01-05T05:03:01+00:00: GET...

This is s strange one for me and I hope someone can advise. Environment is updated to PVE9.1 & PBS 4.1 I have a CT with a 12GB root disk + 3x bind mounts on a Proxmox Host, on the same host I have another CT with 32GB root drive and 5x bind mounts (plus a couple of VM's) The 32GB CT backs up...

Maybe you should try the app again. I have it running in a CT, utilising 3% of 2 cores while monitoring an 80 device/services homelab. I think it's a great app and the only thing I don't like is that it spams the system logs of all the monitored Proxmox nodes.