Last active
July 7, 2023 14:11
-
-
Save mailinglists35/65cf2f165f543243157c2aa573e75a49 to your computer and use it in GitHub Desktop.
recover veracrypt zfs pool after failed usb cable, without reboot
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
******************************************************************************** | |
WARNING THESE ARE MY PARTICULAR CASE NOTES MADE PUBLIC SO I CAN EASILY FIND THEM | |
DO NOT BLINDLY PASTE WITHOUT UNDERSTANDING WHAT DO THESE COMMANDS DO | |
******************************************************************************** | |
dmsetup table | grep veracrypt | |
veracrypt2: 0 3904923136 crypt aes-xts-plain64 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 256 8:34 256 | |
dmsetup reload veracrypt2 --table "0 3904923136 error" | |
dmsetup suspend --noflush veracrypt2 | |
dmsetup resume veracrypt2 | |
(?)zpool clear backup-usb | |
remove from veracrypt UI | |
echo "0 3904923136 zero" | dmsetup reload veracrypt2 | |
dmsetup suspend --noflush veracrypt2 | |
dmsetup resume veracrypt2 | |
dmsetup remove veracrypt2 | |
re-setup dm table from veracrypt UI | |
zpool clear backup-usb | |
scrub will start automatically | |
errors will be found | |
export pool | |
reimport | |
scrub again |
How do you force the zfs to use devmapper virtual device instead of real device?
when you import, you direct it to import from /dev/mapper
zpool import -d /dev/mapper
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
scrub twice to make the error status go away openzfs/zfs#9705 (comment)