dm-crypt.saout.de archive mirror
 help / color / mirror / Atom feed
From: Kasperi <kasperikoti@posteo.net>
To: dm-crypt@saout.de
Subject: [dm-crypt] Help: problem with an encrypted USB drive
Date: Fri, 23 Apr 2021 16:35:00 +0000	[thread overview]
Message-ID: <7bad0bc2-fb8b-60bd-ed5d-68ba3e62b4c7@posteo.net> (raw)


[-- Attachment #1.1.1.1.1: Type: text/plain, Size: 1699 bytes --]

Hi,

First of all, I thank you for the great tool that you provide.

Now, I encountered a problem with an 512 GB USB flash drive that I 
bought recently and I wonder if it is related with the device itself or 
with the LUKS encryption that I put on it. I therefore seek your help. I 
have read the FAQ and searched the web for similar problems and I really 
do not know what I could do more to find a software fix to the problem.

There has been *no physical damage* to the drive and since I have used 
it very scarcely so far, I would be really surprised, if it had worn 
down already. It is a few months old and I only did occasional backups 
on it.

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. After running fsck 
unsuccessfully, the *USB drive stopped working altogether* and I cannot 
do anything with it. My systems (Linux Mint / Debian) do detect the USB 
drive itself (lsusb, lsblk), but the partition table seems to be gone 
now. I have tried to format the drive by different methods, but any 
intent gives errors and gets stuck. Disks, Gparted, mkusb, dd... but all 
to no avail.

Please note that I do not need to recover the data, as they were backups 
only. I want to format it and use the device again, in the case that 
there is not some inherent damage to it.

My question is: Can the LUKS encryption itself cause the described 
behaviour?

I can give you more details if there is still hope to find a software fix.

Kind regards,

Kasperi


[-- Attachment #1.1.1.1.2: Type: text/html, Size: 2088 bytes --]

[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2477 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]

[-- Attachment #2: Type: text/plain, Size: 147 bytes --]

_______________________________________________
dm-crypt mailing list -- dm-crypt@saout.de
To unsubscribe send an email to dm-crypt-leave@saout.de

             reply	other threads:[~2021-04-24 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 16:35 Kasperi [this message]
2021-04-24 18:40 ` [dm-crypt] Re: Help: problem with an encrypted USB drive Peter Grandi
2021-04-25 20:25   ` 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=7bad0bc2-fb8b-60bd-ed5d-68ba3e62b4c7@posteo.net \
    --to=kasperikoti@posteo.net \
    --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 NNTP newsgroup(s).