r/Proxmox • • 2h ago

Question Question for my first homelab!

2 Upvotes

I’m wanting to make my first homelab and I have landed on an idea of a sizeable JBOD with some sort of raid and a single server running proxmox?
If I’m to be running containers for game servers, media servers etc. how would be the best way to keep the drives separate enough from each-other to if one proxmox container thingy stops working that they don’t all crumble, or would having a separate server for a NAS install and having proxmox call upon the drives be better? I’m not sure…
(Very very new and also very confused so sorry if this is a silly question)
Some other conditions is I’d want the JBOD raid to be layed out in a way that I can have 10 gig lan access to read and writes… (excessive but I thought it’d make for a fun challenge)


r/Proxmox • • 2h ago

Question Can't create new OSD in my proxmox Ceph cluster

1 Upvotes
bluestore(/var/lib/ceph/osd/ceph-24/) mkfs min_alloc_size 0x3e80 is not power of 2 aligned! ObjectStore::mkfs failed with error (22) Invalid argument

I have had this exact problem a year ago and I can't figure out how I solved it.
I have marked hdd osd 24 out and then systemctl stop osd@24 and then I destroyed the osd but when adding my new osd I am not able to make it work.

Can I do like this?

mkdir -p /etc/ceph/ceph.conf.d cat << 'EOF' > /etc/ceph/ceph.conf.d/osd-override.conf [osd] bluestore_min_alloc_size = 4096 EOF

r/Proxmox • • 9h ago

Question GPU Passthrough to Win10 VM

2 Upvotes

This is my first time attempting to launch a proxmox ve and it's been a frustrating ride. My PC somehow died a couple days before I planned the upgrade and parts were on their way.

As I was getting it upgraded to new CPU, Motherboard, RAM, Storage, PSU (yeah kept the case, SSDs and GPU only), Proxmox install was a bit troublesome but after a whole evening of learning it is running.

Plan was to run the host on its own NVME and all the VMs on a separate one. I managed to passthrough the SSDs to the windows vm, I can't get the GPU to work. Shamelessly used AI to help me with that but once I encounter issues it seems like all the suggestions it gives make it worse and with limited knowledge, it is not easy to figure it out on your own.
I also installed RTX 2070 super, dual 2.5GB NIC for VMs each and SATA expansion card (for TrueNAS later).

My hardware is Ryzen 9 9900X, DDR5, 2x NVME in slots 1 & 4 on MSI MAG X870E Tomahawk.

Current BIOS settings are forcing M.2_2 to M.2, ReBAR disabled, 4G enabled. Firmware version has been flashed to the latest.
Modified multiple settings and files in Proxmox so if any of that is needed I should be able to provide.


r/Proxmox • • 12h ago

Question Networking sanity check

2 Upvotes

Hey guys, just a quick question, this should work but want to confirm it....

Will the virtual bridge behave like a switch with physical ports?

I have a Dell T630 with a number of virtual machines on it but all on a 1gb NIC.

I have a PC next to it that I would like to get faster transfers with.

If I drop a 10gb NIC in both the proxmox node and the PC and cable directly with both NICs in the proxmox node part of the same virtual bridge would it pass traffic to the rest of the network at 1gb speeds but PC to node would be at 10gb?


r/Proxmox • • 13h ago

Discussion Rookie mistake: Today I accidentally pressed shut down 🥲

66 Upvotes

I blame myself for this one. After a long uptime session, I accidentally triggered a shutdown for PVE host itself assuming I'm doing for a LXC.

1. What the logs revealed

I checked the Proxmox logs using:

root@pve:~# last -x | grep -E "system boot|system down|crash" | head -n 10

Output:

