[Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory

[geole0]

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1962061

Title:
  ZFS Key load error: Failed to open key material file: No such file or
  directory

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello
  The message is

  Key load error: Failed to open key material file: No such file or
  directory

  Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied
  filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied


  
  Hello
  I recently installed an encrypted ZFS 22.04 version.
  She boots well.
  I can do the updates and reboot except that now the reboot is impossible because of the message above.
  I suspect that access to the encryption keys has become impossible.

  The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file
  because the incident is systematic

  
  have a good day

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions