Rebuilding pool hosting apps without loosing apps

Google wasnt my friend this time, in a nutshell ssd manufacturers define 1tb pretty liberally (pool already mixed capacity because of this) and the drive i bought got rejected for being too small.

So, what my plan is to replicate the whole pool onto my hdd array inside a dataset, destroy then rebuild the ssd pool, and after that replicate back. Will this work, as in if i point to tthe restored pool will TN Scale pick up the apps?

Yes, you can use the GUI to move the ā€œix-applicationsā€ dataset on any pool you want, as many times as you want. In your case, you could just create a pool on the smaller 1 TB drive, move the apps there, destroy the old pool and then extend the new pool with the larger 1 TB.

Too late :frowning: . One more ssd kicked the bucket (never buying verbatim again) in the same raidz1 that was already degraded. Luckily set up a replication task when i couldnt replace the 1st failed drive.
Rebbuilt the pool in a single vdev 8 drive raidz2 this (gave the same name as before) time then used replication to restore everything as it was on the old pool. Everything seems to be in order, even the VMs started without touching them after a reboot. But k3s is acting upā€¦

/EDIT
NVM, found the solution:

1 Like