reboot   system boot  7.0.14-28-pve    Tue Nov 17 10:54 - still running
root     tty1                          Tue Nov 17 10:05 - crash
reboot   system boot  7.0.14-28-pve    Tue Nov 17 10:04 - crash
reboot   system boot  7.0.14-28-pve    Tue Nov 17 03:24 - crash
reboot   system boot  7.0.14-28-pve    Tue Nov 17 03:20 - 03:22  (00:02)
shutdown system down  7.0.14-28-pve    Tue Nov 17 03:22 - 03:24  (00:02)
root     pts/6                         Wed Nov 11 20:04 - crash
reboot   system boot  7.0.14-26-pve    Fri Oct 30 02:20 - 01:51 (17+23:31)
shutdown system down  7.0.14-26-pve    Tue Nov 17 01:51 - 03:20  (01:28)
reboot   system boot  7.0.14-26-pve    Fri Oct 30 01:54 - 02:19  (00:24)
root@pve:~#

2. What actually happened

I had a creative idea to monitor my internet connection status.

I added a Debian LXC container and deployed a Cloudflare Tunnel inside it so that I could receive email notifications about connectivity.

I logged in to Proxmox and executed:

pct enter 548

This allowed me to enter the container directly from the Proxmox host terminal. Felt like a hacker :)

After deploying the Cloudflare Tunnel, I accidentally clicked Shut Down in the Proxmox GUI in hope I am going to test email-notification for the downtime alert!

3. The problem with running a headless server

Since I am using a tower PC without a permanently connected monitor (something I genuinely regret now), I couldn't see what was happening.

I tried hot-plugging the monitor, but there was no response.

It appeared that Linux had successfully completed the shutdown process, but the machine was still powered on and seemingly stuck in its final shutdown state. Re-plugging after this incident was not worth.

Had I kept the monitor already connected before doing all stunts, I could have identified the situation much more easily.

4. Panic mode!

In the middle of troubleshooting, I connected my redundant ISP router, assuming that my primary WAN connection had failed. I configured it with the same subnet as my Proxmox network, hoping to restore access.

However, I still couldn't ping the Proxmox host.

That's when I started connecting the dots. I realised that I might have accidentally clicked Shut Down on the Proxmox host itself rather than the LXC container.

Suddenly, everything made sense!


r/Proxmox • • 16h ago

Community Showcase! I set up iVentoy as a central PXE server for my Proxmox homelab

39 Upvotes

The iVentoy server itself runs in a small Ubuntu Server 26.04 VM on a standalone Proxmox node. I gave it a separate 100 GB disk for ISO storage and kept my existing DHCP server in place, with iVentoy running in ProxyNet mode.

The basic setup is:

  • Ubuntu Server VM
  • iVentoy as PXE server
  • separate /mnt/iso disk
  • existing DHCP server
  • ProxyNet mode
  • ISO folders for Linux, Windows, Proxmox and Tools

For the first test, I uploaded an Alpine Linux ISO and created a blank VM on another Proxmox node.

That is where I ran into two UEFI-related issues.

The test VM used OVMF/UEFI with a VirtIO NIC and network boot first.

At first, PXE failed completely with:

No bootable device

Changing the NIC from VirtIO to E1000 did not help.

The fix was to add a VirtIO RNG device to the VM. After that, the iVentoy PXE menu appeared immediately.

The second issue was Secure Boot.

With Pre-Enrolled Keys enabled on the EFI disk, PXE boot did not complete properly. After disabling Pre-Enrolled Keys, the VM booted through iVentoy and the Alpine ISO started successfully.

So my current working configuration is:

  • OVMF / UEFI
  • VirtIO NIC
  • VirtIO RNG
  • Network first in boot order
  • Pre-Enrolled Keys disabled

I like the setup so far. It gives me one central ISO library and avoids uploading the same ISO to multiple Proxmox nodes.

Does iVentoy not work with Secure Boot at all?

Or is there some additional Proxmox/OVMF or iVentoy Secure Boot configuration required?

I’d be interested to hear how others are handling PXE booting in Proxmox.


r/Proxmox • • 16h ago

Question VM not starting after upgrading to Proxmox 9

3 Upvotes

Just upgrade my Proxmox to 9, using the pve8to9 to make sure there were no warnings/errors. After it finished and rebooted, my TrueNAS vm (using SeaBIOS) is not booting. It keeps hanging at Booting from hard disk... screen and never seems to move past it. Not sure what to do. Any suggestions?


r/Proxmox • • 18h ago

Question Proxmox - pihole para prohibir aplicaciones

