Do I have to Reconfig the whole thing?

[Caffe Mocha]

I accidentally extended my slog drive to my pool without setting it as zil and raidz1 instead of RaidZ2.(I have no idea what's got into me). after some googling, I know it's better to delete the whole volume/pool and re-set it again.
correct me if I am wrong, I think recreate the volume and the datasets, using the names as before and everything should work just like before right? since I have left other things untouched.

 

[Mirfster]

Unfortunately, as far as I know you need to completely re-create the Pool. This will of course mean that you need to backup your data elsewhere then restore the data after you make the new Pool. Until that is done, your Pool is at risk, since if that one SSD dies then so will the entire Pool. :(

 

[danb35]

As @Mirfster said, to fix what you did to your pool, you'll need to destroy it and recreate it. But it sounds like you're asking about the rest of your system's configuration, and I'd say you're right--keep the same name on the replacement pool and datasets, and don't change any of the settings, and you should be fine. Make sure you assign the same dataset ownership as before.

I'd suggest taking a backup of your config file before destroying the pool, and re-uploading it after you've rebuilt it. FreeNAS is going to want to disable sharing services when you destroy the pool, and this will make sure that the services and shares are enabled as before.

 

[Stux]

As @Mirfster said, to fix what you did to your pool, you'll need to destroy it and recreate it. But it sounds like you're asking about the rest of your system's configuration, and I'd say you're right--keep the same name on the replacement pool and datasets, and don't change any of the settings, and you should be fine. Make sure you assign the same dataset ownership as before.

I'd suggest taking a backup of your config file before destroying the pool, and re-uploading it after you've rebuilt it. FreeNAS is going to want to disable sharing services when you destroy the pool, and this will make sure that the services and shares are enabled as before.

You can tell it not to disable shares. It recovers just fine.