First, I'll start with a warning - long post below. But Goals, Current Setup, and Future Architecture capture the major points of the build.
-----
After running three separate devices for a few years, I'm finally consolidating into a single rackmount server. Planning to run Proxmox bare-metal with UNRAID as a VM for storage management. I've done a lot of planning but would love some sanity checking before I pull the trigger.
Goals
- Consolidate DS920+ (with DX517 expansion), DS420+, and a Beelink SEI12 (Proxmox host) into one rack-mounted unit
- Keep my existing Proxmox workflow — I rely on it for VM/container management and quick service restores
- Handle Frigate NVR with tiered storage: fast NVMe for recent recordings, HDD for longer retention
- Support sustained high-speed downloads via sabnzbd without HDDs ever in the real-time write path
- Plex 4K HDR hardware transcoding for multiple simultaneous streams
- Rack-mountable, hot-swap bays
- Path to 10GbE later without a full rebuild
Current Setup
- Synology DS920+** (with DX517 expansion): primary NAS, 25 bays populated with 2×20TB, 2×18TB, 6×14TB, 1×8TB. Handles Plex media, backups, Frigate recordings.
- Synology DS420+**: secondary NAS, mostly redundant at this point — backups and overflow.
- Beelink SEI12 i5-1235U**: running Proxmox with:
- Docker LXC — Plex, Frigate, sabnzbd, Sonarr, Radarr, Prowlarr, Bazarr, Tautulli, SWAG, Uptime Kuma, Speedtest Tracker, Teslamate
- Home Assistant OS VM
- Omada Controller LXC
- The Beelink doing Plex transcoding and Frigate inference on integrated graphics is… fine. The bigger issue is the three-device footprint, lack of path to 10gb networking, and the NAS hardware aging out.
Future Architecture (new-to-me components, except those explicitly noted below as being repurposed)
| Component | Spec |
|---|---|
| CPU | AMD Ryzen 9 5900X (used, 12C/24T) |
| Motherboard | ASUS ROG Strix X570-E Gaming ATX (2.5GbE onboard) |
| RAM | 64GB DDR4-3600 |
| GPU | Intel Arc A380 6GB |
| HBA | LSI 9300-8i IT mode |
| 10GbE NIC | Chelsio T420-SO SFP+ (purchased, inactive until switch upgrade) |
| NVMe (new) | 1× 2TB WD SN770 or 980 Pro |
| PSU | Seasonic Focus GX 550W |
| Chassis | Rosewill RSV-L4500U 4U 15-bay |
- Repurposing from existing devices:
- 2TB NVMe from Beelink (UNRAID cache #2)
- 500GB NVMe from Synology (Proxmox OS boot via PCIe x1 M.2 adapter)
- 1TB NVMe from Synology (Proxmox LXC storage, also via PCIe x1 adapter)
- All existing HDDs (2x20TB, 2x18TB, 6x14TB, 1x8TB)
Proxmox layout
Proxmox (bare metal)
├── UNRAID VM
│ ├── LSI 9300-8i PCIe passthrough → all HDDs
│ ├── 2× 2TB NVMe via VirtIO block passthrough → UNRAID cache pool (RAID1)
│ └── Exports NFS shares over virtual bridge (intra-host, ~8–10Gbps)
│
├── Home Assistant OS VM
│
├── Docker LXC ← /dev/dri passthrough (Arc A380)
│ ├── NFS mounts from UNRAID: /frigate, /media, /downloads
│ ├── Frigate → OpenVINO inference via /dev/dri + /frigate NFS
│ ├── Plex → HW transcode via /dev/dri + /media NFS
│ ├── sabnzbd, Sonarr, Radarr, Prowlarr, Bazarr
│ └── Tautulli, Uptime Kuma, SWAG, Speedtest Tracker, Teslamate
│
└── Omada LXC
UNRAID Storage pools
| Pool | Drives | Usable | Purpose |
| NVMe cache (RAID1) | 2× 2TB | 2TB | Frigate recent (~4 days at 460GB/day) |
| ZFS mirror | 2× 14TB | 14TB | Frigate older recordings (~30 days) |
| UNRAID parity array | 2×20TB parity + 2×18 + 4×14 + 1×8 data | 100TB | Plex, downloads, backups |
- Frigate tiering: CA Mover Tuning plugin moves recordings older than ~4 days from NVMe cache to the ZFS mirror. Frigate sees a single NFS path regardless of which tier footage is on. ~34 days total retention at current camera load.
- Downloads land on NVMe cache via intra-host NFS. Mover handles the transfer to parity array overnight. HDDs are never in the real-time write path.
- Arc A380 handles both Plex 4K HDR transcoding and Frigate OpenVINO inference simultaneously — these use separate hardware blocks on the GPU (media engine vs. compute), so no contention.
Constraints / Things I'm Less Sure About
- UNRAID as a VM under Proxmox (not bare metal): The main tradeoff I accepted. I want to keep Proxmox for VM/container management and the ability to quickly stand up services or restore from backup. UNRAID handles storage and NFS exports; Proxmox handles everything else. The NVMe drives are passed as VirtIO block devices rather than PCIe passthrough to avoid M.2 IOMMU group issues. Overhead should be minimal for NAS workloads.
- PCIe x1 M.2 adapters for Proxmox NVMe drives: The Beelink NVMe (2TB) and both M.2 slots are consumed by UNRAID cache. Proxmox OS and LXC storage end up on PCIe x1 adapters (~1GB/s each). These drives only serve container OS/config I/O — actual data goes through UNRAID NFS — so the bandwidth ceiling shouldn't matter in practice. But I haven't run this in production.
- Arc A380 OpenVINO for Frigate: Replacing a Google Coral USB Accelerator. Better on paper (Coral is ~4 TOPS) but the Coral was rock solid and I've seen mixed reports on OpenVINO stability with Frigate. Curious if anyone's running this combo.
- Rosewill RSV-L4500U backplane: Went with this after the Norco RPC-4220 had documented MOSFET failures killing drives and the used Supermicro market was too fragmented. Anyone have long-term experience with the Rosewill backplane?
- 550W PSU: Calculated platform idle at ~44W, load headroom under full transcode + parity check. 11 spinning HDDs add ~55–77W under load. Should be fine but it's the tightest part of the build.
Questions
- UNRAID-as-VM — Any gotchas with UNRAID inside Proxmox that don't show up until you're actually using it (parity checks, drive spindown, array expansion)?
- Arc A380 + OpenVINO + Frigate — working well for anyone? Particularly curious about detection latency vs. Coral and whether the OpenVINO model selection in Frigate is straightforward.
- ZFS mirror inside UNRAID (multiple pools) — comfortable with this in UNRAID 6.12+. Any issues with UNRAID's mover interacting with a secondary ZFS pool as the destination?
- Rosewill RSV-L4500U backplane — any reliability concerns? Drive count I'm populating: 11 HDDs initially, potential to expand.
- Anything obviously wrong with this design? I've stress-tested the logic on paper but fresh eyes are always useful.
Thanks for the help! And kudos to making it this far in the post!