Failed to import any pool on this device(3). Error: Error running a command. cmd

After reinstallation (ver.3.9), I cannot restore saved data on disks that previously formed a pool.

Brief description of the problem

        Traceback (most recent call last):

File “/opt/rockstor/src/rockstor/storageadmin/views/”, line 700, in _btrfs_disk_import
File “/opt/rockstor/src/rockstor/fs/”, line 252, in mount_root
File “/opt/rockstor/src/rockstor/system/”, line 115, in run_command
raise CommandException(cmd, out, err, rc)
CommandException: Error running a command. cmd = /bin/mount /dev/disk/by-label/Pool1 /mnt2/Pool1. rc = 32. stdout = [‘’]. stderr = [‘mount: wrong fs type, bad option, bad superblock on /dev/sdc,’, ’ missing codepage or helper program, or other error’, ‘’, ’ In some cases useful info is found in syslog - try’, ’ dmesg | tail or so.', ‘’]

Detailed step by step instructions to reproduce the problem

[write here]

Web-UI screenshot

[Drag and drop the image here]

Error Traceback provided on the Web-UI

[paste here]

@Wilkolak Hello again, and welcome the the Rockstor community forum.

Our 3.9.1 release was based on CentOS: which is now defunct. We last released a Rockstor based on CentOS

  • Last Testing Channel release (3.9.1-16) - November 2017
  • Last Stable channel released (3.9.2-57) - April 2020

Where as our current “Built on openSUSE” is currently maintained and testing is at Stable Release Candidate (RC3). So you definitely want to start our with our current installers. The Pool (btrfs volume) structure we use is unchanged and son our openSUSE based installers are just a likely (more so really) to be able to import these older pools as the old CentOS installer would be. There are some caveates there: mainly that btrfs was many years younger then!! This can lead to a regression where newer btrfs is more strict. But newer btrfs also have far more capabilities to recover data form pools that were previously available (in the CentOS kernels).

So try a new install using our year newer installers “Built on openSUSE”. You may have the same issue but we/others can then help using modern capabilities that were not available back-then.

Take a look at the following guide on our new instaler:

It is very different, much simpler, and a great deal faster. But it will wipe the target drive entirely: now chit-chat about partitions as we now dictate those for the system drive.

Hope that helps, and let us know if the install works or not there-after. It may be that your old Pool file-system is a little poorly/unwell: in which case the following doc section may help to get the initial import achieved:

Import unwell Pool: Disks — Rockstor documentation

Hope that helps.


Thank you very much, I got my pools back. Phew…
Everything works for now and let’s keep it that way.

@Wilkolak Thanks for letting us know you are now sorted.

In case it helps others in similar situations, what worked for you in the end? And what version of Rockstor did you end up using?

Always a worry when there are few fail-over options. But do keep in mind that there is nothing special about our pools: they are only generic btrfs volumes with usually whole drive (unpartitioned) members. We also only support a limited range of subvolume arrangements. And have some restrictions such as no repeat of subvolume name & pool label, system wide. As such they can be accessed/mounted equally well with any modern linux distribution: assuming some cli & btrfs familiarity.