Attempting to access /dev/disk/by-id/sda3, which is not a valid path to the disk

[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

Rockstor is looking for sda3 at the wrong path in /dev. You want /dev/disk/by-uuid/proper_uuid_here, not /dev/disk/by-id/sda3. The only thing in /dev/disk/by-id is the rather long link to my VMware Virtual IDE CDROM drive at …/…/sr0

Detailed step by step instructions to reproduce the problem

Installed the system in a VM (VMware Fusion 8.5.6), went to the web site and created my user. Got this error.

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/", line 41, in _handle_exception yield File "/opt/rockstor/src/rockstor/storageadmin/views/", line 377, in post return self._update_disk_state() File "/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/utils/", line 145, in inner return func(*args, **kwargs) File "/opt/rockstor/src/rockstor/storageadmin/views/", line 322, in _update_disk_state p.uuid = btrfs_uuid( File "/opt/rockstor/src/rockstor/fs/", line 1055, in btrfs_uuid [BTRFS, 'filesystem', 'show', '/dev/disk/by-id/%s' % disk]) File "/opt/rockstor/src/rockstor/system/", 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', '']

Edit: Typos, and solution should be too look for the proper uuid. sda3 is not the right label. It doesn’t exist anywhere in /dev/disk/by-*

@trenner Welcome to the Rockstor community.

Your reported issue is an existing inelegance in our dealing with unmet “Minimum system requirements” in our Quick start section:

All drives must have unique serial numbers (real drives do); not all VM systems default to this

Rockstor uses by-id device names which are generated by udev and for these names to be unique udev relies on serial numbers. If they don’t exist there is no ‘uniqueness’ to a drive and hence udev is unable to create the by-id links; bear in mind we, as a drives manager, have to track drives even if they have no partition table / fs (and consequently no uuid). Hence the minimum system requirement. Obviously the messaging need improving as, in the case of the system drive only, we simply fail out with what you have experienced; there are plans to improve this however. In the case of data drives a big red explanation is offered in the disk table. We just need to message better when it’s the system drive.

In the case of vmware I think what you are looking for to configure it in a compatible way with udev / Rockstor is:



Hope the helps.