I wanted to add an attached hardware RAID to my existing setup so I could have a dedicated partition to back up the various family computers around the house. This RAID would be connected via USB so that if a recovery is necessary I could simply disconnect from the NAS and restore locally over USB which would be much faster than over the network.
I figured it was also a good time to upgrade the storage of my primary disks. So the goal was to use my old disks for the external hardware RAID and the new larger disks as my primary NAS storage. Here’s a summary of my setup:
- A software RAID 1 is being used for the NAS storage
- A hardware RAID 1 is being used for the external USB storage
- The hardware RAID will be formatted as NTFS to allow for USB interface with different OS types
I would have preferred the software RAID for the external drive, but it would only work on Linux.
Let’s get started.
- Install the new larger capacity drives in the external enclosure with JBOD enabled and create a software RAID using
mdadm( I formatted my drives using
- Plug the external enclosure into NAS
- rsync the old partition to the new partition
- Login to OMV and move existing shared folders to the new partition
- Power down NAS and remove the old drives
- Insert the new drives into NAS, power up and verify operation.
- Insert old drives into the external enclosure and follow the instructions in the manual to enable RAID 1 (see instructions at the end of this post)
- Fix docker containers. Docker could not see my containers and images even though OMV reported the default location as the new shared folder path. Reinstalling docker and resetting the default path fixed this issue.
Edit 20190714: Reinstalling docker did not completely resolve the issue since the containers also appeared to contain references to the old volume. To fix this i removed the Portainer container and reestablished it. Then I used Portainer to “recreate” the containers which appeared to be the most trivial approach.