Comment 1 for bug 1962061

Revision history for this message
geole0 (geole0) wrote :

Helle

Hello
Here is the access sequence to the encrypted partition from another O.S.

zpool import -N -R /ZFS rpool && sleep 10
if [ -e /dev/zvol/rpool/keystore ] ; then
    cryptsetup -v open /dev/zvol/rpool/keystore keystore-rpool && sleep 10
    mkdir -p /run/keystore/rpool
    mount -v /dev/mapper/keystore-rpool /run/keystore/rpool && sleep 10
fi

Here is an encrypted partition release sequence from another O.S. which prevents the boot of the encrypted partition
 shutdown or crash of O.S.

Another
zpool export rpool && shutdown

Antoher
umount -v /run/keystore/rpool && sleep 5
cryptsetup -v close /dev/mapper/keystore-rpool && sleep 5
zpool export rpool
shutdown

Here is the correct sequence of freeing encrypted partition from another O.S. which allows the boot of the encrypted partition.
But first you have to go through the recovery option.
There's probably a better solution.
umount -v /run/keystore/rpool && sleep 5
cryptsetup -v luksClose /dev/mapper/keystore-rpool && sleep 5
zpool export rpool && zpool list
shutdown