From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Anyone know why I can't access my volumes?
Date: Thu, 24 Oct 2019 14:34:05 +0200 [thread overview]
Message-ID: <20191024123404.GC25380@tansi.org> (raw)
In-Reply-To: <09a50a64-15f0-4d3c-1c8a-b60f53f97872@gmx.net>
On Thu, Oct 24, 2019 at 09:26:11 CEST, Carl-Daniel Hailfinger wrote:
[...]
> Can you try booting with the old installed kernel and initrd? Usually
> those are kept for some time after an upgrade.
You may also be able to get them from an archive. Most distros keep
older versions arpound for a while.
> Another thing I had to debug recently for a colleague was a failing
> flash medium. There were no read errors, but single bits of the data had
> flipped.
I had that as well on an USB-stick. An exceptionally bad design
that obviously did without the checksums that all well-designed
storage has.
> A unreported bit flip affecting the keyslots would be
> catastrophic AFAICS.
A single bit will kill the keyslot. If you know it is a single bit
only, you can try with all bits flipped (around 1M tries taking
around 2 weeks with 1 sec per try, i.e. all other keyslosts disabled),
but if it is two bits, you are already pretty much screwed.
> That said, bitflips affecting only the keyslots and
> nothing else would be a strange beast unless this is a really crappy
> SSD. How often do you reboot during normal operation?
It could be a very small number of bits affected. Also, bit-flips
in documents and even software often go unnoticed for a while.
That is why you should allways do a full compare in backups.
I found weak RAM bits, defective HDD connectors, etc. that way
in the past.
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:[~2019-10-24 12:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 21:53 [dm-crypt] Anyone know why I can't access my volumes? Philipp Rösch
2019-10-21 7:50 ` Michael Kjörling
2019-10-21 14:33 ` Philipp Rösch
2019-10-21 14:50 ` Arno Wagner
2019-10-21 14:56 ` Philipp Rösch
2019-10-24 7:26 ` Carl-Daniel Hailfinger
2019-10-24 12:34 ` Arno Wagner [this message]
2019-10-24 19:35 ` Philipp Rösch
2019-12-10 16:34 ` Philipp Rösch
2019-12-10 17:42 ` Chris Murphy
2019-12-10 20:00 ` Michael Kjörling
2019-12-10 21:18 ` Chris Murphy
2019-12-10 21:51 ` Arno Wagner
-- strict thread matches above, loose matches on Subject: below --
2019-10-21 18:16 Arno Wagner
2019-10-21 18:23 ` Philipp Rösch
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=20191024123404.GC25380@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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.