> ## Content Index
> Fetch the complete content index at: https://corelab.tech/llms.txt
> Use this file to discover other available public pages before exploring further.

# The Ultimate OMV8 & Plex Media Server Guide (2026): Build Your Own 100TB NAS
- URL: https://corelab.tech/plexomv/
- Published: 2025-04-23T02:00:51.000Z
- Updated: 2026-11-01T16:41:10.000Z
- Description: Master your home lab with this 2026 update for OpenMediaVault 8. Learn to set up Plex on OMV8 using Docker Compose, optimize ZFS pools, and enable 4K transcoding.
- Author: Core Lab Joe
- Tags: OMV, Plex Media Server, NAS, #2025, #table-of-content

Are you sitting on a massive media collection but still struggling to stream it reliably? Whether you’ve got 20+ years of "Linux ISOs" (like I do!) or a meticulously ripped 4K Blu-ray library, or not. Maybe you dumped it into one giant folder? But just *having* it isn't enough. You need to *enjoy* it. You need more than just storage - you need a powerhouse.

In 2026, the duo of **OpenMediaVault 8 (Synchrony)** and [**Plex Media Server** ](https://corelab.tech/ultimate-media-server-guide/)remains the undisputed king of DIY NAS setups. Based on the rock-solid **Debian 13 (Trixie)**, OMV8 offers 20-35% better memory management than its predecessor and native support for the latest hardware.

Learning Path • Storage Architecture & NAS 

### Mastering OpenMediaVault & Storage Architecture 

Engineer reliable bare-metal NAS hardware, configure OpenMediaVault storage pools, execute seamless OS upgrades, integrate local media workloads, and recover from low-level filesystem corruption. 

Lesson 4 of 5 80% Complete 

Difficulty Curve Intermediate 

Beginner Advanced 

[ ✓ Lesson 01 · Hardware Architecture Completed The "Core Lab" Monster: My 80+TB DIY NAS Build → ](https://corelab.tech/diy-nas-server-build/) [ ✓ Lesson 02 · Storage Foundation Completed How to Setup Open Media Vault 8 (OMV8) & Run ZFS → ](https://corelab.tech/setup-omv/) [ ✓ Lesson 03 · Debian 13 Upgrade Completed OpenMediaVault 8 Upgrade Guide: Debian 13 & Kernel Jump → ](https://corelab.tech/omv8-upgrade-guide/) 

04 

Lesson 04 · Media Server Integration Current Lesson 

The Ultimate OMV8 & Plex Media Server Guide: 100TB NAS 

[ 05 Lesson 05 · Disaster Recovery Capstone Recovering OMV8 After Filesystem Corruption & Kernel Drift → ](https://corelab.tech/omv8-filesystem-corruption-dkms-recovery/) 

Tested in production on 80+TB ZFS storage array 

Core Lab Learning Track · Zero Tracking & Direct Implementation 

In this guide, we’ll walk through a fresh OMV8 install, ZFS pool configuration, and a modernized Docker-based Plex setup.

This is a lengthy one, so have a snack, grab your favourite beverage and strap in for the ride. I've been running Plex since 2013, OMV since 2022, and various Linux server distros since 2012 so I'll help you throughout the whole process!

🤓

This is the Core Lab's [custom NAS](https://corelab.tech/diy-nas-server-build/) setup!

---

## Why Choose OMV8 Synchrony for Your Media Server?🤔

Before we dive into the "how," let’s talk about the "**why**." There are plenty of NAS operating systems - Unraid, TrueNAS SCALE, and more - but OMV8 stands out for its ***flexibility***. It’s essentially "Debian with a beautiful face," giving you full root access without any proprietary overhead or hindrances.

### Pre-Requisites

- **A target x86 system:** (OMV8 has officially dropped support for legacy 32-bit CPUs).
- **USB Drive:** To burn the OMV8 ISO.
- **Network:** An Ethernet connection (WPA3 is now supported for Wi-Fi, but wires are **always** better for 100TB+).
- **The "Core Lab" Special:** A strong coffee or a smoky whisky.🥃

---

## Open Media Vault 8

We'll blast through this!

## Phase 1: Creating Your OMV8 Bootable Media

1. **Download the OMV8 ISO:** Grab the latest "Synchrony" image from the [official OpenMediaVault downloads page](https://www.openmediavault.org/download?ref=corelab.tech).
2. **Flash the Drive:** Use **Rufus** (Windows) or **Etcher** (Mac/Linux).
  - *Note:* In 2026, most BIOS are UEFI-only. Ensure you select "GPT" as the partition scheme in Rufus for modern hardware (last 10 yrs or so).
3. **Check Hardware Compatibility:** OMV8 runs on Linux Kernel 6.12+. If you’re using brand-new 2026 hardware, this kernel is your best friend for driver support.

## Phase 2: Installing OMV8 (The Debian 13 Base)

1. **Boot from USB:** Mash that `F12` or `Del` key and prioritize your USB drive.
2. **Network Config:** Stick with DHCP for now. You can set a Static IP or VLANs once the WebGUI is live.
3. **The Hostname:** Pick something legendary. I named mine "Codex." (Ten points if you know the sci-fi reference!)🤓
4. **Root Password:** **Do not lose this.** This is the keys to the (your new!) kingdom!
5. Follow the onscreen prompts for initial setup which walks you through creating users and enabling some services.
  1. We'll cover the exact RAID/ZFS/storage array setup below!
6. Once you're done this, do an update / apply any and all updates that are pending!

> **Pro Tip:** Install OMV8 on a dedicated small SATA or NVMe SSD. Don't waste your massive 20TB storage drives on the OS; keep your data and OS separate! You can even install it and run OFF a USB - permanently!

## Phase 3: Optimizing OMV-Extras and ZFS

Once you log into the Web Interface (using `admin` / `openmediavault`), we need to unlock the real power.

### 1\. Install OMV-Extras

SSH into your server and run this "magic" command: `wget -O -https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash`

### 2\. The ZFS Deep-Dive

Go to **System > Plugins** and install `openmediavault-zfs`.

- **The Kernel Secret:** For the best ZFS performance, go to the **OMV-Extras** tab and install the **Proxmox Kernel**. This provides better ZFS compatibility and lower latency for media streaming. This bumps you from Linux Kernel v6.12+ to v6.17+!
- **Create Your Pool:** Under **Storage > ZFS**, create a new Pool. I recommend **RAIDZ2** (dual-drive parity) for anything over 50TB. It gives you the peace of mind that even if two drives fail at once, your media and files are fairly safe.
  - Give it a meaningful name that is different from our NAS itself.

## Phase 4: Finalizing OMV8 Setup

- **Configure Services:** Configure the services you want to use, such as SMB/CIFS (for Windows file sharing), NFS (for Linux/Unix file sharing), and FTP.
  - I **VERY STRONGLY** suggest utilizing NFS as much as you can; SMB is inferior in almost every way.
- **Set up Users and Permissions:** Create user accounts and set up appropriate permissions to control access to your files and services.

😲

****Note:** FILE system permissions can conflict with your SHARE permissions, so take your time here to set these up properly. This is where 90% of new OMV users get 'stuck'!

- Test, try to map your shares from linux (NFS) and/or Windows (SMB) clients.

> I found setting the shared folder to accept clients in my whole "home lan" subnet was best, as I mapped my SMB & NFS shares from multiple systems across my home and subnet. You may chose to use /32 instead. Lastly, under "Extra options" for my shared folders, I put these in: rw,async,insecure,no\_subtree\_check,all\_squash,anonuid=1000,anongid=100,crossmnt

> Not the most secure settings, but if someone is poking around at my shares, I've already failed at securing my network.

---

## Plex Media Server Setup

The easy part!

## Phase 5: Installing Plex Media Server (The Docker Way)

In 2026, we no longer install Plex directly onto the OS. Why? Because **Docker Compose** makes backups, updates, and hardware transcoding WAY easier. From a cybersecurity standpoint it also allows you to not expose your new OMV8 NAS directly to the internet via a port forward, regardless of how much we may trust Plex.

To run Plex as a minimum, you should have 2GB of RAM available for it and an x86 processor.

1. **Install Compose:** Go to **Services > Compose** and enable it.
2. **The Stack:** Create a new "File" in the Compose tab and paste this optimized configuration:

```yaml
services:
  plex:
    image: lscr.io/linuxserver/plex:latest
    container_name: plex
    network_mode: host
    environment:
      - PUID=1000
      - PGID=100
      - VERSION=docker
    volumes:
      - /path/to/your/zfs/config:/config
      - /path/to/your/media:/data
    devices:
      - /dev/dri:/dev/dri # This enables Intel QuickSync Transcoding!
    restart: unless-stopped
```

🤖

This is a very basic deployment, for NVIDIA GPU passthrough there are other pre-requisites and configuration required!  
  
Here's a post with a pile of info if you are just starting out [with docker compose, this is a complete guide](https://corelab.tech/setupcompose/).

### 2026 CPU & Transcoding Requirements

If you want to stream 4K HDR to your friends, RAM and CPU matter more than ever. Although Plex's support for AMD CPU & Chips isn't "official", I'll tell you from firsthand experience it works NO PROBLEM. Google it, plethora of "field research" there stating performance. If you fully intend on setting up a transcoding beast like I have, [have a deep dive read here.](https://corelab.tech/transcoding-architecture-nvenc-vs-quicksync/)

| Transcode Type                 | Recommended CPU           | Recommended RAM |
| ------------------------------ | ------------------------- | --------------- |
| **Direct Play (No Transcode)** | Intel N100 / Alder Lake-N | 8GB             |
| **4K HDR (1-2 Streams)**       | Intel Core i5 (12th Gen+) | 16GB            |
| **4K HDR (5+ Streams)**        | Ryzen 7 7000+ or Intel i7 | 32GB+           |

#### **Intel Chips**

| **Transcode**               | **Minimum CPU**       | **RAM** |
| --------------------------- | --------------------- | ------- |
| No Transcode                | Intel “Atom” 1.2GHz   | 2GB     |
| Single 720p transcode       | Intel Core i3 3.0 GHz | 2GB     |
| Single 1080p transcode      | Intel Core i5 3.0GHz  | 2GB     |
| Single 2160p (4K) transcode | Intel Core i7 3.2GHz  | 2GB     |

#### **"Unofficial" AMD Chips**

| **Transcode**                   | **Minimum CPU**     | **RAM** |
| ------------------------------- | ------------------- | ------- |
| A few 720/1080p transcodes      | Ryzen 3 4300G       | 2GB     |
| Multiple 720p/1080p transcodes  | Ryzen 7 5600G/5700G | 2GB     |
| MANY 1080p transcodes, a few 4k | Ryzen 5 5800X       | 2GB     |
| Multiple (4K) transcodes        | Ryzen 5 7600        | 2GB     |

✋

Although the minimum RAM is stated as 2GB, you will need way more! Minimum really should be 8GB, if not 16\. With a busy server doing multiple concurrent transcodes and a large media library, you'd even want 32-64Gb.   
  
[This Plex Optimization Guide](https://corelab.tech/plexoptimization/) will explain why and how you can use that RAM!

---

## Troubleshooting & Conclusion

If the WebGUI becomes unresponsive, don't panic. Hop into the terminal and use the life-saving set of commands: `sudo su` and then `omv-firstaid`

This menu allows you to reset your network, fix the workbench port, and clear locks.

Also plenty of fantastic documentation & guides here:

[https://help.openmediavault.org/](https://help.openmediavault.org/?ref=corelab.tech)

## **Conclusion**

There you have it, your very own brand new NAS & [streaming media server](https://corelab.tech/ultimate-media-server-guide/)!

To get NVIDIA GPU hardware transcoding working, first you need to [setup the NVIDIA Container toolkit.](https://corelab.tech/nvidiatoolkit/)

Then I suggest you head on over to my [Plex optimization guide](https://corelab.tech/plexoptimization/) and checkout how to take full advantage of your [hardware.](https://corelab.tech/homelab-hardware-guide/)

### **Resources:**

- [Open Media Vault Documentation](https://www.openmediavault.org/?ref=corelab.tech)
- [Plex Media Server Documentation](https://support.plex.tv/?ref=corelab.tech)

[InstallationPreparation Before You Begin Before you begin installing Plex Media Server, it’s strongly recommended that you check that your media…![](https://corelab.tech/content/images/icon/plex-180-3.png)Plex Support![](https://corelab.tech/content/images/thumbnail/windows-systemtray-plex.png)](https://support.plex.tv/articles/200288586-installation/?ref=corelab.tech)

---

## ❓ Frequently Asked Questions (FAQ)

### Does Plex officially support AMD CPUs for transcoding?

Not officially, but it works without issue in practice. Plenty of self-hosters run Ryzen chips for hardware transcoding with no problems, even though Plex's official support documentation focuses on Intel Quick Sync.

### How much RAM do I actually need for a Plex/OMV8 media server?

More than the stated minimums suggest. While Plex lists 2GB as a technical minimum, a realistic baseline is 8-16GB, and a busy server doing multiple concurrent 4K transcodes with a large library benefits from 32-64GB.

### What CPU do I need for multiple simultaneous 4K HDR transcodes?

For 1-2 simultaneous 4K HDR streams, an Intel Core i5 (12th Gen+) with 16GB RAM is a solid baseline. For 5+ simultaneous 4K HDR streams, step up to a Ryzen 7 7000-series or Intel i7 with 32GB+ RAM.

### What do I do if the OMV8 WebGUI becomes unresponsive?

Don't panic — SSH into the server, run `sudo su` followed by `omv-firstaid`. This built-in menu lets you reset your network configuration, fix the web interface port, and clear stuck locks without a full reinstall.

### Do I need anything extra for NVIDIA GPU hardware transcoding?

Yes — you need to set up the NVIDIA Container Toolkit before Plex in Docker can access your GPU for hardware transcoding. Without it, Plex will fall back to CPU-only software transcoding.

---

## Sign up for Core Lab

Subscribe 

Email sent! Check your inbox to complete your signup. 

Building Your Digital Fortress. Explore & unlock your own digital space. Discover tutorials & project updates as we build and experiement with homelabbing, smart homes & secure self-hosting!