Error scanning disks

1

I am testing Rockstor using 5 x NVME on an N915 board. 4x NVME were previously in a BTRFS pool on unraid and unformatted. I am unable to see the disks when scanning and receive the following error

            Traceback (most recent call last):
  File "/opt/rockstor/src/rockstor/rest_framework_custom/generic_view.py", line 40, in _handle_exception
    yield
  File "/opt/rockstor/src/rockstor/storageadmin/views/disk.py", line 417, 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 212, in _update_disk_state
    pool_info = dev_pool_info[dev_name]
                ~~~~~~~~~~~~~^^^^^^^^^^
KeyError: '/dev/nvme1n1'
2

@joewalch Welcome to the Rockstor community forum.

Re:

Could you clarify this? For a device to be a btrfs pool member, it has to be formatted. That is what makes it a member of that pool. Did you mean unpopulated data wise?

The output from the following command, run as the root user, should help with what btrfs sees of your current device set:

btrfs fi show

Keep in mind that Rockstor defaults to using whole disk btrfs, we can manage in-partition btrfs; more normally used on other legacy NAS setups. But whole disk cuts out an whole swath of complexity. If your devices were previously in-partition btrfs then each will have to have a re-direction role added accordingly. But if there is no data recovery concern here - then likely better to wipe each disk and go the Rockstor native whole disk route.

Note also that many legacy NAS setups also use LVM - we have no compatibility with this as it is yet more complexity layers and can (if miss configured) undermine the data integrity maintained by btrfs itself. Btrfs being not only a filesystem but also a device management layer (the btrfs raid bit).

Could you indicate the version of Rockstor you are using here?

Incidentally, I wiped your prior (almost duplicate) post that was also in the forum queue as this one seemed to have more info.

Hope the helps, at least with getting this discussion underway.

1 Like