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
Helle
Hello
Here is the access sequence to the encrypted partition from another O.S.
zpool import -N -R /ZFS rpool && sleep 10 rpool/keystore ] ; then rpool/keystore keystore-rpool && sleep 10 keystore- rpool /run/keystore/rpool && sleep 10
if [ -e /dev/zvol/
cryptsetup -v open /dev/zvol/
mkdir -p /run/keystore/rpool
mount -v /dev/mapper/
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 keystore- rpool && sleep 5
umount -v /run/keystore/rpool && sleep 5
cryptsetup -v close /dev/mapper/
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. keystore- rpool && sleep 5
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/
zpool export rpool && zpool list
shutdown