Urgent! boot device died

@cbits68 Hello again.
Re:

That’s good to hear. Do please chip in here on the forum to help others with their hickups on this procedure as it’s one I’m super keen to enter into general Rockstor knowledge. So feel free to pop in on such questions as we very much depend on community support here on the forum.

Best to apply the restore after having imported the pool. As then the pool import (which also imports the shares) ensures the shares are there for the smb stuff to be applied to.

So pool import then config restore.

You shouldn’t have to do this if you have done as advised in wizards and docs and used specific shares for each Rock-on config. Rock-on restore is only a 4 thing so you won’t have them restored but as long as when you re-install them you pick the exact same shares (presumably named to help this) then the Rock-ons will pick-up where they left off.

You may also have an issue with docker getting confused with a pre-owned rock-ons-root. In which case, assuming you have used it for nothing else, it will only contain the docker images anyway which will be downloaded if not found by the Rock-on install process. So if it all goes pear shaped with Rock-on re-installs just create a fresh Rock-ons-root2 say and then it should be possible to re-install the Rock-ons into there but selecting each’s prior config/data shares so the resume their prior state.

Re CentOS base to ‘Built on openSUSE’ our code, outside managing the far more complex system subvol arrangement, is the same. But as always you should have backups refreshed before hand and take great care with drive selection during install, and ideally disconnect all but the intended system disk when doing the fresh install.

See the excellent post by our intrepid forum Admin and long time core developer @Flox on this same question:

And in the same thread an as ever poniente contribution by the prolific @GeoffA:

Hope that helps.

1 Like