I have two zfs pools. I upgraded one of my array drives by moving the data from it onto the new drive and then removed the smaller drive because of limited case space. I used reset config to remove the gap in the UI lineup. After, my single drive zfs pool came back no issue. My mirrored two drive zfs pool says unmountable wrong or no file system. I used zpool import and status and it showed no issues. I am able to view and access my mirrored zfs pool in Shares with the contents still present. I tried zpool export and then unselected the mirrored pool in Main with the array offline and then started the array to remove it. Then stopped the array and tried to remount it as a pool device. Still the same result.

I read on another post that Docker or scripts can interfere with pool mounts because they grab the pool before unRAID can properly mount it. I turned off Docker and scripts to prepare. I have about an hour until my parity check finishes then I want to jump at this issue and correctly mount my mirrored two drive zfs pool. Any suggestions?

Where did I go wrong before?

diagnostics-20260410-0752.zip

Edited April 10Apr 10 by Chandelin
Confused by half of my post disappearing once I posted. Rewriting it.

Try this:

Make sure the pool is exported. If it's not exported with zpool export, then

on main click on the first device for that pool and then "remove pool"

back on main, create a new pool with the same name and number of slots

assign the pool device(s), leave the filesystem set to auto

start the array to import the pool, if it still fails, post new diags and the output from zpool import

You are describing as I did. I'll repeat to be sure and grab diagnostics. After the first fail I did import and status then export. I actually did the same to the mirrored pool and the single drive pool and got all is well replies. The single drive pool is running an older version of zfs I learned, which should not be bad because that pool mounted fine... correct? (Should I update that one?)

From what I read around the subject I can't see why one pool mounted and the other didn't. Both have Shares assigned. Actually the one that succeeded has my Docker app data so if Docker was causing issues with the mirrored pool and not it's host drive my mind would be blown. The difference is the failed mount is mirrored.

I've got half an hour until the parity finishes. Then it is crunch time.

To be clear this screenshot is from after the first failure to mount.

Edited April 10Apr 10 by Chandelin
clarity

1 hour ago, JorgeB said:

Try this:

Make sure the pool is exported. If it's not exported with zpool export, then

>>on main click on the first device for that pool and then "remove pool"<<

back on main, create a new pool with the same name and number of slots

assign the pool device(s), leave the filesystem set to auto

start the array to import the pool

Well that did it. Odd that using the CLI alone did not work the second try. To be sure, this time I used zpool export and the UI as you instructed and it worked on the import. With Docker and scripts not running to be extra sure.

It now shows up as expected in Main. Thank you.

Edited April 10Apr 10 by Chandelin
I swear I know how to type. Corrections.