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 17:15:02 +0100 [thread overview]
Message-ID: <2381021.NG923GbCHz@lichtvoll.de> (raw)
In-Reply-To: <2316735.ElGaqSPkdT@lichtvoll.de>
Martin Steigerwald - 11.02.24, 15:28:52 CET:
> Martin Steigerwald - 11.02.24, 15:13:25 CET:
> > 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.
>
> It does not. I/O error that aborted rsync within the first 10 minutes.
>
> So it appears that external SSD on Linux is currently unusable. :(
>
> After at least some Sandisk Extreme Pro SSDs reportedly having all kinds
> of trouble – I have been lucky so far – it appears that Transcend SSD
> is not really a better choice. But let's see what comes out of a report
> to USB people.
On reporting this I got the notice that this could be fixed by the
following BCacheFS commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
fs/bcachefs?id=3e44f325f6f75078cdcd44cd337f517ba3650d05
I was aware of some stable fixes, even briefly read through them. But I
did not make the connection.
I will likely wait till 6.7.5 and retry then.
Best,
--
Martin
prev parent reply other threads:[~2024-02-11 16:15 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
2024-02-11 14:28 ` Martin Steigerwald
2024-02-11 16:15 ` Martin Steigerwald [this message]
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=2381021.NG923GbCHz@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.