r/Proxmox • • 2m ago

Community Showcase! Proxmox Storage Configuration: Practical Examples

1 Upvotes

Small details in storage configuration can seriously impact system behavior. For example, a disk planned to be thin-provisioned may be fully allocated, a zvol may report excessive space usage, or an iSCSI mount may fail to remount after a reboot. These issues can disrupt backups and complicate recovery. 

We’re sharing the checks we found most useful for anyone setting up a new Proxmox host or reviewing an existing one, from homelab users to admins running production VMs.

Thin provisioning checks

1. LVM-Thin: run 'lvs -a | grep vm-<VMID>-disk-<NUM>' on the disks you've converted or migrated. If the Data% column is blank, then the disk is thick provisioned. The easiest fix is to migrate to thin-capable storage, and if it's already on thin-capable storage, then 'lvchange -ay' may be all that's required.

2. ZFS: the 'thin provision' checkbox is not in the creation window. You have to double-click on the new storage and then select it in the Edit: ZFS window.

3. zvol reservation: if ZFS get reservation <zvol> returns a non-zero value, then zfs set reservation=none <zvol> should free up the reserved space.

4. Discard: Turn it on for VM disks so the guest can issue TRIM. On ZFS, TRIM alone may not reduce USED, so it's worth comparing REFER to USED.

Other storage types

  • Directory: Partition, format, add to /etc/fstab, and leave preallocation at Default.

  • NFS and SMB: Add under Datacenter > Storage > Add. Proxmox mounts them under /mnt/pve/.

  • iSCSI: Partition and format the LUN first, mount by UUID with _netdev in /etc/fstab, then add the mount point as Directory storage.

  • ZFS: Zvols only support Raw, so use a Directory datastore on the pool for QCOW2.

Quick example

Create a VM with a 12GB QCOW2 disk on a directory or SMB datastore and install the guest OS. Then run du -h <disk>.qcow2. In our test, the disk used around 5.1GB of the 12GB provisioned, which is exactly what thin provisioning should be doing.

Pitfalls

  • dd fails with 'No such file or directory' on an LV: reactivate it with lvchange -ay.

  • If you're doing a disk copy with dd, then double-check that you have 'if' and 'of' the right way round. Getting them the wrong way round will overwrite the original disk.

Full workflow

Our blog has step-by-step examples for LVM-Thin, ZFS (zvols vs QCOW2 and the unexpected USED space), Directory, NFS, SMB and iSCSI from both the web interface and the CLI.

Read it here: https://www.nakivo.com/blog/proxmox-storage-configuration/ 

Which storage type do you rely on most for VM disks: LVM-Thin, ZFS, or file-based storage like NFS, SMB and iSCSI? 


r/Proxmox • • 12h ago

Community Showcase! My MCU-inspired homelab: ~140 Docker containers, 4 physical nodes, Proxmox, ZFS, and a virtual OpenWrt router

Post image
125 Upvotes

First post here! I've been lurking for a long time. Recently, I came across u/goblinmine's homelab diagram and knew I finally had to make one for my own setup. I forked their generator, adapted it to my infrastructure, and finally got it done! Everything is named after the MCU (Tesseract holds the space/containers, Bifrost is the bridge/router, Ultron is the gatekeeper, Agamotto handles time/backups, etc.). What started as a simple media server gradually snowballed into approximately 140 Docker containers across 10 Proxmox LXCs and four physical nodes, with a separate machine handling AI workloads.

Hardware

  • Tesseract (main server): AMD Ryzen 5 5600X, 32GB DDR4-3600, ASUS TUF B550M-Plus, Radeon RX 6600 XT, LSI 9300-8i SAS HBA, and a Realtek 2.5G NIC, all housed in a DAWG Y909 full tower (supports up to 17 HDDs). Runs Proxmox VE 9.1.

  • Tesseract's storage:

  • rpool: 2x 512GB NVMe in a ZFS mirror for Proxmox OS, LXC root disks, and /rpool/appdata.

  • tank: 2x 4TB Seagate IronWolf in a ZFS mirror for important personal data (Immich photos, ownCloud, Paperless PDFs, music).

  • scratch: 500GB WD Blue SATA SSD (single-disk ZFS) used as a sacrificial download staging area to prevent torrents from thrashing the main pools.

  • eternity: MergerFS + SnapRAID media pool combining 2x 4TB IronWolfs (iceman, phoenix), a 2TB Barracuda (spiderverse), and a 2TB Samsung 970 EVO Plus NVMe (jarvis), protected by a 4TB Barracuda parity drive (hangman).

  • Asgard (AI & Docker host): Mac Mini M4 with 32GB unified memory. Runs native Ollama for local LLMs alongside Open WebUI, Qdrant, AdGuard Home, Beszel Hub, Grafana + Loki, and a custom analytics stack.

  • Agamotto (backup server): Raspberry Pi 5 (8GB) in an Argon One M.2 case with a 1TB Samsung 980 PRO NVMe, running Proxmox Backup Server.

  • Watcher (external monitoring): Raspberry Pi 4 (4GB) running Uptime Kuma and a standalone NPM instance.

  • Network gear: BSNL FTTH (200/200 Mbps) with the ONT in bridge mode, feeding a TP-Link AX1500.

