[Please complete the below template with details of the problem reported on your Web-UI. Be as detailed as possible. Community members, including developers, shall try and help. Thanks for your time in reporting this issue! We recommend purchasing commercial support for expedited support directly from the developers.]
Brief description of the problem
[Add Storage-> scan = error message]
Detailed step by step instructions to reproduce the problem
[Add Storage-> scan = error message]
Web-UI screenshot
[Drag and drop the image here]
Error Traceback provided on the Web-UI
[ Traceback (most recent call last):
File "/opt/rockstor/src/rockstor/rest_framework_custom/generic_view.py", line 41, in _handle_exception
yield
File "/opt/rockstor/src/rockstor/storageadmin/views/disk.py", line 320, in post
return self._update_disk_state()
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 265, in _update_disk_state
p.uuid = btrfs_uuid(dob.name)
File "/opt/rockstor/src/rockstor/fs/btrfs.py", line 1008, in btrfs_uuid
[BTRFS, 'filesystem', 'show', '/dev/disk/by-id/%s' % disk])
File "/opt/rockstor/src/rockstor/system/osi.py", line 114, in run_command
raise CommandException(cmd, out, err, rc)
CommandException: Error running a command. cmd = /sbin/btrfs filesystem show /dev/disk/by-id/sda3. rc = 1. stdout = ['']. stderr = ['ERROR: not a valid btrfs filesystem: /dev/disk/by-id/sda3', '']
@bridgemarkinc Welcome to the Rockstor community forum.
This error is our current inelegance when faced with a system drive without a serial number, such as some VM systems have by default. Rockstor requires as a minimum specification that all drives have a unique serial number as we rely on by-id names which udev can’t itself create without this unique identifier. Were this to be a data drive then we have a nice message explaining the above only on the system drive we fail rather inelegantly with the message you see. There is now a pending pull request to address this in the docs as a prerequisite:
and there are pending changes that will hopefully allow us to display a more friendly and informative message when the same is encountered on the system drive; as we already do on data drives.
Hope that helps.
If you indicate the nature of your VM / hyper visor then there is mostly likely someone on the forum who can help with the required configuration.
I do have to apologize for this whole thread. It was not my intention to start a thread. First time install I get the error message and it provides me instructions to submit the info of the error. My first approach to any problem is to research out and find the solution. I know first hand that the problem most likely has happened before. My apologizes again and thank you Phillip for your swift response to the situation.
@bridgemarkinc No apologies necessary. The auto thread creation on submitting issue reports helps with support and seeing what’s not working as intended, and gets the eyes of forum members on issues quicker. But with repeat issues like these it can get frustrating, only this issue was a side effect of a large base design alteration and although irritating, is far better than the original problem the changes addressed. In time we should have this one refined into something a little more descriptive / helpful and in keeping than what currently happens.
Your welcome and hopefully your Rockstor experience going forward will be a little smoother.