move from 7 Raidz2 HDD to 6 SSD raidz2 with SAS adapter change too

[vthinsel]

Hello !

My current setup is based on a supermicro mini ITX board with a 6Gb SAS adapter with 7 HDD. No issues with this setup. I use some k8s apps, some VMs too.
I had the opportunity to get nice 12gb/s SAS SSDs, which are a bit smaller than the HDD (3.8T vs 4T) so replacing the disks like I used to do to increase strorage will not work. As those are 16Gb, I also found a SAS3008-8i (my current SAS couldnt find the new SSDs anyway). I installed a new truenas with this SAS adapter, on an old supermicro board and started to happily replicate the HDD pool to this temp setup using the replication task. Now I have all the data transferred , what are the next steps ? I had this in mind :

- remove HDD / SAS from mini ITX
- install new SAS with SSD
- power-on and pray :)

As I had the brilliant idea to name the pool differently, is it likely to fail miserably ? Can the SSD pool be renamed ? Does TrueNas care about IDs instead of names ? Will VMs and apps come back "magically" ? (for renaming, looks like exporting/importing with the new name would work, but I wonder if TrueNAS will be happy about that)

Thanks !

Current pool:
root@freenas[~]# zpool status Pool01_7HDD pool: Pool01_7HDD state: ONLINE scan: scrub repaired 0B in 07:40:43 with 0 errors on Sun May 15 07:41:09 2022 config: NAME STATE READ WRITE CKSUM Pool01_7HDD ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 9c690d44-f237-11eb-ab7a-3cecef05c5f2 ONLINE 0 0 0 9c8ca9c5-f237-11eb-ab7a-3cecef05c5f2 ONLINE 0 0 0 9ca69977-f237-11eb-ab7a-3cecef05c5f2 ONLINE 0 0 0 9ceecd71-f237-11eb-ab7a-3cecef05c5f2 ONLINE 0 0 0 9ccc013f-f237-11eb-ab7a-3cecef05c5f2 ONLINE 0 0 0 9cb2fed2-f237-11eb-ab7a-3cecef05c5f2 ONLINE 0 0 0 9d3857e2-f237-11eb-ab7a-3cecef05c5f2 ONLINE 0 0 0 errors: No known data errors root@freenas[~]#

Target pool:
root@truenastmp[~]# zpool status Pool01_7SSD pool: Pool01_7SSD state: ONLINE config: NAME STATE READ WRITE CKSUM Pool01_7SSD ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 039bb25d-5281-474f-bc32-ad37bb10255e ONLINE 0 0 0 4020ee4b-d5ec-4591-8a0a-4f8f9991b478 ONLINE 0 0 0 431f8f59-d6bf-4d32-ac3d-b4f0f2dc15a9 ONLINE 0 0 0 c5673318-fb93-4f3d-a87d-0e1ed822b917 ONLINE 0 0 0 9a897428-51aa-44f3-80da-e68a1d8b27c6 ONLINE 0 0 0 980e82a8-0fa2-4439-9593-cf1b4a322080 ONLINE 0 0 0 errors: No known data errors root@truenastmp[~]#

 

[sretalla]

All the commands you should need are here:

Howto: migrate data from one pool to a bigger pool

There have been a lot of posts recently about how to move data from one pool to another. Usually it's because folks want to upgrade to a much larger pool and the drive-by-drive resilvering process will take too long. I've recently gone through this as well. Here are the steps that I followed...

www.truenas.com

 

[vthinsel]

Thanks ! So I was on a good track , great !

 

[vthinsel]

Finally, I kept the new Pool name but I'm facing some issues: the kubernetes apps are messed up: I cant change the pool because it complains about the IP:
Error: [EINVAL] kubernetes_update.node_ip: Please provide a valid IP address.
And I cant change the IP because it complains about the pool:
Error: [EINVAL] kubernetes_update.pool: Please provide a valid pool configured in the system.
Chicken/egg issue

Second issue is on NFS: I cant update the NFS shares. On the CIFS shares, I could retype the correct pool name, but on NFS shares it is not possible. Any ideas on how to do this ? Any files where this can be edited so /etc/exports gets created correctly (currently NFS service refuses to start, probably because of non existent path due to new pool name )?

Thanks

 

[sretalla]

Sounds like you didn't go back to the same pool name at the end... maybe that would be easier? (the linked thread also discussed how to do that)

 

[vthinsel]

Well, my naming convention was not enough future proof. Pool01_7HDD would now be Pool01_6SSD.
NFS issue is now sorted, everything is now properly remapped, VMs are fine.
Last point to address is the kubernetes pool and IP. I couldnt find in the thread ideas on this topic. Any clues on this ?

 

[sretalla]

OK, well the config DB is sqlite3 format, so you can start with that:

sqlite3
.open /data/freenas-v1.db
.tables (optional if you wanted to see all the available tables)
.dump services_kubernetes

Seems to me that the first little bit of the first line of that contains the pool name... maybe can be edited and re-imported...

have config and data backups and be ready to use them before messing with that stuff... here be demons.