From: pg@dmcrypt.list.sabi.co.UK (Peter Grandi)
To: list Linux dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] Re: Help: problem with an encrypted USB drive
Date: Sat, 24 Apr 2021 20:40:09 +0200 [thread overview]
Message-ID: <24708.26121.660646.671275@cyme.ty.sabi.co.uk> (raw)
In-Reply-To: <7bad0bc2-fb8b-60bd-ed5d-68ba3e62b4c7@posteo.net>
> First, the USB drive started to change its permissions to
> *write protected* when I was doing file transfers. Then, I run
> the system utility tool fsck to check and fix the filesystem
> as I suspected that errors therein might cause the behaviour.
That is rather vague and not very useful.
> After running fsck unsuccessfully, the *USB drive stopped
> working altogether*
Most likely explanatuions: it is either defective or it has a
fake size. There are a lot of fake flash drives.
> My question is: Can the LUKS encryption itself cause the
> described behaviour?
No.
_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de
next prev parent reply other threads:[~2021-04-24 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 16:35 [dm-crypt] Help: problem with an encrypted USB drive Kasperi
2021-04-24 18:40 ` Peter Grandi [this message]
2021-04-25 20:25 ` [dm-crypt] " Arno Wagner
2021-04-24 21:13 ` Carlos E. R.
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=24708.26121.660646.671275@cyme.ty.sabi.co.uk \
--to=pg@dmcrypt.list.sabi.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).