Skip to content

cannot import dm-crypt pool after upgrade to 2.2.8 #17474

Answered by robn
aerusso asked this question in Q&A
Discussion options

You must be logged in to vote
    state: 2

That's POOL_STATE_DESTROYED, that is, you ran zpool destroy. I don't know if that's true, or if some script you use or something else did it, but that looks like a clean, successful destroy.

Fortunately, "destroying" a pool is actually just an export that flips a bit to say "ignore this pool when trying to detect a pool. dbgmsg suggests a clean and tidy import, and then an exit because of the "destroyed" state.

If that's all true, try zpool import -D, which is "consider deleted pools". If it shows your pool, and it's not a weird state (failed, imported elsewhere), you can try zpool import -f -D hydrapool to import it (which will also clear the "deleted" state). Don't try to …

Replies: 2 comments 5 replies

Comment options

You must be logged in to vote
3 replies
@robn
Comment options

robn Jun 20, 2025
Collaborator

@aerusso
Comment options

@robn
Comment options

robn Jun 20, 2025
Collaborator

Comment options

You must be logged in to vote
2 replies
@aerusso
Comment options

@robn
Comment options

robn Jun 20, 2025
Collaborator

Answer selected by aerusso
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants