Thank you to u/g3rmw0rm for sharing a ZimaBlade NAS built around Proxmox, Linux containers and an NVMe drive in an enclosure. Samba provides file access, Jellyfin gives the media collection a playback interface, and the small machine leaves room for the owner to keep experimenting.
The original Reddit showcase and follow-up discussion capture both the working services and an unresolved storage problem. Nextcloud was still a planned addition, while a later exchange raised questions about a second hard drive and power during startup.
One Small Host Has Several Defined Jobs
A NAS can be understood through the services that make its files useful. Accessing a shared folder from a computer is one task. Browsing a library from a television is another. Those tasks may use the same stored content while needing different software and permissions.

| Part of the build | What the creator reports |
|---|---|
| ZimaBlade | The compact server at the center of the NAS |
| Proxmox | The host platform for Linux containers |
| Samba | Network file-sharing service |
| Jellyfin | Media-library service |
| NVMe drive in an enclosure | Described as the main drive |
| Nextcloud | A planned installation |
The hardware belongs to the ZimaBlade single-board server family. The source describes a Proxmox installation, so its software layout should be read on those terms.
Containers Separate Services While Sharing the Host
The Proxmox VE feature overview explains its support for Linux containers as well as full virtual machines. Containers share the host’s kernel, making them a different arrangement from giving every application a complete guest operating system.
For a compact server, organizing services this way can make their administration more manageable. A file-sharing change and a media-library change can be considered separately, even though both applications still depend on the same physical host.
That distinction is useful during troubleshooting. If both services lose access to a directory, the common storage path deserves attention. If only one fails, its own configuration or permissions become a more specific place to look. Restarting the host, meanwhile, interrupts every service it supplies.
Our small homelab story from u/jc-21 examines a different division of work across machines. Here, the separation happens within one small server, making the shared dependencies especially important to understand.
An NVMe Enclosure Adds Another Storage Path
The enclosure is a useful detail because it shows the owner expanding beyond the board’s immediate storage arrangement. The post identifies the enclosed NVMe as the main drive, but does not publish a complete map of boot files, container disks and shared data.
For another builder, that map is worth making before copying the idea. “Main drive” can refer to several different responsibilities. The disk that starts the operating system may also hold application configuration, while a different disk contains the files served to other devices.

When storage is exposed to a container, three names can matter: the physical device, the location where the host mounts it and the directory presented inside the container. Recording those relationships makes a missing folder easier to diagnose after a reboot or hardware change.
The source does not establish the enclosure’s connection speed or a measured benefit over another drive. Its contribution to the story is the additional storage option and the owner’s chosen role for it.
File Sharing and Media Playback Need Different Access
The Samba project overview describes its implementation of SMB services for Linux and Unix-like systems. A share provides a familiar way for another computer to reach files across the network.
Jellyfin adds an application view of the media. It needs to see the intended library directory and have permission to read it. A working network share therefore does not, by itself, show that the media service can see the same content inside its own environment.
For readers following this approach, a small sample is more useful than moving the entire collection immediately. Copy a file through the intended share, check the resulting location, then confirm that the library service can discover and play it. This is a suggested validation sequence, rather than a procedure documented by the creator.
Playback also depends on the client. The Jellyfin transcoding guide distinguishes Direct Play from conversion. The same server can face quite different loads depending on the file format and playback device, so the presence of Jellyfin does not establish a guaranteed number of streams.
The Second-Drive Discussion Remains Open
A later commenter asked whether the supplied adapter could support two hard drives alongside the rest of the setup. The creator then described difficulty with the second drive and also wondered whether that drive itself might be failing.
Those observations leave more than one possible explanation. The discussion does not include a controlled comparison that identifies the adapter, drive, cable or another component as the confirmed cause. It should therefore remain an account of troubleshooting in progress.
For someone investigating a similar symptom, recording when a drive disappears can narrow the question. Failure to appear during startup is different from losing access during a file copy, and both differ from a service pointing at the wrong directory. Keeping those observations separate makes a support request more useful.
The thread also mentions a connection-timing workaround. It is not a documented general solution, and this article does not turn it into an installation step. Hardware guidance should follow the exact board, power supply and drive combination being used.
Adding Nextcloud Would Add Another Data Relationship
Nextcloud was an intended next step. Its installation was not confirmed in the showcase, so it should not be counted among the completed services.
The plan is still informative: the same NAS may gradually grow from shared folders and media playback into application-managed files. For another owner, that is a good point to decide which application owns each directory and which configuration would be needed to bring it back.
The Proxbox backup-server story provides a related example of giving recovery a distinct role as a homelab expands. Adding another application is easier to assess when its data responsibilities are visible first.
FAQ
Is this a ZimaOS build?
The creator identifies Proxmox as the host platform. The official ZimaBlade overview provides broader hardware and operating-system context.
Was Nextcloud already running?
No completed installation is established in the source. It is described as the owner’s next planned service.
Did the thread confirm a power-supply fault?
No. Power and the condition of the second drive were both discussed, without a confirmed final diagnosis.
Do the photographs provide everything needed to reproduce it?
They show the physical arrangement. They do not supply a complete container, storage, permissions or recovery configuration.
Conclusion
This ZimaBlade NAS brings familiar household services onto a small Proxmox host. The enclosed NVMe, visible hard-drive frame and container-based services show how a compact machine can become a useful place to learn about storage and applications together.
The follow-up discussion also gives the story an honest stopping point: the build is useful while parts of its behavior still need investigation. For another builder, the practical lesson is to keep the storage paths and service responsibilities clear as each new component is added.
Welcome to the ZimaSpace community! Share your setup, ask questions, and explore practical build guides, real user stories, and product updates with fellow self-hosters.
Zima Campaign Hub
More to Read

A ZimaBoard 2 Prototype with Two 22 TB Drives on the Test Bench
Explore sabitech2k’s early ZimaBoard 2 drive test, the reported power conditions, and the existing ZimaBoard used for Proxmox backups.

A Quiet ZimaCube and ZimaBoard Homelab with Debian and Docker
A ZimaCube and ZimaBoard split everyday applications from smart-home services, with Debian, Docker, Pi-hole and a Homepage dashboard.

A LEGO Rack for a First ZimaBoard 2 Home Server
See how a first-time builder organized a ZimaBoard 2 and two SSDs in a LEGO rack, with Home Assistant and home-office storage planned next.



