ERROR from disk name /dev/disk/by-id/cciss!c0d1

[kostet (konstantin)]

Good day. need help.

I can not create a pool because of the disk name is not specified correctly. the name is “!”

I do not have a virtual system

Error running a command. cmd = /sbin/mkfs.btrfs -f -d single -m dup -L VMWARE /dev/disk/by-id/cciss!c0d1. rc = 1. stdout = [‘btrfs-progs v4.12’, ‘See http://btrfs.wiki.kernel.org for more information.’, ‘’, ‘’]. stderr = [‘ERROR: failed to check size for /dev/disk/by-id/cciss!c0d1: No such file or directory’, ‘’]

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/pool.py”, line 315, in post
add_pool(p, dnames)
File “/opt/rockstor/src/rockstor/fs/btrfs.py”, line 61, in add_pool
out, err, rc = run_command(cmd, log=True)
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/mkfs.btrfs -f -d single -m dup -L VMWARE /dev/disk/by-id/cciss!c0d1. rc = 1. stdout = [‘btrfs-progs v4.12’, ‘See http://btrfs.wiki.kernel.org for more information.’, ‘’, ‘’]. stderr = [‘ERROR: failed to check size for /dev/disk/by-id/cciss!c0d1: No such file or directory’, ‘’]

[root@rockstor views]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
cciss!c0d1 104:16 0 2.5T 0 disk
cciss!c0d0 104:0 0 558.9G 0 disk
├─cciss!c0d0p3 104:3 0 554.5G 0 part
├─cciss!c0d0p1 104:1 0 500M 0 part /boot
└─cciss!c0d0p2 104:2 0 3.9G 0 part
[root@rockstor views]#

[root@rockstor by-id]# blkid
/dev/cciss/c0d0p1: UUID=“71c579e3-58cb-4dfe-be34-9f729de838cd” TYPE=“ext4”
/dev/cciss/c0d0p2: UUID=“63acee2e-2d82-4fa7-aa04-2d84413180ff” TYPE=“swap”
/dev/cciss/c0d0p3: LABEL=“rockstor_rockstor” UUID=“3896a690-a605-428a-ade3-5a731d2d8c29” UUID_SUB=“dadae8dc-24a4-49aa-a744-07853d43bdf6” TYPE=“btrfs”
/dev/cciss/c0d1: LABEL=“VMWARE” UUID=“785792b8-9298-4590-92f7-c57307c3d536” UUID_SUB=“c4f989e8-cce2-40f6-bec1-dc1a345ae228” TYPE=“btrfs”
/dev/cciss/c0d0: PTTYPE=“dos”
[root@rockstor by-id]#

Solved this problem.

Made a clean installation and updated lsblk to version 2.29
I have another error now.
no discs.

when I press ressan crashes

        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 342, in _update_disk_state
if (re.match(‘fake-serial-’, do.serial) is not None) or (
File “/usr/lib64/python2.7/re.py”, line 137, in match
return _compile(pattern, flags).match(string)
TypeError: expected string or buffer

[root@rockstor ~]# lsblk --nodeps -o name,serial
NAME SERIAL
cciss/c0d0 600508b100105439535a32305048000b
cciss/c0d1 600508b100105439535a32305048000a
[root@rockstor ~]#

[phillxnet (Philip Guyton)]

@kostet Welcome to the Rockstor community.

I think the key problem here is that Rockstor is just not able to deal with these device names. I suspect and I’m pretty sure there is an alternative kernel driver that presents these raid array drives as more generic /dev/sda type names. This has come up some time ago and I think that was way around it then. If you look to alternative drivers for this disk controller it should become apparent. I think the general approach is that you pass kernel parameters to favour the kernel driver that presents more generically. That way udev etc can give us proper by-id names and serials hopefully. Rockstor depends on udev and udev depends on drives having proper serials. We also don’t account for these names in particular. That my guess currently.

If you could report the system and it’s particular array controller and also look to the alternative kernel drivers for it I think you should be heading in the right direction.

also a full details listing of the by-id directory would help:

ls -la /dev/disk/by-id

as then we can see what links to what.
But I suspect you just need to transition, if possible, to an alternate driver so that these drives are presented in a more scsi standard way.

It may not be relevant but your could take a look at the following post:

Install on HP DL360 G5 fails to detect hardware raid [solved]

@suman that’s a nice trick. But this looks more like not having / loading a driver for the main drive controller (ie in initrd), @Bearbonez indicated that the USB was the only target visible; and those drive names from the omv are for the raid controller. @Bearbonez, we have another forum thread that unfortunately has very little info in it but I noticed that their machine, a Dell 2950 is of a similar class, do you know if it has the same type of raid controller: Rockstor installtion on a dell…

which relates to HP Smart Array driver issues, and in turn links to a site that should establish if you are able to use this alternative hspa driver.

May be off the mark but hopefully the above thread / suggestion should help.

Nice find on the blkid update by the way but we do dev name parsing and although you seem to now have device serials the problem is probably in the dev name parsing so you are most likely better off taking the alternative driver approach.

Let us know how you get on and remember to past your hardware specifics in here as others can then chip in with more suggestions.