Refreshing rockons error

[freaktechnik (Martin Giger)]

First off, I’m on the latest developer release (3.9.2-57) running on openSUSE Leap (4.12.14-lp151.28.44-default). Since today updating the rockons list leads to an error message with all the currently installed rockons:

Errors occurred while processing updates for the following Rock-ons (A: ['Cannot add/remove volume definitions of the container (A) as it belongs to an installed Rock-on (A). Uninstall it first and try again.', 'Traceback (most recent call last):\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 111, in post\n self._create_update_meta(r, rockons[r])\n File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/utils/decorators.py", line 145, in inner\n return func(*args, **kwargs)\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 272, in _create_update_meta\n handle_exception(Exception(e_msg), self.request)\n File "/opt/rockstor/src/rockstor/storageadmin/util.py", line 47, in handle_exception\n trace=traceback.format_exc())\nRockStorAPIException: [\'Cannot add/remove volume definitions of the container (B) as it belongs to an installed Rock-on (B). Uninstall it first and try again.\', \'Traceback (most recent call last):\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 111, in post\\n self._create_update_meta(r, rockons[r])\\n File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/utils/decorators.py", line 145, in inner\\n return func(*args, **kwargs)\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 272, in _create_update_meta\\n handle_exception(Exception(e_msg), self.request)\\n File "/opt/rockstor/src/rockstor/storageadmin/util.py", line 47, in handle_exception\\n trace=traceback.format_exc())\\nRockStorAPIException: [\\\'Cannot add/remove volume definitions of the container (C) as it belongs to an installed Rock-on (C). Uninstall it first and try again.\\\', \\\'Traceback (most recent call last):\\\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 111, in post\\\\n self._create_update_meta(r, rockons[r])\\\\n File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/utils/decorators.py", line 145, in inner\\\\n return func(*args, **kwargs)\\\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 272, in _create_update_meta\\\\n handle_exception(Exception(e_msg), self.request)\\\\n File "/opt/rockstor/src/rockstor/storageadmin/util.py", line 47, in handle_exception\\\\n trace=traceback.format_exc())\\\\nRockStorAPIException: [\\\\\\\'Cannot add/remove volume definitions of the container (D) as it belongs to an installed Rock-on (D). Uninstall it first and try again.\\\\\\\', \\\\\\\'Traceback (most recent call last):\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 111, in post\\\\\\\\n self._create_update_meta(r, rockons[r])\\\\\\\\n File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/utils/decorators.py", line 145, in inner\\\\\\\\n return func(*args, **kwargs)\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 272, in _create_update_meta\\\\\\\\n handle_exception(Exception(e_msg), self.request)\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/util.py", line 47, in handle_exception\\\\\\\\n trace=traceback.format_exc())\\\\\\\\nRockStorAPIException: [\\\\\\\\\\\\\\\'Cannot add/remove volume definitions of the container (E) as it belongs to an installed Rock-on (E). Uninstall it first and try again.\\\\\\\\\\\\\\\', \\\\\\\\\\\\\\\'Traceback (most recent call last):\\\\\\\\\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 111, in post\\\\\\\\\\\\\\\\n self._create_update_meta(r, rockons[r])\\\\\\\\\\\\\\\\n File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/utils/decorators.py", line 145, in inner\\\\\\\\\\\\\\\\n return func(*args, **kwargs)\\\\\\\\\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 272, in _create_update_meta\\\\\\\\\\\\\\\\n handle_exception(Exception(e_msg), self.request)\\\\\\\\\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/util.py", line 47, in handle_exception\\\\\\\\\\\\\\\\n trace=traceback.format_exc())\\\\\\\\\\\\\\\\nRockStorAPIException: [\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'Cannot add/remove volume definitions of the container (F) as it belongs to an installed Rock-on (F). Uninstall it first and try again.\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\', \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'Traceback (most recent call last):\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 111, in post\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n self._create_update_meta(r, rockons[r])\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/utils/decorators.py", line 145, in inner\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n return func(*args, **kwargs)\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 272, in _create_update_meta\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n handle_exception(Exception(e_msg), self.request)\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/util.py", line 47, in handle_exception\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n trace=traceback.format_exc())\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\nRockStorAPIException: [\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'Cannot add/remove volume definitions of the container (G) as it belongs to an installed Rock-on (G). Uninstall it first and try again.\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\', \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'Traceback (most recent call last):\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 111, in post\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n self._create_update_meta(r, rockons[r])\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/utils/decorators.py", line 145, in inner\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n return func(*args, **kwargs)\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 272, in _create_update_meta\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n handle_exception(Exception(e_msg), self.request)\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/util.py", line 47, in handle_exception\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n trace=traceback.format_exc())\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\nRockStorAPIException: [\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'Cannot add/remove volume definitions of the container (H) as it belongs to an installed Rock-on (H). Uninstall it first and try again.\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\', \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'Traceback (most recent call last):\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 111, in post\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n self._create_update_meta(r, rockons[r])\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/utils/decorators.py", line 145, in inner\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n return func(*args, **kwargs)\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 272, in _create_update_meta\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n handle_exception(Exception(e_msg), self.request)\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/src/rockstor/storageadmin/util.py", line 47, in handle_exception\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n trace=traceback.format_exc())\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\nRockStorAPIException: [\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'Cannot add/remove volume definitions of the container (I) as it belongs to an installed Rock-on (I). Uninstall it first and try again.\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\', \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'Traceback (most recent call last):\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/eggs/gunicorn-19.7.1-py2.7.egg/gunicorn/workers/sync.py", line 68, in run_for_one\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n self.accept(listener)\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/opt/rockstor/eggs/gunicorn-19.7.1-py2.7.egg/gunicorn/workers/sync.py", line 27, in accept\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n client, addr = listener.accept()\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n File "/usr/lib64/python2.7/socket.py", line 206, in accept\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n sock, addr = self._sock.accept()\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\nerror: [Errno 11] Resource temporarily unavailable\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\']\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\']\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\']\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\']\\\\\\\\\\\\\\\\n\\\\\\\\\\\\\\\']\\\\\\\\n\\\\\\\']\\\\n\\\']\\n\']\n']).