The PCIe and storage compromises

Fitting multiple NVMe drives, a GPU, and an HBA onto a micro-ATX B550 motherboard required some PCIe compromises. The RX 6600 XT operates at reduced PCIe bandwidth due to the motherboard's lane-sharing constraints. However, since it's primarily used for Jellyfin transcoding (Vision) and Immich ML (Edith), this hasn't been a significant bottleneck in my experience. The other interesting aspect is my MergerFS pool (eternity), which combines single-disk ZFS pools (iceman, phoenix) and ext4 drives (spiderverse, jarvis). It's a slightly unconventional arrangement. I have ZFS ARC hard-capped at 8GB to keep Proxmox from consuming too much of the available 32GB RAM.

Networking: Router-on-a-Stick

Instead of replacing my existing Wi-Fi router, I went with a virtual router-on-a-stick setup. Bifrost is a tiny OpenWrt VM (1 vCPU, 256MB RAM) on Proxmox that handles VLAN trunking, firewalling, and WireGuard. One of my primary design considerations was avoiding a situation where tinkering with Proxmox takes down the entire household internet. So, Asgard, Watcher, and Agamotto remain on the physical LAN, upstream of Bifrost. This means that if Tesseract or Bifrost goes down, essential services like Wi-Fi, DNS, external monitoring, and backups remain available. For internal segmentation, I've created five VLANs:

  • VLAN 10 – Management / Gatekeepers

  • VLAN 20 – Media

  • VLAN 30 – DevOps

  • VLAN 40 – Downloads

  • VLAN 50 – Sandbox

The physical LAN uses a static summary route to reach the internal VLANs, avoiding the need to configure individual routes on every client.

Services & Security

Instead of creating one LXC per application, I generally group applications into stacks, with one LXC per stack. Currently, that's 10 LXCs in total. Every host/container runs Beszel, Dozzle, and Portainer agents for monitoring, log visibility, and management. All externally accessible traffic passes through Ultron, which runs NPMplus with:

  • CrowdSec (bouncer + AppSec WAF)

  • Authentik SSO

  • IP allowlisting for services that should only be accessible through trusted networks or VPN Only a carefully selected subset of services is exposed to the public internet, such as Jellyfin, Immich, my portfolio Everything else is restricted to trusted networks and WireGuard VPN access. Downloads live in their own isolated VLAN on Quicksilver, running behind Gluetun + AirVPN with a kill switch.

Backups & Automation

Everything is automated using Semaphore UI (Ansible) on Friday, along with host-level cron scripts. Notifications are distributed through Gotify/iGotify via Apprise. My backup and maintenance workflow looks like this:

  • Nightly Proxmox backups of LXCs and /rpool/appdata to Agamotto (PBS).

  • Automated SnapRAID diff/sync, with safeguards to abort if deletions exceed a configured threshold.

  • Scheduled SnapRAID scrubbing.

  • Additional monthly backups of important personal data from tank to PBS. The idea is to keep backups, monitoring, and essential infrastructure as independent as possible from the main Proxmox host.

What's next?

