Value too long for type character varying (128)

After installing Rockstor to a USB using VMware then transferring that to a PC that I want to use the software on I clicked add disk but it gives me this error. I can’t install it directly to the PC as it doesn’t give me the option to install rockstor and instead just CentOS which gives me errors.

Error Traceback provided on the Web-UI

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 316, in _update_disk_state
p.disk_set.add(dob)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/fields/related.py”, line 750, in add
obj.save()
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/base.py”, line 734, in save
force_update=force_update, update_fields=update_fields)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/base.py”, line 762, in save_base
updated = self._save_table(raw, cls, force_insert, force_update, using, update_fields)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/base.py”, line 846, in _save_table
result = self._do_insert(cls._base_manager, using, fields, update_pk, raw)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/base.py”, line 885, in _do_insert
using=using, raw=raw)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/manager.py”, line 127, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/query.py”, line 920, in _insert
return query.get_compiler(using=using).execute_sql(return_id)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/models/sql/compiler.py”, line 974, in execute_sql
cursor.execute(sql, params)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/utils.py”, line 64, in execute
return self.cursor.execute(sql, params)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/utils.py”, line 98, in exit
six.reraise(dj_exc_type, dj_exc_value, traceback)
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/db/backends/utils.py”, line 64, in execute
return self.cursor.execute(sql, params)
DataError: value too long for type character varying(128)

After doing some digging I did find another post, and I believe the USB is the culprit here. not sure though so I have provided the code line below. its around 146 characters long

total 0
drwxr-xr-x 2 root root 640 Jan 18 10:23 .
drwxr-xr-x 7 root root 140 Jan 18 10:23 …
lrwxrwxrwx 1 root root 9 Jan 18 10:23 ata-Hitachi_HCS5C2020ALA632_ML0230FA0A5KHD ->
…/…/sdb
lrwxrwxrwx 1 root root 10 Jan 18 10:23 ata-Hitachi_HCS5C2020ALA632_ML0230FA0A5KHD-par
t1 -> …/…/sdb1
lrwxrwxrwx 1 root root 9 Jan 18 10:23 ata-Hitachi_HCS5C2020ALA632_ML4230FA0L16HK ->
…/…/sde
lrwxrwxrwx 1 root root 10 Jan 18 10:23 ata-Hitachi_HCS5C2020ALA632_ML4230FA0L16HK-par
t1 -> …/…/sde1
lrwxrwxrwx 1 root root 9 Jan 18 10:23 ata-PNY_CS900_240GB_SSD_PNY43191910250108142 -