I have one custom rockon running, however that was installed before the update. I haven’t added any rockons since updating.

EDIT: one possible reason could be that I had updated the hardware a bit today and one of the pools was missing a drive. I fixed the issue and everything started fine. I wonder if these errors are leftover from the invalid state?

[phillxnet (Philip Guyton)]

@freaktechnik Welcome to the Rockstor community.

Thanks for trying out the ‘Built on openSUSE’ testing channel.

Since today updating the rockons list leads to an error message with all the currently installed rockons:

The update button updates the available rock-ons. It does a fresh fetch from the web page. But your issue looks to be related to the following:

'Cannot add/remove volume definitions of the container © as it belongs to an installed Rock-on ©. Uninstall it first and try again.

Have you been experimenting with creating your own rockon as there is mention of a container named “C” there which is odd. And even stranger I’ve just noticed it seems to have a whole bunch of single letter containers in there. Same message for containers named A, B, C, D, E, F, G, H, I

I’ve just tried clicking the update button on rpm installs of the same version on all of Leap 15.1 Leap 15.2 beta, and Tumbleweed and was not able to produce this issue. All 3 updated the available list as expected.

Let us know if you are experimenting with a Rock-on definition as if so you may need to force remove a Rock-on ‘ghost’ via our emergency command line option of:

leap15-1:~ # /opt/rockstor/bin/delete-rockon 
Delete metadata, containers and images of a Rock-on
        Usage: /opt/rockstor/bin/delete-rockon <rockon name>

Pop in the display name and it tries to wipe all db records of a problematic Rock-on. Usually only needed when on is stuck with a Rock-on that is always installing or deleting and gets stuck in that state.

Let us know how you get on.

I have one custom rockon running, however that was installed before the update. I haven’t added any rockons since updating.

That is strange. I’d try removing both rock-ons, forcibly if required, and then re-installing them again. If you use the same shares as now then they should pick-up from where they left off.

EDIT: one possible reason could be that I had updated the hardware a bit today and one of the pools was missing a drive. I fixed the issue and everything started fine. I wonder if these errors are leftover from the invalid state?

