Traceback (most recent call last):
File "/opt/rockstor/src/rockstor/rest_framework_custom/generic_view.py", line 41, in _handle_exception
File "/opt/rockstor/src/rockstor/storageadmin/views/disk.py", line 459, in post
File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/utils/decorators.py", line 145, in inner
return func(*args, **kwargs)
File "/opt/rockstor/src/rockstor/storageadmin/views/disk.py", line 322, in _update_disk_state
p_info = dev_pool_info[dev_name]
I couldn’t solve my problem by searching, so I hope for your help.
This is a strange one. It may help those here to diagnose what might have happened here by starting with the output of the following command:
ls -la /dev/disk/by-id/
And could you give some history as to how your system got into this state. I.e. has this install ever recognised the non system drives. Have you for instances installed any additional multi tools or the like.
I’m really not clear on what’s happened here.
You could try out our Rockstor 4 variant (Release Candidate 4) but it does have a broken AD currently. But otherwise seems to be at feature parity. It’s currently a DIY installer, no installer downloads untill we get this AD thing sorted. The instructions for creating your own installer for this new Build on openSUSE variant are here:
Are yes, that makes sense now. I seem to remember some combination of partition types that could cause this. Sorry I wasn’t able to pickup on this previously and thanks for sharing your findings / work around.