Migrating from JBOD to Raid

Operating System ZimaOS
1

Hello Everyone,

I just started with my very first home server and am very happy so far. :slight_smile:

Since storage prices are very high right now and my home server only has nvme storage options, I went with a single NVME SSD configured as a JBOD and a USB-HDD for backups. The ZimaOS is running on a built-in eMMc memory.

What is the best way to migrate the Data and Docker Containers from the JBOD to a Raid-1 or 5 configuration when I add more storage later on?

Thank you very much!

2

You are thinking about this the right way.

Based on how ZimaOS handles storage today, there is no supported in-place conversion from a single-disk JBOD to RAID-1 or RAID-5. The system uses mdadm underneath, and the Storage UI creates fresh arrays from selected unused disks. It does not offer a migrate or convert option for turning an existing single disk into a RAID set without rebuilding.

Official documentation and community upgrade threads consistently follow the same workflow when changing layouts:

backup > create new array > restore.

Recommended migration path

  1. Back up everything first
    Back up:
  • /DATA/AppData
  • All shares
  • Any custom bind-mounted folders

Use the ZimaOS Backup app or copy to your USB HDD manually. Verify the backup is readable before proceeding.

  1. Install the new NVMe drives
    Shut down, install additional NVMe drives, then boot back into ZimaOS.
  2. Create a fresh RAID array
    In Storage, use Combine and create:
  • RAID-1 (2 drives), or
  • RAID-5 (3+ drives)

This will initialize and wipe the selected disks. Your original single NVMe remains untouched at this stage.

Wait until RAID status shows Normal. Do not start heavy writes while it is still initializing or resyncing.

  1. Restore data to the new RAID
    Stop all Docker containers before copying data.

Restore:

  • /DATA/AppData
  • Shares
  • Any custom paths

You can use the Backup app restore or copy manually. Stopping containers avoids file locks and corruption.

  1. Verify before wiping the old disk
    Confirm:
  • All containers start cleanly
  • No permission errors
  • Data is accessible
  • RAID status remains Normal

Only after full verification should you wipe or repurpose the original single disk.

Additional notes

  • RAID-1 and RAID-5 follow the same migration logic.
  • RAID-5 requires at least three drives and will have longer parity initialization times.
  • There is no exposed mdadm grow workflow in the UI for single-disk to RAID transitions.

Final reminder

RAID is redundancy, not backup. Keep your USB backup in place even after moving to RAID, and consider a proper 3-2-1 strategy if the data matters.

Your plan to stage on a single NVMe now and move to RAID later is completely reasonable. Just follow the backup > rebuild > restore approach and you will avoid headaches.

1 Like