There are plenty of things I'd still like to improve. The homelab is very much a continuous learning project. I'm particularly interested in improving automation, local AI integration, storage management, and infrastructure observability. Open to any questions, roasts, suggestions, or alternative approaches! (Note: The diagram was built using Goblinmine/homelab-diagram. I also used AI to help organize my notes and polish this write-up so I wouldn't miss anything.)

P.S. Reposting this today as the original was removed earlier as it was posted outside showcase day. Happy to answer any questions about the setup!


r/Proxmox • • 19h ago

Homelab Anyone with a Supermicro X10 motherboard running an intel arc gpu?

Thumbnail reddit.com
4 Upvotes

r/Proxmox • • 23h ago

Question Proxmox on steam deck

9 Upvotes

I’m looking to buy a PC to add a node to my Proxmox setup.

At the moment, prices in Italy are through the roof.

I’ve got a 256GB Steam Deck LCD lying around and I was thinking of using it for Proxmox instead of buying a new PC.

I haven’t found much information online.

Has anyone tried this?

It shouldn’t be too difficult (a Steam Deck should be just like a normal PC), but the lack of information online makes me think I might be missing something.


r/Proxmox • • 1d ago

Guide Proxmox Ceph LXCs and trim, storage usage went from 80% to 58%

34 Upvotes

My Ceph storage usage had hit 80% and I was debating between adding SSDs (expensive) or figuring out what to delete (time expensive and error prone).

I asked the AI (something on opencode, likely deepseek) where my space was used and to recommend where I could get space back. I figured I'd have to cut back on how long I was saving backups.

opencode/ai identified that trim was not on in my LXCs and I use all LXCs except for one (now two) VMs. I'm still on PVE 8.4.21.

Bottom line, I (AI) turned on trim (manually to start, then once a week) and my Ceph storage usage went from 80% to 58%.

That saved me about $1K USD if I had to add a single 2TB SSD to each of my three Ceph nodes.

Food for thought and YMMV.


r/Proxmox • • 1d ago

Question Is There a Lightweight Open Source GUI for Monitoring Sanoid/Syncoid ZFS Backups on Proxmox?

7 Upvotes

Hi,

I've been using Sanoid and Syncoid directly on my Proxmox host to manage ZFS snapshots and regularly replicate my datasets to a separate external hard drive. Everything is working great so far, but coming from TrueNAS, I have to admit I really miss having a simple web interface where I can quickly check that everything is running properly.

Ideally, I'd love something that gives me an at-a-glance overview of my datasets and child datasets, their replication status, when they were last successfully backed up, and whether anything has failed or needs attention.

I've been looking around for a lightweight, open source solution, but honestly, I haven't found anything particularly promising. I'm not interested in spinning up an entire TrueNAS VM just for a dashboard, as that seems like massive overkill for something that should be relatively simple.

Something lightweight that I could run in an LXC container would be ideal, although I'd also consider installing it directly on the Proxmox host if necessary.

I'm not necessarily looking to replace Sanoid or Syncoid since they're already doing their jobs perfectly. I just want a clean, reliable visual interface to monitor everything without constantly having to jump into the terminal.

Does anyone know of any actively maintained open source projects that offer something like this? I'd love to hear what others are using.

Thanks!


r/Proxmox • • 1d ago

Question Backup/restore question - Proxmox Backup Server and snapshots

Thumbnail reddit.com
2 Upvotes

**Update: Question resolved**

I'm having a problem with one of my VM's (original post linked for the curious) and I *DO* have backups available via the proxmox backup server but it's my first time actually recovering from a backup under proxmox so I'm hesitant and looking for confirmation/assurance on course of action here.

I'm familiar with ESXi at work where our process is usually taking a snapshot, restoring from a backup over a VM, doing what we need to do, and then either deleting the snapshot (restored system was good) or returning to the snapshot (restored system didn't help) and trying something else.

I took a snapshot with Proxmox and went to select 'restore' from one of the backup image dates and it flashed a warning saying all data would be deleted... so that's my question really: would doing a restore after taking a snapshot work WITH the snapshot, or would it actually wipe everything out (snapshot included) to restore from the PBS data?


r/Proxmox • • 2d ago

Question Stretched EVPN and global firewall policy

2 Upvotes

Hey all,

We’re evaluating Proxmox to replace vSphere and NSX, and I wondered if anyone is running EVPN across clusters and across sites?

We have high-speed, low-bandwidth fibre between the sites and currently run NSX in a Global Manager/Local Manager setup with stretched segments. We also use the GM for global distributed firewall policies.

From reading the PDM docs, it looks like you can create EVPN zones across multiple clusters as long as the VNIs are the same, so VMs see each other as L2 neighbours.

I don’t think the firewall policies can be created globally though, so I was thinking some Ansible work could help in that regard?


r/Proxmox • • 2d ago

Question Tuning Syncthing on Proxmox

1 Upvotes

I installed a SyncThing LXC from the scripts page. All went as expected, but I noticed that it looks like it is beating the bejesus out of the disk, even with no clients connected. On that host, the "I/O Pressure stall" metric raises and stays at 50%+ when the LXC is running. There are two other LXC's on that host, Vaultwarden and nginx. The disk involved is simple spinning rust /ext4. Shutdown SyncThing and I/O pressure drops to nothing.

Some Google work turned up some settings to change in SyncThing, and on the sync'd folder. No real improvement. There were also some "under the hood" changes to edit Proxmox parameters, but I tapped the brakes there.

I understand that I should expect some increase in disk i/o, but this seems kinda excessive. Am I looking at the wrong metrics, or just over thinking it?


r/Proxmox • • 2d ago

Question How to write files to ProxMox ZFS from an external drive?

1 Upvotes

