Get AI summaries of any video or article — Sign up free
how to build a Raspberry Pi NAS (it’s AWESOME!!) thumbnail

how to build a Raspberry Pi NAS (it’s AWESOME!!)

NetworkChuck·
5 min read

Based on NetworkChuck's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Use a Raspberry Pi 4 (4GB or 8GB RAM) plus Raspberry Pi OS Lite with SSH enabled to run the NAS headlessly.

Briefing

A credit-card-sized Raspberry Pi can be turned into a practical network-attached storage (NAS) box—complete with a Plex media server—by pairing Raspberry Pi OS Lite with OpenMediaVault and an external USB drive. The payoff is a low-cost, portable “away-from-home” library for movies, plus a simple way to offload camera footage and access files across devices on the same network.

The build starts with hardware selection: a Raspberry Pi 4 with 4GB or 8GB RAM, a power adapter, an SD card, and a USB hard drive or SSD. For the storage layer, the transcript emphasizes that speed and reliability matter—Samsung T5 SSDs are recommended, while larger Seagate drives are also viable. A Geekworm kit is mentioned as an optional upgrade that adds an internal SSD via a Raspberry Pi hat, but the core steps remain the same whether the drive is external or internal.

Software setup begins on a computer using Raspberry Pi Imager. The process installs Raspberry Pi OS Lite (no desktop) onto the microSD card, then uses Imager’s options to enable SSH and set the Pi user password. Wi‑Fi is possible, but the instructions push Ethernet for stability. The result is a headless Raspberry Pi that can be managed remotely.

Once the Pi boots, the next task is finding its IP address from the home router’s DHCP list. SSH access then follows with a command of the form `ssh pi@<ip>`, using the password set during imaging. After logging in, the system is brought up to date with `sudo apt update` and `sudo apt upgrade`.

To convert the Pi into NAS storage, OpenMediaVault is installed using a one-command script pulled from GitHub via `wget` and executed with `bash`. After installation, the web interface is reached in a browser (using the Pi’s IP). The first security move is changing the default OpenMediaVault web administrator password, since leaving defaults invites trouble.

Next comes the storage workflow inside OpenMediaVault: plug in the USB drive, confirm it appears under Discs, mount it, then create a shared folder (named “nasty” in the walkthrough) and grant the Pi user read/write privileges. Access is enabled through SMB (Windows file sharing) and NFS (Linux/macOS file sharing). When NFS throws an error, the fix described is destructive: stop SMB, delete the shared folder, unmount the drive, wipe it, recreate an Ext4 filesystem, and then re-enable SMB and NFS. After that, Windows File Explorer can connect to the share via the Pi’s IP and the configured credentials, and large file transfers are tested by copying a video.

With storage working, Plex media server is installed on the same Pi using apt commands after adding Plex’s repository and keys. Plex is then accessed via a browser on port 32400, signed into with a free Plex account, and configured to scan a “movies” folder on the NAS. The end state is a networked library accessible from phones through the Plex app, plus the ability to keep media and footage synchronized between home and travel. The transcript closes by reiterating that the same approach scales from a simple external drive to a more integrated Geekworm internal SSD setup.

Cornell Notes

The core idea is to repurpose a Raspberry Pi 4 into a NAS by installing OpenMediaVault and attaching a USB storage drive, then add Plex Media Server so the same box becomes a streaming library. The workflow starts with Raspberry Pi OS Lite, enabling SSH during SD-card imaging, and using router DHCP to find the Pi’s IP for remote login. OpenMediaVault then mounts the external drive, creates a shared folder with correct read/write permissions, and enables SMB and NFS for cross-platform access. Plex is installed via apt after adding Plex’s repository, and it scans a NAS folder (like “movies”) so content plays on phones through the Plex app. This matters because it turns a cheap, portable device into always-available storage and media streaming.

Why does the setup begin with Raspberry Pi OS Lite and SSH enabled before the Pi ever boots?

