Problem on Install: not enough values to unpack (expected 2, got 1)

Brief description of the problem

Issue while installation. Justed installed rockstor Rockstor-Leap15.6-generic.x86_64-5.0.9-0.install.iso image on USB flash (Gen 3.2) and after submitting admin credentials it fails. No any errors while installation, or something. Interesting, that Web-UI is still working fine. The problem occurs again, when I’m trying to scan disks. I think, problem was, that one of disks has previously been formatted with Synology FS, but I shreded it after, and have two clean drives (as it said in Pre-Install). And the problem Remains

Detailed step by step instructions to reproduce the problem

  1. Write image with Rufus DD with instructions
  2. Install to Flash USB drive
  3. Enter Web-UI, and set admin credentials

Web-UI screenshot

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 418, in post return self._update_disk_state() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/contextlib.py", line 81, in inner return func(*args, **kwds) ^^^^^^^^^^^^^^^^^^^ File "/opt/rockstor/src/rockstor/storageadmin/views/disk.py", line 115, in _update_disk_state attached_disks = scan_disks(MIN_DISK_SIZE) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/rockstor/src/rockstor/system/osi.py", line 330, in scan_disks blk_dev_properties: dict = { ^ File "/opt/rockstor/src/rockstor/system/osi.py", line 336, in for key, value in ( ^^^^^^^^^^ ValueError: not enough values to unpack (expected 2, got 1)

I think, this might be a similar issue, that was discovered some shortly after the 5.0.9 test release. What disk brand/type are you using?

1 Like

Yes. I’ve seen this post. And think this is very similiar. 'Cause I’m also installin on USB of unknown vendor (I’ve forgotten :`) But, after I’ve tried workaround, system became to hard rebooting on load ((
I’ll try to reinstall. An write after

1 Like

@gkonoplya Just wanted to chip in on:

There should be no work-around required as this is believed to be fixed as of our 5.0.11-0 release:

https://forum.rockstor.com/t/v5-0-testing-channel-changelog/8898/21

As per @Hooverdan provided link. We are in late testing phase currently so that channel currently contains our Stable Release candidate rpms: currently 5.0.14-0 (RC9). But be sure to switch back to Stable, or avoid applying testing channel updates once we have reached our final testing rpm in the current RC / late-testing channel phase. We plan to rebuild all installers once we have our first Stable rpm out as we near the end of our current testing phase.

Hope that helps.

1 Like

Yes. After reinstall, I’ve tried to replace my old flash with kingston Datatraveller Exodia M 64 GB, and updates to 5.0.14 immediately after install. Don’t know what helped, flash stick change, or update, but now everything works well (Maybe both :sweat_smile:). Thank you all!

3 Likes

@gkonoplya Thanks for the update, and good to hear your up-and-running again, via what-ever side-step or fix.

For some more context, we also have a fix in-coming of this type by @cellisten who found and fixed a leading space issue, where as our prior fix in this area was a sensitivity to trailing spaces!! My apologies for not mentioning this previously, but 5.0.15-0 (next testing release) should contain @cellisten fix detailed here:

Hopefully there-after we should be sorted on this front. We had a major re-work to return that whole code area to something way more maintainable, modern, and simpler; and inevitably introduced these space sensitivities. But there has now been a few eyes on this code so I’m hopeful we are ready for our next Stable release rpm, of which 5.0.15-0 is to be RC10 (Stable Release Candidate 10).

Hope that helps, at least with some development context.

2 Likes

@gkonoplya Just a quick notification re:

5.0.15-0 is now available, and does in-deed contain @cellisten follow-up fix to my-own re, in this case leading spaces in lsblk values. Bit by bit.

Hope that helps.

2 Likes