Failed to config a drive

Troubleshooting
1

Added a new drive, went to config the role and Houston appeared

        Traceback (most recent call last):

File “/opt/rockstor/src/rockstor/storageadmin/views/disk.py”, line 822, in _role_disk
return self._wipe(disk.id, request)
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 531, in _wipe
wipe_disk(disk_name)
File “/opt/rockstor/src/rockstor/system/osi.py”, line 791, in wipe_disk
return run_command([WIPEFS, ‘-a’, disk_byid_withpath])
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 = /usr/sbin/wipefs -a /dev/disk/by-id/cciss!c0d0. rc = 1. stdout = [’’]. stderr = [‘wipefs: error: /dev/disk/by-id/cciss!c0d0: probing initialization failed: No such file or directory’, ‘’]

2

@goingslowlyblind Welcome to the Rockstor community

From that dev name I would suggest that there is an issue with drive serial not being passed through some how, ie the /dev type name of cciss!c0d0 rather than a udev by-id type name. However it may be that we just done support this controller’s/driver’s device names. Ie we are expecting the regular scsi type names ie /dev/sda and their udev /dev/disk/by-id/ counterparts.

Does anyone else on the forum have experience with this dev name, I seem to remember these coming from a certain older card / diver and there being a newer alternative that presents the same hardware as regular scsi devices; where upon udev can do it’s magic and create the relevant by-id names that are a pre-requisite.

Hope that helps.