@kysdaddy Hello again.
Quoting from your other thread:
Might it be best to edit his thread so as to avoid suggestions that are only relevant if you had only one system working:
And given both systems are currently working, the simplest option may well be to just switch all drives, including the system drive, so that each system drive stays with it’s configured pool drive set. There are potential caveats here, ie on a re-install of one system it would pickup the appliance id of the motherboard it then found itself on: and for mechanisms such as replication, you would then be required to re-install the other machine so that it, in turn, picked up it’s appliance id from the former machines motherboard: so that could get tricky.
Just a though as this may suit your requirements. The main complexity as you surmised is the Rock-ons root share as we don’t currently transition rock-on configuration via the Configuration Backup and Restore mechanism; which necessitates that on a re-install the rock-on root share is best wiped and a fresh rock-on (docker) setup done, but this rock-on / docker re-setup can of course inherit you prior config and data shares so they should all pickup where they left off. Assuming no rock-on config or data shares were not the system drive that is.
It is generally not advised that you put any data, ie rock-on config or data, shares on the system drive. But it is less risky putting your rock-ons root share on the system drive as it contains nothing that can’t be re-established via rock-ons re-install. Where as your config and data rock-on shares, if placed on a system disk, will be subject to loss if you ever have to re-install.
Hope that answers at least part of your question. Also note that if you have a spare device you can always try a test config backup, download that config to your client machine. Disconnect your functional system disk, and re-install on the spare disk and attempt a config restore. If the machine you are re-installing on is already subscribed to the stable channel they you just have to re-enter the appropriate activation code issued for that machine (motherboard). This gives you the option to at least try a re-install, which ultimately is a good thing to be comfortable with anyway.
And always remember that there really is no substitute to disconnecting all data drives during a re-install as it is then impossible for a bug or human error there after to write to those drive. The Reinstalling Rockstor howto may be of interest here.
Hope that helps and apologies if I’ve wandered from the desired topic on this one.