From: Arno Wagner <arno@wagner.name>
To: Milan Broz <gmazyland@gmail.com>
Cc: "Lars Francke" <lars.francke@gmail.com>,
"Michael Kjörling" <152cc69a347e@ewoof.net>,
cryptsetup@lists.linux.dev
Subject: Re: cryptsetup - No key available with passphrase
Date: Fri, 3 Mar 2023 18:42:53 +0100 [thread overview]
Message-ID: <20230303174253.GA24756@tansi.org> (raw)
In-Reply-To: <47da0423-7e8c-c059-c65c-fe6252b0e384@gmail.com>
On Fri, Mar 03, 2023 at 08:55:50 CET, Milan Broz wrote:
> But memory failure is just a recipe for disaster later...)
I agree. I usually run memtest86+ (there is a new version out)
for 2 days, just to be sure. Things have gotten better with
DDR5 (on-chip ECC), but you can still get failures in buses
or uncorrectable errors with low-quality RAM. Sometimes the
RAM is even completely fine, but the mainboard manufacturer
has screwed up the parameters that the BIOS uses.
Regards,
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2023-03-03 17:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 14:03 cryptsetup - No key available with passphrase Lars Francke
2023-03-02 15:01 ` Milan Broz
2023-03-02 16:23 ` Lars Francke
2023-03-02 16:40 ` Milan Broz
2023-03-02 20:34 ` Lars Francke
2023-03-02 21:46 ` Michael Kjörling
2023-03-02 22:12 ` Lars Francke
2023-03-03 7:55 ` Milan Broz
2023-03-03 10:17 ` Michael Kjörling
2023-03-03 17:42 ` Arno Wagner [this message]
2023-03-04 6:54 ` Lars Francke
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=20230303174253.GA24756@tansi.org \
--to=arno@wagner.name \
--cc=152cc69a347e@ewoof.net \
--cc=cryptsetup@lists.linux.dev \
--cc=gmazyland@gmail.com \
--cc=lars.francke@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox