Bottom Line: A Reinstall or System-Disk Change on Third-Party Hardware Can Trigger a Plus Activation Conflict
The TerraMaster case moved ZimaOS from a USB boot drive to SSD and then received “This code has been used on another device.” Support issued a replacement code and activation succeeded. A second user reported the same pattern after moving from USB to SSD. That proves this was a real recovery path, but it does not prove that the license is officially defined as “bound to the system drive.” Current ZimaOS pricing only states that a purchased Plus license is bound to a single device.
First Separate Official Zima Hardware From Third-Party Hardware
Current ZimaOS pricing says official Zima devices already include ZimaOS+ and should auto-activate even after reinstall. A TerraMaster or generic x86 machine uses a purchased Plus entitlement instead, so reinstall/replacement behavior can follow a different activation path.
The ZimaOS Plus licensing is the current source for plan and device-binding language.
Do Not Buy a Second License Immediately
If the same third-party server was licensed before the reinstall, collect the existing activation information and contact IceWhale support first. The 2026 source cases were resolved by reissuing a code rather than asking users to purchase another entitlement.
What to Send Support
- ZimaOS version before and after reinstall.
- Hardware model.
- Whether the system drive changed.
- The exact activation error.
- Your purchase email/order reference.
- Current device identifier shown by ZimaOS, if available.
Do not publish order numbers or activation codes in a public forum post. Treat them as account/licensing data.
Why a Disk Move Can Look Like a Different Device
Licensing systems can derive activation identity from more than one hardware/software attribute. The community outcome suggests that moving the boot medium changed enough state for the service to reject the old one-time code, but IceWhale's current public pricing does not document the exact fingerprint algorithm. Avoid turning a support observation into a guaranteed rule.
If you need a block-level safety copy before replacing boot media, Clonezilla disk imaging is one independent option for advanced users. For broader recovery planning, NIST recovery planning reinforces the same principle: preserve a tested recovery path before changing the system that holds your configuration.
Back Up Before Moving From USB to SSD
Even when the license can be recovered, app data and user files are separate risks. Protect AppData, databases and important files before changing the system disk. The ZimaOS backup covers that recovery layer.
Use a Proper System Disk for Long-Term ZimaOS
A small USB thumb drive is convenient for testing, but long-term write workload, heat and reliability vary widely by device. Moving production ZimaOS to SSD is a reasonable design choice; just plan entitlement and data recovery before the move.
The ZimaOS installation recovery provides the current reinstall baseline.
Official Zima Hardware Has a Different Plus Promise
Current pricing says official ZimaBoard, ZimaBoard 2, ZimaCube and ZimaBlade devices include ZimaOS+ and auto-activate after system reinstall. If an official Zima device does not recover Plus automatically, that is a stronger support case because the published expectation is explicit.
The ZimaBoard 2 Plus and ZimaCube 2 Plus show current official device options.
Keep Activation Recovery Separate From OS Recovery
If ZimaOS boots, storage mounts and apps work but only Plus activation fails, do not reinstall repeatedly. Repeated OS changes can create new storage/app risks without solving a server-side entitlement mismatch. Fix the license layer through support.
Document the Entitlement After It Is Restored
Once Plus is active again, keep the purchase receipt and support resolution outside the NAS. Before the next system-disk replacement, confirm the current licensing policy because activation implementation can change over time.
FAQ
Is ZimaOS Plus tied to the system drive?
Current public pricing says a purchased Plus license is bound to one device, but it does not publicly define the exact hardware fingerprint. Do not treat system-drive binding as an official universal rule.
What if my code says it was used on another device?
If this is the same licensed server after a reinstall or boot-drive change, contact IceWhale support with the existing purchase details instead of buying another code immediately.
Does official Zima hardware need a Plus code?
Current pricing says official Zima hardware includes ZimaOS+ and should auto-activate after reinstall.
Will reinstalling again fix the activation code?
Usually not if the problem is an entitlement mismatch. Repeated reinstalls add risk without changing the server-side license state.
Should I publish my order number in the forum?
No. Send purchase references and activation details privately to support.
