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 377, 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.uuid = btrfs_uuid(dob.name)
File “/opt/rockstor/src/rockstor/fs/btrfs.py”, line 1055, in btrfs_uuid
[BTRFS, ‘filesystem’, ‘show’, ‘/dev/disk/by-id/%s’ % disk])
File “/opt/rockstor/src/rockstor/system/osi.py”, line 115, 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’, ‘’]
You might need to provide some more information on this.
- What were the most recent changes you made before this error started coming up?
- What is it that you’re trying to do?
- At what point does the message come up, and what steps do you do to replicate the issue?
At this point, it looks like the DB entry for one of your btrfs pools may be incorrect. Specifically, sda3 may have changed names.
Also, what is the output of:
btrfs fi show
@echoxalpha Welcome to the Rockstor community
and @Haioken thanks for the fine suggestions here.
This can happen when the system drive has no serial, such as when Rockstor is running within a VM with insufficient configuration re passing through / providing unique serial numbers for disks ie such as real disks have.
Serial numbers for devices is a pre-requisite for Rockstor ie from Quick start subsection Minimum system requirements we have:
“All drives must have unique serial numbers (real drives do); not all VM [*] systems default to this”
with the * referencing the following note for VMware:
“[*] For VMware ensure you have disk.EnableUUID=“true” in your .vmx file”
Hope that helps.