HP 400 Mini G9 Storage Configuration, Best Practices?

madrian

New Member
Nov 3, 2025
1
0
1
Hi all,

Screenshot 2025-11-02 at 22.41.34.png

Today I picked up an HP 400 Mini G9 with an Intel i5-12500T and 32GB RAM for my homelab. I’m migrating from an HP MicroServer Gen8 (ESXi), and since I’m not too strong on hardware planning, I’d appreciate advice on the storage layout.

The machine has three built-in storage options:

  • M.2 2280
  • 2.5" SATA bay (SATA 600)
  • M.2 2230 (currently occupied by Wi-Fi module)
  • External USB-C USB 3.2 Gen 2x2
I'm considering removing the Wi-Fi card and replacing it with storage — but not sure if there's enough physical space for an adapter + SSD to reliably run as a data drive. Has anyone done this on the 400 G9?

For the main M.2 slot, I’m planning to use a 2TB Transcend TS2TMTE712A (~120€). Seller advertises it as industrial grade (4000 TBW), so seems decent for VM workloads.

My use case​

  • Server will only run VMs/containers
  • Separate NAS already exists for media/document storage
  • Just looking for the optimal layout for Proxmox + VM disks

Options I'm considering​

A:​

  • Install Proxmox on the 2.5" SATA SSD
  • Use the 2TB NVMe (M.2 2280) for VM storage
Since SATA is the slowest link, it feels logical to put the host OS there — but is this still considered good practice?
Would it be OK to store light backups / non-critical data on the same SATA disk alongside the PVE installation?

B:​

  • Install Proxmox on an external USB 3.2 Gen 2x2 drive (20 Gbps)
  • Create a ZFS pool using SATA + NVMe
Would ZFS performance be bottlenecked by the SATA disk in this case? And is USB booting stable enough long term for Proxmox?

Filesystem dilemma​

I know this one is debated everywhere

Given:

  • No power-loss-protected SSDs
  • 32GB RAM (not huge for ZFS + ARC)
  • Mostly VM storage, not a fileserver workload
Should I…
  • use EXT4 for Proxmox system disk?
  • and ZFS for the VM storage NVMe?
    Even if it will be a single-drive ZFS pool?
Or should I just stick to EXT4 everywhere and avoid ZFS overhead entirely?

Thanks!

Adrian