A ZimaBoard 2 Prototype with Two 22 TB Drives on the Test Bench

Eva Wong is the Technical Writer and resident tinkerer at ZimaSpace. A lifelong geek with a passion for homelabs and open-source software, she specializes in translating complex technical concepts into accessible, hands-on guides. Eva believes that self-hosting should be fun, not intimidating. Through her tutorials, she empowers the community to demystify hardware setups, from building their first NAS to mastering Docker containers.

Thank you to u/sabitech2k for sharing an early ZimaBoard 2 prototype on the test bench. The original photograph puts the compact board between two 22 TB hard drives. A later owner reply confirms that the disks were recognized and formatted while using an aftermarket power supply, giving the thread a concrete storage result alongside the initial teardown.

The original prototype post dates from April 2025. It should be read as a historical test report. The account below separates that result from the further work needed to turn a bench setup into a dependable storage or backup service.

The Photograph Starts with a Specific Hardware Question

Sabitech2k’s ZimaBoard 2 prototype between two 22 TB Western Digital Ultrastar drives on a test bench
The ZimaBoard 2 prototype between two Western Digital Ultrastar DC HC570 drives labeled 22 TB each. Original photograph: u/sabitech2k, via the linked Reddit post.

The board's finned metal enclosure occupies the middle of the photograph, with a hard drive on either side. The labels and visible connections make storage the immediate focus. The arrangement is a test bench: components are accessible and the cabling can be examined directly.

That accessibility is useful while establishing what a system can recognize and use. A permanent home server brings additional questions, including mounting, cable strain, airflow and recovery. A photograph of connected hardware is a starting point for those decisions rather than a substitute for them.

The creator also linked an unboxing and teardown video from the post. Readers can follow that companion material for the original presentation; the reported disk result is documented separately in the Reddit replies.

What the Creator Actually Reported

Evidence Reported detail What it establishes
Original post Prototype received for testing, teardown and review An early evaluation stage
Drive photograph Two disks labeled 22 TB The physical devices pictured
Owner's follow-up Disks recognized, formatted and working A successful initial storage test
Power context Aftermarket 12 V, 10 A supply used The conditions attached to that result

The owner's disk-recognition reply is especially useful because it states both the outcome and a relevant test condition. Keeping those together lets another reader understand the result without assuming every power arrangement was tried.

Recognizing a disk, creating a filesystem and completing a sustained workload answer progressively different questions. The first confirms that the device is visible. The second shows that it can be prepared for use. A longer workload would help characterize repeated operation, temperatures and behavior over time. The published reply does not supply those additional measurements.

Keep Prototype Conditions with the Historical Result

The platform in the story is a ZimaBoard 2. For a current installation, the official ZimaBoard 2 setup guide is the appropriate place to check storage connections and power guidance. It documents two SATA connections and calls attention to the starting-current needs of dual 3.5-inch drives.

A prototype discussion and current setup instructions have different jobs. The former records what one tester used at a particular stage. The latter describes the supported installation process for readers building now. Keeping the date and test conditions visible prevents an old experiment from becoming an assumed specification for every later unit.

For another builder, the useful record would include the drive models, their connection method and the power arrangement, followed by the actual result observed. This makes a test repeatable enough to compare with a later change. Simply listing an adapter's current rating cannot provide that whole picture.

A Backup Server Already Had a Place in the Rack

In another reply, the creator explains that a first-generation ZimaBoard was already running Proxmox Backup Server in the rack. They also describe disabling its eMMC in the BIOS and booting from USB. Those details concern the existing machine, rather than establishing the prototype's operating-system layout.

The original ZimaBoard therefore has a defined role in the background of this story. The new hardware was being evaluated by someone who already had a compact server doing useful work.

The Proxmox Backup Server introduction describes a client-server system for backing up virtual machines, containers and physical hosts. It helps explain the role of a dedicated backup machine without implying that any newly attached disk is already a configured backup destination.

Our Proxbox backup-server story offers another example of giving recovery its own hardware role. The useful comparison is the job assigned to the machine, rather than the appearance of its case.

Capacity Labels Do Not Describe a Finished Storage Service

Two labeled capacities do not identify the filesystem, redundancy policy or usable shared space. A reader planning a NAS would still need to decide how the disks are presented to applications and what happens when a device becomes unavailable.

That decision is also separate from backup retention. A location used to store active files and a location used to recover earlier versions serve different needs. Before calling a similar bench setup ready for household data, a useful exercise would be to recover a small test file to another location and check that the intended contents return.

The creator's report supports an initial compatibility observation. It does not document a RAID layout, a usable-capacity measurement, a completed restore exercise or a long-term availability record. Those would be additional results to collect as a project moves beyond the bench.

Give the Next Test a Clear Pass Condition

A staged approach makes a hardware experiment easier to learn from. After basic recognition, choose one workload and define what a satisfactory result would look like. For file storage, that might mean writing and reading a known test set. For a backup role, it would include recovering a deliberately selected item.

Useful notes would record the software version, storage layout, test duration and observed outcome. This is reader guidance drawn from the evaluation stage, rather than a claim that the creator performed a particular benchmark or encountered a failure.

The ZimaBoard 2 dual-NVMe build provides a companion example of a different storage arrangement. Together, the cases show why the intended job should guide the drive layout and enclosure choices.

FAQ

Does this report guarantee compatibility with every large disk?

No. It describes the creator's particular test conditions. Other combinations need their own checks.

Was a protected storage array demonstrated?

The source does not establish an array layout or redundancy policy. Drive capacity alone cannot answer that question.

Which machine was already handling backups?

The creator assigns that role to the older board. The prototype discussion records a separate evaluation.

Is the aftermarket adapter a requirement for a current unit?

The historical test does not establish that. Use current official guidance for the hardware and drives being installed.

Conclusion

This case is useful because a specific result comes with its context. It records early storage testing while leaving room for the measurements and recovery checks that a permanent server would need. The next step for a similar project is to turn a promising connection test into a documented service with a clear, verifiable job.

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

Get More Builds Like This

Stay in the Loop

Get updates from Zima - new products, exclusive deals, and real builds from the community.

Stay in the Loop preferences

We respect your inbox. Unsubscribe anytime.