Convert raidz1 to raidz2?

[oxyde]

@Covenn

create a new raidz2 pool: I am liking this idea, after I create the new raidz2 pool with the new disks, would I first create the same matching datasets on the new pool before copying the data? I am also going to assume that Rsync would be the ideal way to replicate the data or would I use the replicate task.

The best way IMHO to transfer data in those case is the replication, no need to recreate anything, all is managed by the task having snapshot recursive and with the full file system replication check. Everything will be copied in the new pool, snapshots, permission, property, ecc ecc. ; rsync will not preserve those.

@Covenn

Stop all services: I am presently running portainer through the apps, and all of my docker stacks and containers are managed through portainer. Is it just a matter of stopping all stacks / containers and then stopping portainer through the apps interface. I’m going to also assume I stop all smb shares.

Yes, stop all stacks, stop portainer, do snapshot and replicate, this will prevent inconsistence on apps data.

@Covenn

Export old pool: this part seems self explanitory

yep nothing fancy, just not delete the configuration or you will lose all smb shares cronjob ecc

@Covenn

Rename the new pool to the previous pool: How is this achieved I was looking through the interface and it didn’t stand out as an option.

afaik this is not possible via gui, but is not difficult

HOWTO: Rename a ZFS pool

The basic process to rename a ZFS pool is to export it from the GUI, import it in the CLI with the new name, then export it again, and re-import it in the GUI. I find I normally want to do this after creating a new pool (with perhaps a different set of disks/layout), replicating my old pool to the new pool, and then I want to rename the new pool to the same as the old pool, and then all the shares work correctly, and its fairly transparent. Mostly. (tested with TrueNAS CORE 12U8-1. Works with …

@Covenn

I will be perfectly happy with the “six” 8TB disks of capacity at 48TB for the additional redundancy of having 2 drive failure tolerance.

i’m sorry but as @dan pointed, my previously calc on the storage was wrong.
You have to balance those things well with this “way”, because as is true that

• the process to transfer data is easier (especially if your backup not talk ZFS)
• you don’t need to destroy data on the old pool until you want create the new vdev (so you have all time to check after the replication if all is fine)

at the end you will lose a lot of space, 36tb vs 48tb (not 40).