Search results

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.

I'm sorry, my comment is not meant to offend, but I think you have spent way too much time chasing specs. You are supposed to decide what it is that you want from the Proxmox environment and then spec the system around your requirements. You seem to have taken the opposite approach, gathering...

You might try upgrading the Intel CPU micro code in Proxmox in case the they are running an older or different versions. This might help: https://community-scripts.github.io/ProxmoxVE/scripts?id=microcode&category=Proxmox+&+Virtualization

I've had the unit since early Sept, it's fully loaded with 11 drives and using the 10Gbe networking. Running Windows 11 VM and a TrueNAS server. The only times it's been down is when I'm messing around with the configuration, but even that downtime is becoming less because the TrueNAS has...

I can't say that as I have no experience with those controllers and no idea what devices you have connected on each. I would try to disable the Rombar one device at a time. Then look into firmware updates, rolling back the kernel to the earlier version and if it still fails do further...

I can say that the WTR MAX is almost the perfect Proxmox node, lots of power in every aspect needed in a Proxmox node. I wish I could afford a 3 unit cluster. And Aoostar, although being relatively new to international sales, are fairly good at working out any issues. For example, for the...

I'll second that. It would be great to have a list of the relevant changes (for passthrough etc.) in case of rebuild after host hardware failure. Every one of my Proxmox nodes have different changes made over time, and they are not really documented anywhere.

What SATA controller / HBA are you using.? I had to disable the Rombar (and upgrade the firmware) for the my controller to boot TrueNAS after upgrade from kernel 6.8.14

One of the best / easiest options at the moment is the setup of a Tailscale network, you can run a tailscale node in an LXC and access you entire LAN for anywhere. No requirement to open holes in the firewall https://tailscale.com/

OMV is a file server application. with some extra's bolted on. It does have the advanced power management for spinning down the drives, but as I say, I never use them.

Ah, sorry, I completely misunderstood the thread, I have a similar setup for none important data storage (even USB drives), OMV is still the best option I found after testing multiple LXC files servers.

In a VM the NVMe the drive shows as a PCI device (not a drive), once you find the correct PCI device (use the command lspci to list them) and then passthrough that device.

I wouldn't worry about that too much, if the drive is shared (and other family members need access) then you want it to be always available. I know there is a way to tell OMV to spin down the drives, but I never use it myself. More important than the longevity of the drive (that can always be...