Using Raspberry Pi OS Lite avoids a desktop environment and keeps the system focused on storage and services. Enabling SSH during SD-card imaging creates a headless workflow: after boot, the Pi can be managed remotely without attaching a monitor, keyboard, or mouse. The transcript also notes that Ethernet is preferred over Wi‑Fi for reliability, which further supports a smooth headless install.

How does the build find the Raspberry Pi’s IP address, and why is that step necessary?

After the Pi boots, the IP address is pulled from the home router’s DHCP device list by checking the most recently assigned address. That IP is required for SSH (`ssh pi@<ip>`) and later for the OpenMediaVault web UI and Plex web access. Without the IP, remote login and browser-based configuration can’t happen.

What are the main OpenMediaVault steps to turn a USB drive into usable NAS storage?

Inside OpenMediaVault: (1) plug in the USB drive and confirm it appears under Discs, (2) mount it under File Systems, (3) create a shared folder under Access Rights Management → Shared Folders, and (4) set privileges so the Pi user has read/write access. Changes often require clicking Apply to commit settings. Only after mounting and permissions are correct does the share become accessible over the network.

What’s the difference between SMB and NFS in this NAS setup, and how does the transcript handle both?

SMB is the file-sharing protocol commonly used by Windows, while NFS is used by Linux and also works with macOS. The transcript enables both services so the NAS can be accessed from multiple operating systems. It also adds the same shared folder (“nasty”) to each service’s share list, then applies changes.

What troubleshooting path is described when NFS fails to apply, and what does it cost?

When NFS-related errors appear, the fix involves wiping and reformatting the USB drive. The transcript describes stopping SMB, deleting the shared folder, unmounting the drive, then using Wipe under Discs to erase everything. After that, it recreates an Ext4 filesystem and re-enables SMB and NFS. The tradeoff is data loss on the drive.

How does Plex get wired into the NAS, and what does Plex actually scan?

Plex is installed on the Pi via apt after adding Plex’s repository and keys. In Plex’s setup wizard, a library (e.g., Movies) is created and pointed at a folder on the NAS share (like “movies” inside the “nasty” share). Plex then scans that folder on the mounted storage so the media becomes playable in the Plex app on phones and other clients.

Review Questions

  1. What specific settings during SD-card imaging make the Raspberry Pi manageable without a monitor (and which network method is recommended)?
  2. In OpenMediaVault, what sequence of actions is required before a network share works (mounting, shared folder creation, privileges, and applying changes)?
  3. If NFS errors persist, what destructive recovery steps are described, and why might they resolve the issue?

Key Points

  1. 1

    Use a Raspberry Pi 4 (4GB or 8GB RAM) plus Raspberry Pi OS Lite with SSH enabled to run the NAS headlessly.

  2. 2

    Attach a USB hard drive or SSD; the transcript recommends fast SSDs like Samsung T5 for performance.

  3. 3

    Install OpenMediaVault via a GitHub script, then immediately change the default OpenMediaVault web administrator password.

  4. 4

    Mount the external drive, create a shared folder, and set read/write privileges for the Pi user before enabling network protocols.

  5. 5

    Enable SMB for Windows compatibility and NFS for Linux/macOS; both can be configured to point at the same shared folder.

  6. 6

    If NFS configuration errors occur, the described fix is to wipe and recreate an Ext4 filesystem on the drive, which erases existing data.

  7. 7

    Install Plex Media Server on the same Pi, then configure Plex libraries to scan folders inside the NAS share for streaming access.

Highlights

OpenMediaVault turns a Raspberry Pi into a real NAS by mounting a USB drive, creating a shared folder, and exposing it over SMB/NFS.
The walkthrough’s NFS troubleshooting is practical but destructive: wiping and reformatting the drive to Ext4 resolves persistent NFS errors.
Plex is installed on the NAS itself, then pointed at a NAS folder (like “movies”), enabling playback through the Plex app on phones.

Topics

  • Raspberry Pi NAS
  • OpenMediaVault
  • SMB NFS
  • Plex Media Server
  • Headless SSH Setup

Mentioned

Get summaries like this for any content

Videos, articles, research papers — all summarized by AI and searchable in one place.

Start building your library