Community Solution

ZimaCube N100 Running Xpenology DSM 7.2 with Arc Loader

A June 2024 ZimaCube N100 owner successfully booted Synology DSM 7.2 through the community Arc Loader, then tested 10Gb networking, SSD cache, a 32 GB RAM upgrade, and additional cooling.

A community user successfully ran Synology DSM 7.2 on the original ZimaCube N100 in June 2024 by using the third-party Arc Loader/Xpenology project. The system booted, detected the built-in hardware and an added Intel 10Gb NIC, and was later expanded with SSD cache, 32 GB of RAM, and a Noctua low-profile cooler.

This was an unofficial community experiment, not a ZimaSpace-supported DSM installation path. Arc Loader remains an active community project in 2026, but it is independent from Synology and explicitly describes itself as a boot helper for DSM/Xpenology. Synology's current software and Package Center terms place restrictions on use outside Synology devices, so anyone reproducing the experiment should review those terms and understand that normal Synology support, licensing, updates, and hardware compatibility cannot be assumed.

What the Original ZimaCube N100 User Tested

The source author received an N100-based ZimaCube and tried DSM 7.2 through Arc Loader. Their first report said the installation worked and that the available hardware, including an added Intel 10Gb network card, was detected without an obvious error.

The initial configuration later grew to:

  • two 18 TB Seagate enterprise hard drives;
  • two 460 GB SATA SSDs intended for cache;
  • an Intel 10Gb NIC;
  • a Crucial 32 GB memory module;
  • a Noctua NH-L9i low-profile heatsink/fan.

The source author specifically identified the 32 GB RAM module as:

Crucial CT32G4SFD832A

They reported that it worked in their machine even though the memory configuration was outside the originally supported specification. Treat that as one-user hardware evidence, not a universal compatibility guarantee.

The Historical Arc Loader Method Shared in the Thread

When another community member asked how DSM had been installed, the author described this high-level workflow:

  1. Download Arc Loader.
  2. Write the Arc image to a USB drive.
  3. Set the ZimaCube BIOS/UEFI boot order so USB boots first.
  4. Boot Arc Loader.
  5. Follow the guided setup.
  6. For the N100 system in that 2024 test, select a Synology DS1520+ profile.

The source author described Arc as the easiest RedPill/Xpenology loader they had personally used.

Current Arc project: AuxXxilium Arc Loader on GitHub.

The DS1520+ Profile Was a 2024 Community Choice

The recommendation to emulate a DS1520+ came from this specific June/July 2024 test. Arc Loader has continued to evolve, and its hardware profiles, modules, patches, DSM compatibility, and recommended models can change.

Do not treat DS1520+ as a permanent best profile for every ZimaCube, ZimaCube Pro, or later hardware revision. Check the current Arc compatibility information before testing a newer system.

Arc Loader Is Still Active in 2026

The Arc project remained actively maintained in 2026, with current releases in the 3.x series. Its documentation describes Arc as a customized RedPill loader for DSM 7.x with additional hardware support, addons, and guided installation.

The project also makes several boundaries explicit:

  • Arc and DSM are independent projects.
  • Arc is a boot helper for DSM.
  • DSM remains owned and copyrighted by Synology.
  • Arc says commercial use of the loader is not permitted.
  • Custom bootloader modifications can risk data loss.

Those warnings matter more than simply confirming that a 2024 boot test succeeded.

The 10GbE Transfer Test Was Much Slower Than Line Rate

After adding SSD cache, the author tested a file transfer over a 10Gb network link and reported an average of only about:

120 MB/s

That is far below the theoretical throughput of 10GbE. The author did not establish a confirmed root cause. They suspected either that the SSD cache was not working as expected or that a bottleneck existed in the SATA path and planned to try PCIe-attached cache storage later.

Do not turn this single result into a claim that ZimaCube hardware is limited to 120 MB/s. It was one early DSM/Xpenology test with a specific storage layout and no final bottleneck analysis.

What Happened with SSD Cache?

The source author installed two SATA SSDs for cache but did not post a completed before/after cache benchmark. Their 120 MB/s transfer result led them to question whether cache was active or whether the storage path was limiting throughput.

Because the thread never confirmed the cause, a migrated page should preserve that uncertainty rather than claiming SSD cache failed.

The 32 GB RAM Upgrade Worked for One User

The original N100 ZimaCube shipped with 8 GB in this discussion, and the author expected that amount to become restrictive once many Docker containers were running. They later installed a 32 GB Crucial module and reported that the system operated normally.

This is useful community evidence, but unsupported memory configurations can behave differently across firmware revisions and workloads. Memory detection at boot does not by itself prove long-term stability under load.

The Thread Also Mentioned ZimaCube Pro

Later in the discussion, the same author said they had also installed Xpenology successfully on a ZimaCube Pro, although they had moved that machine back to Unraid. Another user asked about NVIDIA GPU and Thunderbolt/USB4 support, but the thread did not provide a confirmed profile that enabled those features under DSM.

Do not extrapolate the N100 result into guaranteed NVIDIA, Thunderbolt, or USB4 support.

DSM Licensing and Support Need to Be Considered Separately

Synology DSM is proprietary software. Synology's current EULA describes the software as licensed, not sold, and limits permitted use in connection with Synology products. Current Package Center terms also state that Package Center should not be accessed from a non-Synology device.

Review the current Synology EULA and applicable service/package terms before deciding whether to use DSM on non-Synology hardware.

A successful community boot test does not grant Synology support, warranty coverage, Package Center rights, update compatibility, or a license exception.

Do Not Test Xpenology First on Irreplaceable Data

Arc itself warns that bootloader customization can result in irreversible data destruction. DSM updates can also change kernel, driver, storage, or loader compatibility.

For experimentation:

  1. use test disks first;
  2. keep independent backups;
  3. do not make the Arc USB or DSM array your only copy of important files;
  4. verify networking and storage before migrating production data;
  5. check Arc compatibility before every major DSM update.

What This Community Thread Proves—and What It Does Not

Source-supported result Not established by the thread
DSM 7.2 booted on one ZimaCube N100 with Arc Loader Official DSM support on ZimaCube
Intel 10Gb NIC was detected in that setup Full compatibility with every NIC or DSM update
32 GB Crucial RAM worked for the author Guaranteed supported memory configuration
Two SATA SSDs were installed for cache A confirmed cache-performance gain
One 10Gb LAN transfer averaged about 120 MB/s A proven ZimaCube hardware throughput limit
Arc DS1520+ profile worked in the 2024 N100 test Best current profile for all Zima hardware

ZimaCube Xpenology DSM FAQ

Did DSM 7.2 actually run on the ZimaCube N100?

Yes. The source author reported a successful Arc Loader/Xpenology installation and detected hardware, including an added Intel 10Gb NIC.

Which Arc profile did the author use?

The 2024 reply recommended the DS1520+ profile for that N100 test. Current Arc versions may have different recommendations.

Is DSM officially supported by ZimaSpace on ZimaCube?

No. This is an unofficial community experiment using a third-party bootloader.

Did 32 GB RAM work?

The author reported success with Crucial CT32G4SFD832A on their N100 unit, but that does not make it an official compatibility guarantee.

Why was 10GbE only around 120 MB/s?

The thread did not establish the root cause. The author suspected cache or SATA-path limitations and planned additional testing.