That would have had to have been some pretty specific corruption. I’m just perplexed by the ‘alphabetic’ nature of this issue. Let us know what you find. Also that output look pretty strange with all those “”. I’d go for turning all rock-ons off and uninstall / re-install them and see if that pops things back. Also keep that emergency delete in mind. And as a last resort you can always create a new Rock-on-root and start completely fresh on the docker images side.

Assuming you were previously running 3.9.2-56 then the update to -57 was nothing more than some tests and a password treatment on config restore so nothing any where near the Rock-ons system.
Curious.

Hope that helps.

[freaktechnik (Martin Giger)]

The alphabetic nature is me removing the rockon names.

As it turns out this was related to the shares not being available for a time. I’ve uninstalled all rockons and am reinstalling them. The association for all the missing shares were lost in the config (the little config window that opens when you click on the wrench icon on installed rockons). So I had to reinstall them all to set the share association again. I guess the error is because the rockon configs expect a share mount, but none is configured.

Edit: shares that were in a pool that wasn’t broken survived unscaved.
Edit2: the very curious part is that the shares were still properly mounted to the docker containers again, once they were available. So it must be some de-sync of the config state.

[freaktechnik (Martin Giger)]

Thanks for trying out the ‘Built on openSUSE’ testing channel.

btw. that was the only thing that would run on my hardware, since it’s too new for centOS to even load…

[phillxnet (Philip Guyton)]

@freaktechnik Yes, it is good to be moving to a more modern kernel by default. And that gets all the better with the pending Leap 15.2 (currently beta). Plus we also have the Tumbleweed option if needs must, though that’s more for seeing whats on it’s way into future Leaps really. But I’m chuffed to have these options finnaly coming to fruition. It’s been quite a long road for us.

Glad your up and running again and do keep an eye on that Leap15.2 beta progress as that is planned as our next stable release base of choice for our ‘Built on openSUSE’ variants.

And thank again for your report.

Incidentally, you mentioned having a custom rockon; if it’s something others might be interested in then do consider doing a pull request to our rockon-registry repo:

https://github.com/rockstor/rockon-registry/pulls

Oh, and as this is a DIY NAS project, info on hardware folks are running is often of general interest. So do feel free to do a fresh post on your systems particulars. Pictures are a plus. Especially interesting given you had need of our newer offering. And encouraging for others in similar situations with newer hardware that would also like to try Rockstor out and end up in an apparent dead-end with our now ancient ISO (more on that soon hopefully).

As to your finding re "

@freaktechnik

So it must be some de-sync of the config state.

There is definitely ‘robustness’ work to be done in that area, but we must first focus on achieving a feature parity of sorts with out CenOS offering and sorting out our mounting technical debt before we tackle such things. Interesting though and now we have this report it’s something we can keep and eye on. Ideally, for it to transition to a well formed GitHub issue, we would need a reproducer. So if you do end up ‘re-visiting’ this issue then do take notes and we may then have a reproducer that can be used to develop and test any proposed fixes.

Cheers.

[freaktechnik (Martin Giger)]

Incidentally, you mentioned having a custom rockon; if it’s something others might be interested in then do consider doing a pull request to our rockon-registry repo:

I’m publishing the working rockon definitions at https://github.com/freaktechnik/rockons for now. The main reason I’m not proposing them for the main rockon repo is either stability or configurability. I exposed just the things I needed for my specific setup, plus I believe both would benefit from a custom setup handler to reduce repeating port numbers and such.

Oh, and as this is a DIY NAS project, info on hardware folks are running is often of general interest. So do feel free to do a fresh post on your systems particulars. Pictures are a plus. Especially interesting given you had need of our newer offering. And encouraging for others in similar situations with newer hardware that would also like to try Rockstor out and end up in an apparent dead-end with our now ancient ISO (more on that soon hopefully).

Will do.

So if you do end up ‘re-visiting’ this issue then do take notes and we may then have a reproducer that can be used to develop and test any proposed fixes.

So I’ve also noticed a second thing that got screwed up by the pool being broken: the samba shares that contained shares from the pool while still working are no longer visible in the UI.

I’m pretty sure at this point that the reproduction steps go something along the way of:

• make pool with multiple drives
• disconnect drive
• restart
• (things “break”)
• reconnect drive
• restart
• you’re in the invalid state now.