@iain0404 Re:
Im still not sure what’s going on here I’m afraid. So as a potentially over-the-top procedure to hopefully get you up and running again, now you are on the older docker to rule out that know issue, you could try re-doing your rock-on-root setup. This has been known to resolve (work around) some tricky failures. Essentially you disable the rock-ons service (off already for you anyway for unknown reasons) and setup a new rock-on-root subvol by a different name to your existing one:
https://rockstor.com/docs/docker-based-rock-ons/overview.html#initial-rock-ons-setup
Then select this new ‘clean’ Rock-ons-root’ for the Rock-ons system via the Rock-ons spanner icon and thereafter be able to re-enable the Rock-ons service. This should give you a new start and if you have done as indicated in your prior Rock-ons setups and used dedicated config & data subvols for each rock-on, re-installing each rock-on should put that rock-ons exactly back where it was config & data wise.
If you still have dangling Rock-ons from the prior Rock-ons root you can use the instructions here:
referenced in the other thread I mentioned re the docker downgrade thing, to remove these ghost entries in the db before re-installing that rock-on.
The prior Rock-ons root can then be deleted, assuming you didn’t use it for any of the Rock-ons config or data store (highly un-recommended) previously.
This is a brute-force and obtuse method but if it gets you up and running again then great.
Hope that helps and I’m afraid this is all I can think of currently.