All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: RlndVt <RlndVt@protonmail.com>
Cc: "linux-bcachefs@vger.kernel.org" <linux-bcachefs@vger.kernel.org>
Subject: Re: Mounting a encrypted disk: Fatal error: Required key not available
Date: Sun, 11 Feb 2024 15:13:25 +0100	[thread overview]
Message-ID: <6018852.lOV4Wx5bFT@lichtvoll.de> (raw)
In-Reply-To: <afzrkbtBglFNpOW-YIx7L6WNqdsPlgWUp9EzVxMzGXdUrzUW0Np_eVwo7EkCWWIaSNTFsZUv7TYn6zeWxLH3qa_tuB-tCNhoQeGZbb5DG4c=@protonmail.com>

Hi Roland,

RlndVt - 26.01.24, 13:22:02 CET:
> On Thursday, 25 January 2024 at 23:54, Martin Steigerwald 
> <martin@lichtvoll.de> wrote:
> > Hi Roland.
> > 
> > RlndVt - 25.01.24, 21:10:25 CET:
> > > I'm having difficulties mounting a new array I've created:
> > > 
> > > # bcachefs mount /dev/sde /mnt/vault/
> > > ERROR - bcachefs_rust::cmd_mount: Fatal error: Required key not
> > > available
> > 
> > This has been discussed before. A possible work-around is:
> > 
> > Re: Error while unlocking encrypted BCacheFS: Required key not
> > available
> > 
> > Date: Tue, 16 Jan 2024 11:59:08 -0600
> > 
> > https://lore.kernel.org/linux-bcachefs/
> > CACmrr9gQeXccyS9ZRiR2KnTKnA6EVBCVz_YWcDC3p1mbGqgMSg@mail.gmail.com/
> > 
> > I did not yet take time to test it, but I think for George it worked.
[…]
> Thanks; from the #bcache IRC I got the advice to try unlocking with the
> `-k session` option, which worked for me.

It did not work for me. I tried

bcachefs unlock -k session /dev/sda1

but could not mount it:

error requesting encryption key: ENOKEY

The sequence

bcachefs unlock /dev/sda1

keyctl link @u @s

does work. The "keyctl" command is from the mail I linked above.

Now on to copying 1,4 TiB of data once again as Transcend XS2000 4 TB 
external SSD does not seem to like UAS. Lots of timeouts and I/O errors 
after a certain time. BCacheFS told a lot of interesting stuff to kernel 
log, but that is to be expected on timeouts and write errors. BCacheFS is 
not to blame for that.

Thus I recreated the file system and start from scratch after adding the 
following quirk:

% cat /etc/modprobe.d/disable-uas.conf
# Does not work with external SSD Transcend XS2000 4TB
options usb-storage quirks=0951:176b:u

I hope it works stable with usb-storage only instead of uas.

Will provide bug report to USB people about that.

Best,
-- 
Martin



  reply	other threads:[~2024-02-11 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 20:10 Mounting a encrypted disk: Fatal error: Required key not available RlndVt
2024-01-25 22:54 ` Martin Steigerwald
2024-01-26 12:22   ` RlndVt
2024-02-11 14:13     ` Martin Steigerwald [this message]
2024-02-11 14:28       ` Martin Steigerwald
2024-02-11 16:15         ` Martin Steigerwald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6018852.lOV4Wx5bFT@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=RlndVt@protonmail.com \
    --cc=linux-bcachefs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.