ZFS Cockpit Manager - Error creating Pools/Status Errors

I’ve been trying to use the ZFS Cockpit plugin but I’m running into issues when creating pools using my NVMe drives, or when performing actions such as “Export ZFS Pool” and “Import ZFS Pool.” Furthermore, the “Replication Status” for all my ZFS pools seems to show “Error.”

When I use the terminal and execute the command to check status, no issues reported:

Furthermore, I’m able to use the Terminal to make changes to the Pools and it works. I’m using the standard ‘45drives’ user to interact with ZFS cockpit. Not sure if this is a permissions error related thing?

All drives seem to be healthy:

After you set up a replication task, you will need to restart the service called ZnapZend. This will then see the configured tasks for replication and start doing them.

As for the commands in the UI, I would suggest pressing the elevated access button on the top of the screen and then trying again. this will make sure you are running the commands as a sudo user.

Hmm, seems like I’m already using elevated access in the UI (Logged into the 45Drives account):

ZnapZend was not installed. I installed the service manually, but not sure how it should be configured? Looking at the SystemCTL Status, the service immediately enters a degraded mode, exiting with error 255:

The service will only go healthy if there is a replication task configured

When you say the 45Drives user you are not using root so you will still need to press the administrative button on the top to run commands as root

If I click the “Administrative Access” button on top, it asks if I want to switch to “Limited Access.” When I say the 45drives user, I’m referring to the default user that Rocky Linux comes pre-configured with out of the box (root and 45drives are the two accounts provisioned by default).

Is your system up to date and on the latest kernel version? Sometimes if you do not reboot after an update you will get newer packages for a new kernel;l but if you do not reboot you will not be using that new kernel.