WAY WAY back when, I called the RockOns share “RockDock”. It was then deleted along with the pool I had used.
Today I created a new pool on unused disks, created a new share called “RockOnsShare” and the system bugged out when I tried to “Enable Rockons”.
[20/Sep/2026 21:09:54] ERROR [storageadmin.util:45] Exception: Share name (RockDock) does not exist.
Traceback (most recent call last):
File "/opt/rockstor/src/rockstor/smart_manager/views/docker_service.py", line 48, in _validate_root
return Share.objects.get(name=root)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/rockstor/.venv/lib/python3.11/site-packages/django/db/models/manager.py", line 87, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/rockstor/.venv/lib/python3.11/site-packages/django/db/models/query.py", line 637, in get
raise self.model.DoesNotExist(
storageadmin.models.share.Share.DoesNotExist: Share matching query does not exist.
It seems to remember the OLD share name and ignored the NEW share name.
I changed the NEW share name to the OLD share name and everything works now.
How messed up am I?
LOL!
Did you remove the setting in the Rockon Configuration (under services) and then point it to another share? Or was it empty when you put the Rockon Share name in there (and then the error occurred when you tried to start the Rockon service)?
Hmmm, went looking around and finally as a last resort clicked on the wrench symbol and guess what? There is a little input thing that has the “RockDock” name in it!
Well, learned something new that I can’t remember seeing in the documentation…
SOOO, the answer is NOPE! I didn’t check that and like I was worried about, my booboo!
HOWEVER, I would suggest in the interest of simplicity that having to enter the pool name in only ONE place is the best method. Since we can’t create more than one RockOn pool at a time, there should be a change that prompts to erase any OLD pool before recreating a new pool and then overwrite the old name with the new name.
Let’s keep things simple and KISS the GUI as much as possible.
True. I think under normal circumstances, when you want to delete the RockonRoot manually, you will see a warning message, prompting to designate a different one in the Rockon service. But since you’ve lost the RockDock in a different way, that warning was never triggered. So, it would make sense to at least have a more meaningful error message in those situations that will clearly point to the misconfiguration of the Rockon Root setting.
You have such a polite way of saying I messed up somehow!!!
I admit, I am not a Linux guru, but a simple hardware dude… Sooo, I’m used to all the hardware tools available to me on Winderz and wish the same were on Linux…
Alas, everything is so weird on Linux that it confuses me sometimes… but, I consider that “FUN”!
I like your solution to support igor-nint folks like me!