…/…/sda
lrwxrwxrwx 1 root root 10 Jan 18 10:23 ata-PNY_CS900_240GB_SSD_PNY43191910250108142-p
art1 -> …/…/sda1
lrwxrwxrwx 1 root root 9 Jan 18 10:23 ata-ST2000VM003-1CT164_W1H1VKCZ -> …/…/sdc
lrwxrwxrwx 1 root root 10 Jan 18 10:23 ata-ST2000VM003-1CT164_W1H1VKCZ-part1 -> …/…
/sdc1
lrwxrwxrwx 1 root root 9 Jan 18 10:23 ata-ST2000VM003-1ET164_W720V93G -> …/…/sdf
lrwxrwxrwx 1 root root 10 Jan 18 10:23 ata-ST2000VM003-1ET164_W720V93G-part1 -> …/…
/sdf1
lrwxrwxrwx 1 root root 9 Jan 18 10:23 ata-WDC_WD10EURX-83UY4Y0_WD-WCC4J0UK470R -> …
/…/sdd
lrwxrwxrwx 1 root root 10 Jan 18 10:23 ata-WDC_WD10EURX-83UY4Y0_WD-WCC4J0UK470R-part1
-> …/…/sdd1
lrwxrwxrwx 1 root root 10 Jan 18 10:23 ata-WDC_WD10EURX-83UY4Y0_WD-WCC4J0UK470R-part2
-> …/…/sdd2
lrwxrwxrwx 1 root root 9 Jan 18 10:23 usb-SanDisk_Ultra_0401f0b1adcd6d2516a9583a4607
d111c5f042220a7984885a0cc8c7e6614e02dab1000000000000000000000ecf2caaff9805188155810784
277d75-0:0 -> …/…/sdg
lrwxrwxrwx 1 root root 10 Jan 18 10:23 usb-SanDisk_Ultra_0401f0b1adcd6d2516a9583a4607
d111c5f042220a7984885a0cc8c7e6614e02dab1000000000000000000000ecf2caaff9805188155810784
277d75-0:0-part1 -> …/…/sdg1
lrwxrwxrwx 1 root root 10 Jan 18 10:23 usb-SanDisk_Ultra_0401f0b1adcd6d2516a9583a4607
d111c5f042220a7984885a0cc8c7e6614e02dab1000000000000000000000ecf2caaff9805188155810784
277d75-0:0-part2 -> …/…/sdg2
lrwxrwxrwx 1 root root 10 Jan 18 10:23 usb-SanDisk_Ultra_0401f0b1adcd6d2516a9583a4607
d111c5f042220a7984885a0cc8c7e6614e02dab1000000000000000000000ecf2caaff9805188155810784
277d75-0:0-part3 -> …/…/sdg3
lrwxrwxrwx 1 root root 9 Jan 18 10:23 wwn-0x5000c50069d5e4c5 -> …/…/sdc
lrwxrwxrwx 1 root root 10 Jan 18 10:23 wwn-0x5000c50069d5e4c5-part1 -> …/…/sdc1
lrwxrwxrwx 1 root root 9 Jan 18 10:23 wwn-0x5000c5008ff0b6cf -> …/…/sdf
lrwxrwxrwx 1 root root 10 Jan 18 10:23 wwn-0x5000c5008ff0b6cf-part1 -> …/…/sdf1
lrwxrwxrwx 1 root root 9 Jan 18 10:23 wwn-0x5000cca36ac4a099 -> …/…/sdb
lrwxrwxrwx 1 root root 10 Jan 18 10:23 wwn-0x5000cca36ac4a099-part1 -> …/…/sdb1
lrwxrwxrwx 1 root root 9 Jan 18 10:23 wwn-0x5000cca36ac83338 -> …/…/sde
lrwxrwxrwx 1 root root 10 Jan 18 10:23 wwn-0x5000cca36ac83338-part1 -> …/…/sde1
lrwxrwxrwx 1 root root 9 Jan 18 10:23 wwn-0x50014ee2b8f69c95 -> …/…/sdd
lrwxrwxrwx 1 root root 10 Jan 18 10:23 wwn-0x50014ee2b8f69c95-part1 -> …/…/sdd1
lrwxrwxrwx 1 root root 10 Jan 18 10:23 wwn-0x50014ee2b8f69c95-part2 -> …/…/sdd2
lrwxrwxrwx 1 root root 9 Jan 18 10:23 wwn-0x5f8db4c431908142 -> …/…/sda
lrwxrwxrwx 1 root root 10 Jan 18 10:23 wwn-0x5f8db4c431908142-part1 -> …/…/sda1

@Regan Hello again, and thanks for the report.

Re:

We have had the exact same report from forum member @Squeakz in the following forum thread:

and I opened the following issue as a result:

In the reported case the device was a usb-SanDisk_Ultra_Fit.

I purchased one back then for testing but ended up not getting the giant name variant as it goes.

I have added your report to that issue and hopefully we can get this database field extended via an update soon.

Could you possibly give an exact model number for this device as it would be good to know.

Thanks again for the report.

Hey!
The number should be SDCZ48-O32G

@Regan Thanks for the problematic SanDisk model number.

I’ve now added it to the issue.

Cheers.

1 Like

@Regan Hello again. Re:

Just a notification that as of 3.9.2-53 this issue is now resolved:

Hope that helps.

1 Like