Error uppon initial setup

1

Hey,

Setting up a new system running in a ESXi 6.5 VM and getting the following when trying to complete the initial setup

Houston, we’ve had a problem.

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’, ‘’]

 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 377, 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 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’, ‘’]

Was able to login afterwards, but kinda a scary screen to see

2

@seriald Hello and welcome to the Rockstor community.

Agreed.

This problem is caused by the minimum system requirements of Rockstor not being met, ie that of each drive requiring a unique serial. We definitely need to improve our behave in such circumstance and in fact we do on all disk bar the system disk, bit red message against each explaining this serial thing, and we have an open issue to address this far less elegant behaviour when it concerns the system disk:

https://github.com/rockstor/rockstor-core/issues/1866

And from our Quick start docs section we have the Minimum system requirements:

“All drives must have unique serial numbers (real drives do); not all VM [*] systems default to this”

with a note on how this can be achieved in the config of VMware:

“[*] For VMware ensure you have disk.EnableUUID=“true” in your .vmx file”

But I’m not aware of an ESXi config to give the drives the serial numbers that udev requires to allocate our required /dev/disk/by-id names.

Hope that helps and do let us know if you find a way of getting ESXi to give it’s clients drives that look like real ones to udev, ie having unique serial numbers.