Hey gang, any help appreciated.

Recently set up a Proxmox server to run jellyfin following this video.

Basically I set up an ubuntu container running jellyfin and pointed the media directory to an external HDD (We'll call it DRIVE-A) that is set up as a ZFS mediapool. Also installed samba to be able to access it from other computers. Everything working great it's just that transferring over LAN is slow, and would take months for the 4 TBs of media I have (on DRIVE-B).

So what's the best way to physically move media from DRIVE-B to DRIVE-A?

Tried to do it via Proxmox shell, by mounting DRIVE-B & using rsync but it was stalling from what I assume is how big the files are. Is it easier to passthrough both drives to a VM and just drag and drop the files there?

I don't know the best way to proceed and then would appreciate any guidance! Thanks!


r/Proxmox • • 2d ago

Question Proxmox and docker structure

12 Upvotes

I am new to the homelab scene and have a use case question on how it should be set up and it comes from an ignorance of how proxmox and docker should be used together. I am aiming to run a few use applications in either of the following ways.

Machine: HPz840 with dual E5-2630v3, 64 GB DDR4, 256GB SSD, 4x2TB HDD, Nvidia Quadro K2200

Applications: NAS, Jellyfin, Immich, Automatic Ripper Machine, Minecraft server, pihole

Either utilize: every application with it's own docker installation or creating one large docker vm that hosts all the applications.

My main concern is that I eventually want to access jellyfin through tailscale but one step at a time and I want to be able to have that separation as an additional layer of security.

I have considered just running through community scripts but I want to make sure I am setting things up correctly.

Any opinions/guidance is appreciated.


r/Proxmox • • 2d ago

Question Proxmox Installation error

0 Upvotes

im trying to make my frt homelab, i wanted to ue proxmox o i could try different VM and erver without needing to intall a new OS each time, but i getting a huge problem

im using ventoy

i enter in the proxmo iso in grub2 mode (cause normal mode just boots into the old ubuntu server install idk why)

then i try to run the graphical installer, but it just open a window saying: "error: invalid magic number" and "you need to load the kernel first"

i also tried intalling as TUI, Terminal and all the advanced ones, but i get the same error

tried to reset the bios to see if it was a bios bug but still the same results

can someone help me figure it out what happening and/or fi it?


r/Proxmox • • 2d ago

Homelab Proxmox win; VMware fail; with a little Nutanix and VirtualBox for good measure

19 Upvotes

I have obtained a few old HP DL 360p Gen 8 servers. 384GB RAM, 24 procs, but only 2 drives per chassis as they were used for VMware ESX 6.5 and the storage was on Netapp. I've been tasked to learn about Nutanix and they have a version called Nutanix CE geared towards trial / lab use.

If you want to skip the story and get to the question, it's in BOLD below...

Story: To start, I have ZERO hands on experience with Proxmox, though it was on my to-do list.

I was able to upgrade the server BIOS, iLO (OOBM), storage controller, etx. to the latest versions that HP has available.

A Bare Metal Nutanix CE install attempt failed, most likely due to drive speeds (USB and physical) and this required the P420i to be in HBA Passthrough mode.

I then tried installing Linux and the Linux version of VMWare Workstation. The install was successful, but the Nutanix Hypervisor saw no RAM or CPU so I couldn't actually run any VM's. (Actually tried Oracle VirtualBox as well!) Upgrade attempts made the install unusable.

Next decided to try Windows and two different versions of VMWare Workstation and had the same problems.

Then I tried ESXi 6.5 (as that's what these servers have been running for over 10 years); no go. Tried ESXi 6.7; no go. Tried ESXi 8; wouldn't even install.

Keep in mind that, with all of the VMWare installs, I searched far and wide and tried so many different tweaks to no avail. I was seriously thinking that the Ivy Bridge Xeon Processors or the BIOS of the server just wouldn't work for nested virtualization, even though all documentation stated that it would.

Having no Proxmox experience (but wanting to get some) I decided I'd give it a try. To say that it went smooth is really an understatement. I breezed through the standard install guide. Searched for how to add my other two disks as storage, how to emulate SSD on one of them, and lastly how to upload an ISO (the Nutanix CE install). After that, I spun up the Nutanix CE based on a blog post by the same guy that had guides for the bare metal and VMWare installs. (He's awesome and knows his stuff; pretty sure the guides didn't miss anything) It worked perfectly the first try! As a first test, I ran an install of Puppy Linux inside the Nutanix, which was inside the Proxmox and it just worked perfectly!

If you've made it this far, thanks for reading. I wanted to document for any other person that may be struggling as much / as long as I did.

Now for the question: What is it about these machines that VMWare seemingly couldn't deal with but Proxmox handled "out-of-the-box"?

Some notes:

  • In VMWare and Nutanix, I had to edit config files to expose UUID's for the drives.

  • In VMWare, I had to enable promiscuous mode on the nic's / virtual switch (and it worked; so I don't think that was an issue)

  • The same drives were used in all scenarios and set the same way in the server (except the one Bare Metal attempt) so I don't see how that could be a problem.

  • The BIOS Settings were checked and verified multiple times, but were actually never changed so I don't see how that could be a problem.

  • Processor and Memory shouldn't have been a problem. The guides all call for 32GB and 4 CPU's min. On all of them, I tied 64GB and 8 procs first, but then reinstalled with 32 and 4 before moving on.

  • Memory management / ballooning on VMware was a thought so I tweaked that every way I could figure and it made no difference.

  • I was getting a "LargePages" problem on ESXi 6.5 but not on 6.7 so I don't think that was a problem except maybe on the 6.5.

  • I noticed some "SMBIOS" errors on the VMWare installs (not sure which ones) that I don't recall seeing on the Proxmox install so I'm inclined to think that this may be where the problem is, but I'm not sure what I could do differently for VMWare AND Proxmox, evidently, doesn't have that problem.

I wanted to document this for others but if anyone has any ideas, let me know. I thought about cross posting to a VMWare group but I don't want to look like I'm beating them up; they've taken it on the chin for about 3 years now and I don't want to pile on. I also figure that my peers and other homelab users will have experience in many Hypervisors anyway so one post should be enough.


r/Proxmox • • 2d ago

Homelab LXC vs docker VM

Thumbnail reddit.com
0 Upvotes

r/Proxmox • • 3d ago

Question I dont understand windows and how ram works in Proxmox

Thumbnail reddit.com
0 Upvotes

I deploy a windows vm with 4 gb ram when I change through proxmox ui then windows doesnt detect that change


r/Proxmox • • 3d ago

Question Questions about how to set up local VPN/port forwarding between Proxmox computer and Opnsense router installed on separate hardware (repost)

3 Upvotes

I'm still very new to self-hosting so please forgive me if this question seems a bit green.

Also this is the second time I'm posting this question because the mods wanted me to add a network diagram, for some reason. They haven't been able to get back to me when I added the below image to the previous post so starting fresh seems like the only other option I got atm. Seems like a generally understandable problem without one, but again, green. Just ask if you need more details.

My current situation is that I have a Proxmox server connected to an Opnsense router installed on bare metal. I prefer the physical separation for security purposes and that the Opnsense router is expected to be used by guests, so virtualization is not ideal. They are connected through a separate smart switch that accepts VLAN IDs, although my ISP is connected to the Opnsense router directly.

I've been having issues when trying to use a separate VPN service on any of my computers interfering with my access to Proxmox until I switch the VPN off, and there is no method to greenlight the Proxmox IP address, and even if there was I'd rather use a solution that is moreso bound to the settings of the server/router hardware.

What I want to do is to set up some sort of local VPN or port forwarding method to always have access to my local server regardless of my connection to the outside internet being run through my VPN software. I've been reading a lot of different guides from both Proxmox/Opnsense documentation and through a lot of forum posts, but there doesn't seem to be a solution that makes sense or really works with my specific situation, that being having separate Proxmox and Opnsense computers.

What service or program would be both generally easy to understand and secure enough for a beginner to use in order to have continuous access to my Proxmox server? I've heard good things about Wireguard, but again I'm still fairly new and would want some advice on the best practices to using a local VPN or if that is even best practices for what I want to do. I intend to run things like Jellyfin or qBittorrent on Proxmox and access their GUIs via the browser, but I don't want to make things too open in case some bad actior tries to remote into my setup.

What do you think my best solution is for my circumstances? And what would be the steps I'd have to take to achieve it? I want to be able to learn or at least understand what I'd be doing so any helpful or informative resources will help in addition. Thank you all for your help in advance!


r/Proxmox • • 3d ago

Question windows vm failed to boot - stuck at grub

1 Upvotes

Howdy folks! I had a windows VM get stuck on reboot (probably automated patching overnight, not sure). I had to force the system to power off at the proxmox host command line, then when I booted it up it would just hang again. It wasn't until I fully rebooted the host that now the system gets past the grub countdown but then just drops to a grub> prompt.

I'm genuinely unsure what to do to fix it, I've used grub with linux before but not windows. Anybody able to point me at a resource or provide some commands, please?

UPDATE:

I used my Proxmox Backup Server to recover the VM to where it was on Nov 8, however in the process I learned that the PBS restore is destructive to the snapshot I took as a safety net in case the restore didn't work. So I'm glad that the restore *DID* work, but this behavior means that the only 'safety net' I can use when working with PBS backups is to force a new PBS backup as a point in time lock rather than a snapshot like I am familiar with in the ESXi world.

After the restore, I did all the windows updates and other things I was hoping might trigger the problem again, and... nothing. So I'm genuinely unsure what happened to start with but my vm is back in operation with only a couple days lost of world-save status on a low activity game server; in other words not a big deal to have 6 days go missing.


r/Proxmox • • 3d ago

Discussion Proxmox X Commvault Outage Caused by Race Condition

35 Upvotes

We had a major outage today in our Proxmox clusters caused by Commvault.

Documentation from Commvault on this: https://kb.commvault.com/article/?id=KA-191658

My org was hit by this. From the Proxmox team, this was the cause and fix:

On each host, we saw a ton of stale NDB devices:

nbd4                       43:128   0    30G  1 disk 
├─nbd4p1                   43:129   0     1G  1 part 
├─nbd4p2                   43:130   0     2G  1 part 
└─nbd4p3                   43:131   0  26.9G  1 part 
  └─ubuntu--vg-ubuntu--lv 252:4     0  26.9G  0 lvm  
nbd5                       43:160   0     0B  1 disk 
nbd6                       43:192   0     0B  1 disk 
nbd7                       43:224   0     0B  1 disk 
nbd8                       43:256   0     0B  1 disk 
nbd9                       43:288   0     0B  1 disk 
nbd10                      43:320   0     0B  1 disk 
nbd11                      43:352   0     0B  1 disk 
nbd12                      43:384   0     0B  1 disk 
nbd13                      43:416   0     0B  1 disk 
nbd14                      43:448   0     0B  1 disk 
nbd15                      43:480   0     0B  1 disk 
nbd16                      43:512   0     0B  1 disk 
nbd17                      43:544   0     0B  1 disk 
nbd18                      43:576   0     0B  1 disk 
nbd19                      43:608   0     0B  1 disk 
nbd20                      43:640   0     0B  1 disk 
nbd21                      43:672   0    80G  1 disk 
├─nbd21p1                  43:673   0  1007K  1 part 
├─nbd21p2                  43:674   0   512M  1 part 
└─nbd21p3                  43:675   0  79.5G  1 part 
  ├─pdm-swap              252:5     0     4G  0 lvm  
  └─pdm-root              252:6     0  65.6G  0 lvmnbd4                       43:128   0    30G  1 

After this happens, each VM impacted by this stops booting because its disks disappear.

The cause is as follows:

From what I discovered, this issue was caused by a race condition between proxmox and commvault for access to the /dev/nbd devices.  The solution I was able to find requires that we edit /etc/lvm/lvm.conf on each prox host and add the following exclusion so proxmox does not try to take control of the NBD devices during backups.

global_filter=["r|/dev/zd.*|","r|/dev/rbd.*|","r|/dev/nbd.*|"]

I may need to reinstall and configure the Commvault agent on the POC prox nodes to test this change.  I'd also like to confirm this with Proxmox Support if we are able to purchase a contract.

The immediate fix to clean up any stale NBD devices is to evacuate and reboot each proxmox node one at a time.

The fix we used was the following:

  1. Locate the VM and save evidence before stopping it

ID=189
PID=$(cat /var/run/qemu-server/$ID.pid)
mkdir -p /root/incident/$ID
ls -l /proc/$PID/fd | grep -E 'cv_staging|\.qcow2|\.raw' > /root/incident/$ID/open_files.txt
journalctl -t QEMU --since "3 days ago" | grep "QEMU\[$PID\]" > /root/incident/$ID/qemu_errors.txt
qm config $ID > /root/incident/$ID/config.txt
grep -c cv_staging /root/incident/$ID/open_files.txt     # staging files held by QEMU
grep cv_staging /root/incident/$ID/config.txt            # should be empty

Optionally, open qm monitor $ID and run info block -v. Copy any cv_staging or copy-before-write nodes into the evidence folder.

2. Take it out of HA (if HA-managed)

ha-manager status | grep "vm:$ID" && ha-manager set vm:$ID --state ignoredha-manager status | grep "vm:$ID" && ha-manager set vm:$ID --state ignored

3. Hard stop

qm stop $ID --skiplock --timeout 30
qm status $IDqm stop $ID --skiplock --timeout 30
qm status $ID

If it’s still running: kill -9 $PID, wait 5 seconds, confirm with ps -p $PID, then qm stop $ID — skiplock. If the process is stuck in D state, escalate.

4. Check the config and disks

check reports corruption, copy the files before doing anything else.

grep cv_staging /etc/pve/qemu-server/$ID.conf            # must be empty
for f in $(qm config $ID | grep -E '^(scsi|virtio|sata|ide|efidisk)[0-9]+:' | grep -v cdrom \
           | sed -E 's/^[^:]+: ([^,]+).*/\1/' | xargs -n1 pvesm path 2>/dev/null); do
  echo "== $f"; qemu-img check "$f"
done

If the config references cv_staging, stop and contact Commvault; don't start the VM. If qemu-img

5. Start, then confirm the new process is clean

qm start $ID
NEWPID=$(cat /var/run/qemu-server/$ID.pid)
ls -l /proc/$NEWPID/fd | grep -c cv_staging              # must be 0

Watch the console for fsck or an emergency shell.qm start $ID

6. Verify

  • Guest: root not read-only, no I/O errors in dmesg, systemctl — failed clean, the service works.

  • Host, after about 5 minutes: disk mtimes are recent, and journalctl -t QEMU — since -10min | grep “QEMU

  • $NEWPID

  • “ shows nothing.

7. Return it to HA

ha-manager set vm:$ID --state startedha-manager set vm:$ID --state started

r/Proxmox • • 3d ago

Question I’ve never used proxmox and I’m extremely curious

0 Upvotes

I’m new to all this like super green. In my fragmented learning stage I learned about hypervisors and used UTM on my Mac book where I ran a VM (ubuntu) that essentially powered my jellyfin home server. From there I learned the value in an always on device cause if the VM wasn’t running on my Mac jellyfin wouldn’t work so I got an old thinkcentre nothing crazy. Flashed Ubuntu on it and I downloaded docker. Now all my services sit in directories in their own “containers” (I’d assume) that I configured using docker compose yaml files. I use portainer if I need to start or stop a service but I mainly play around with it in the CLI just so I can get reps with it since I’ve never used it before this side venture. This is all context my actual question.

What purpose does proxmox serve? If it’s another UTM then it isn’t needed for my setup but every single person uses it everyone talks about proxmox every guide for anything uses proxmox but I’m currently getting the same (assumption remember I’m green here lol you guys are lowkey geniuses) experience so why doesn’t everyone cut out proxmox. There’s something I’m missing I know it.


r/Proxmox • • 4d ago

Question I would love some structural advise on my new Proxmox/TrueNAS setup

Thumbnail reddit.com
1 Upvotes

r/Proxmox • • 4d ago

Homelab another proxmox manager for mobile

0 Upvotes

edit2: clustara is free to download now

a bunch of you said you weren't paying 7 bucks for something you couldn't try so now you get 2 weeks with everything unlocked

android has it today. apple is still reviewing it so the iphone one is the old paid version for now, give it a day or two

while i was in there i added snapshots, backups and node restart/shutdown for proxmox

and one apology: the app used to hand you a pveum command to fix console access that could make that vm or node disappear from the app. that was my bug. it's fixed, and if you ran the old one just delete that permission in datacenter > permissions and add the role on / instead

also fixed metrics on qnap and the helper script menus dying in container consoles. thanks to the guy who emailed me logs for both

edit: looks like all the codes for android are gone, dm me if you need a code for next few hours while im awake

i didn't find any proxmox manager on mobile that i really liked using, so i made clustara. and yes, as a software engineer in 2026 i used ai to help me.

what it does:

  • nodes, vms and lxcs with live cpu, memory and disk. guests sit under the node they run on

  • start, shutdown, stop, restart, resume. anything that interrupts a guest asks first and names it

  • edit a guest's cpu, memory, disks and network

  • console for vms and lxcs plus a node shell, straight through the proxmox connection

  • it also does plain ssh hosts and docker. docker goes over ssh so there's nothing to install on the host, and if your docker host is a vm on the cluster it shows up under its node

  • a real terminal with esc/tab/ctrl/arrows, snippets and find

  • logs: journal, /var/log, docker and proxmox task logs, with search and live follow

  • one overview screen that just tells you what's broken: hosts down, stopped guests, failed backups

  • home screen widgets and optional background checks. the phone does the checking, nothing runs on your servers

  • api token or user/password with totp. it gives you the pveum commands for a read-only role if you don't trust it, which, fair

i haven't added added snapshots, backups, migration, creating or deleting guests, ceph, pbs yet.

you can check it at https://clustara.com

there is no backend server to track you. it's all on device, on your network or vpn/twingate/tailscale etc. no account yada yada

its on iphone, ipad and android.

anyways here are some free promo codes if anyone wants to check out my ai slop

iphone / ipad

33KPHJLWXJR9
7XYTTK6YH794
7MAJJPPM4AYY
4WRTMTWWRTW7
H4X74XT366JP
7LENPAJRKYTX
7HMLEKPTNN9F
3FPMXT4KHYLY
P69MLKJNEM3Y
JNJYHKYPHRX4
ML4YLNX6X4YT
R3T4NERYHR7T
NLYR3N63K6PA
7AEJHE6AFNAE
3A4L97WP3KFW
RYYYHAMWK6N3
RNN99W96R437
J7WX967JHHP7
T696ML3N9377
XTMFRTNNN393

android

JJVJ9G78785G57P33QUJ00F
4PCNMD3BBAN8PX7546ES7YD
PMR54S8G9D6Q53LBDVTW6Y6
CBBP8MLT4PGPPTJW5J1T1MW
ZHQXUJUB810UBLUAHMV01A7
9NFFG4G68KX5Z0SEG7127WH
2SVU76XQCQKC2M7BT8EXX7S
26VCEPSS5Y7ZDE9AR397F67
PGUZSRX5WAS71NN0M3FGREE
K2F9BD6JFC2B5T304NR68FQ
DEQXER0SCDAVD7CHJ9D2TWB
R8BUX2KNH00G3JGCVY13WBN
HCEHTCW2X91D1T7RU7DGQF7
ZTTGWP5BLY068Z3VQVEHLEJ
ZS7V7JX4QSANU7DW1Z3ZPGK
BGG9T7LNTB6BQ6P48XJD24A
AWSD2H08G0BT4X3A0ZE8D80
FX2QJ75NJ2YGP07ZP6TK1RW
L3NDG9VH8ZUGRNYF3R0E1HH
NQB4455F44JZ8V64QHS72PK

links app store: https://apps.apple.com/app/id6828100739 google play: https://play.google.com/store/apps/details?id=com.clustara.app


r/Proxmox • • 4d ago

Question The recurring question /enterprise

20 Upvotes

Hi there,

I know, I know—this question keeps coming back.

Has anyone in an enterprise environment moved from VMware to Proxmox?

We currently have a small lab with an old SAN running Proxmox. It's very nice and stable for what we've tested, though it is running on old hardware.

Now that Everpure has announced an official plugin, I'm wondering if I should start looking into migrating our production environment.

We are currently running an 8-host cluster with a total of 512 cores, 16TB of RAM, and a Pure Storage SAN.

Has anyone with a similar enterprise setup made the move?

I'm emphasizing "enterprise" here because these threads often get flooded by homelabbers. Sorry guys—I run Proxmox in my homelab too, and I love it, but it's a totally different ballgame than production enterprise scenarios


r/Proxmox • • 4d ago

Question Help me split this Dell MicroPC out for Proxmox?

0 Upvotes

MicroPC Specs

i5-6500T 16GB RAM 256GB SSD 1TB HDD

I want to run Home Assistant VM and maybe a Linux VM on it. Thoughts on how to break it up? Thanks in advance.


r/Proxmox • • 4d ago

Question i7-8700k to 5700g worth it?

2 Upvotes

hi, thinking of swapping my proxmox server to other gear.

currently:

Z370 mobo + Intel i7-8700k (6 core, 95w) + 1tb nvme + 96gb ddr4 (2* 16 + 2* 32 ) w/ intel 4 port NIC (using bridge, no pcie passthrough for mikrotik)

Planning on:

Ryzen 7 5700G (8 core, 65w) + A520M + same ram and SSD.

What I currently run:

Mikrotik router (doing PPPoE for my ISP @ 1gbps, so it somewhat does hit the cpu + misc mangle rules that I'm pretty sure also affect the CPU)

W10 VM for remoting into my network and misc stuff, occasionally run MC servers on here too

Docker VM or LXC (don't remember which) w/ portainer, proxy, and uptime kuma

Web server VM (ubuntu)

LXC for minecraft servers (modded 1.20+ 8gb a piece or more usually) but they're are more seasonable for the 2-week special.

I'm mostly interested in knowing if this upgrade will benefit me performance wise and power usage wise since the R7 has a lower TDP and I'm guessing not being an X series (or K series for intel) means it's more power efficient?

Haven't really had any performance issues though I'm also interested in reserving a core specifically for the mikrotik in case of a 100% CPU usage? And also looking into frigate to where I've been told the iGPU on intel might be better, but I haven't configured IGPU and the CPU usage isn't really eye catching either afaik.? 4 cams @ 720 / 900p and up to 15fps probably. Regular IP cams that are pretty old but work fine.

What do you guys think?

If it matters, I'm pretty sure the 2x16gb kit is 3000mhz and the 2x32gb is 3200 but I don't really care for expo/xmp on this and the z370 was bios modded to accept more than 64gb of ram since it was limiting itself, haven't had any issues.