As @phillxnet mentioned in a recent post (in a different thread, see below), this unfortunately is a problem that has already been identified and planned on being addressed as soon as possible:
In this situation, the current solution I know is to turn-off your Rock-on service, and then remove your rockons_root share (the share you used to configure to Rock-on service), before reconfiguring it as it was before. The main drawback is that you would have to re-install the rock-on(s) you had installed before, but no data should be lost if you re-use the same shares as before for each rock-on.
Sorry for the short answer; I’m unfortunately quite short on time ![]()
Hope this helps,