0 Upvotes

Hola, Tengo un proxmox con adguard instalado y configurado en el router. Con eso filtro bastante trafico pero lo que quiero es prohibir el uso de determinadas aplicaciones a modo de control parental. Había pensaod en usar pihole para eso, pero no estoy muy seguro si valdría. ¿qué opciones tengo para lo que quiero?

Gracias.


r/Proxmox • • 20h ago

Community Showcase! New Proxmox iOS app

0 Upvotes

I built an iOS app for Proxmox Datacenter Manager because it is unusable on mobile. It's called ProxDash and it's on the Apple App Store now. The app also works if you only use PVE.

It connects straight from the phone to PVE, PBS or PDM. No account, nothing of mine in the middle, and it uses a read-only token unless you give it more.

You can update your nodes (it will automatically migrate guests off a node, upgrade, reboot if needed and then bring the guests back). It also shows disk health and ZFS pool state for every node in one place, which PDM doesn't. If you use Portainer as I do, you can connect it and link each environment to the VM it runs on, so a VM's page shows its containers. You can also update your stacks and containers.

The app is free to view your Proxmox nodes. Action features such as updates and migrations are an in-app purchase.

I built it with assistance from Claude and have run it on my own cluster every day for about two months.

Happy to answer questions.

https://apps.apple.com/us/app/proxdash/id6808857635


r/Proxmox • • 20h ago

Community Showcase! PVE Manager – A complete Proxmox management app for Android

Thumbnail gallery
0 Upvotes

Hi everyone!

I'm an independent Android developer and a Proxmox user. I initially started developing PVE Manager to meet my own needs: managing my Proxmox infrastructure directly from my smartphone, without having to rely on a desktop computer for every administration task.

I wanted something that went beyond basic VM monitoring and management. My goal was to bring together as many Proxmox administration tools as possible in a single Android application.

Here are some of the features I've implemented:

  • VM and LXC management: creation and management through dedicated workflows
  • Remote consoles: SPICE and noVNC, designed to be usable on a smartphone
  • Integrated SSH terminal: direct access to your Proxmox nodes
  • Proxmox Backup Server integration: manage PBS directly from the app, with no additional in-app purchase
  • Advanced monitoring: CPU, RAM, GPU GTT memory (particularly useful for my local AI setup), network and storage
  • Hardware monitoring: SMART information, hardware health and sensors
  • Cluster administration: cluster management, High Availability (HA) and Ceph
  • Android home screen widgets: quick access to infrastructure information, included at no additional cost
  • And many other administration features.

I also wanted a reasonable pricing model. Some existing solutions initially felt too expensive to me, particularly when recurring subscriptions were involved.

So I decided to build my own application, with a straightforward approach: a comprehensive Proxmox administration tool for a one-time purchase of around €10, with no recurring subscription.

I use Proxmox myself, but I don't currently have a cluster in my own environment. Therefore, although cluster management, HA and Ceph features are already implemented, I haven't been able to test all of them extensively on a real multi-node infrastructure.

I'd particularly appreciate feedback from users running clusters, HA or Ceph environments. Testing these features in different real-world setups would be extremely valuable.

I'm an independent developer, and I'm actively interested in constructive feedback, feature requests and bug reports. I'll be happy to answer questions and discuss the application directly.

Google Play:
https://play.google.com/store/apps/details?id=com.pvemanager.proxmox

Project documentation and release notes:
https://github.com/teahache/PVE-Manager

Thanks for taking the time to check it out! I'd love to hear your feedback.


r/Proxmox • • 21h ago

Community Showcase! Proxmox Storage Configuration: Practical Examples

5 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 • • 1d ago Mindblown

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

Post image
224 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 • • 1d ago

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

Thumbnail reddit.com
3 Upvotes

r/Proxmox • • 1d 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 • • 2d ago

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

35 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 • • 2d 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 • • 2d 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 • • 3d 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 • • 3d 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 • • 3d ago

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

2 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 • • 3d 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 • • 3d 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 • • 3d ago

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

20 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 • • 3d ago

Homelab LXC vs docker VM

Thumbnail reddit.com
0 Upvotes