From: janemba <cap.janemba@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] External HD don't want to be deciphered
Date: Tue, 05 May 2015 20:47:28 +0200 [thread overview]
Message-ID: <55491040.2090400@gmail.com> (raw)
In-Reply-To: <31863d9a3c317bd4943bcb16612a63ca.squirrel@ssl.verfeiert.org>
On 05/04/2015 08:59 PM, Sven Eschenberg wrote:
> On Mon, May 4, 2015 16:51, janemba wrote:
>> (Sorry I forgot the subject)
>>
>> On Mon, May 4, 2015 at 4:50 PM, janemba <cap.janemba@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I have an issue with LUKS. I have a new external hard drive with the
>>> following characteristics :
>>>
>>> Host scsi11: usb-storage
>>> Vendor: Seagate (2TB)
>>> Product: Expansion
>>> Serial Number: xxx
>>> Protocol: Transparent SCSI
>>> Transport: Bulk
>>> Quirks: SANE_SENSE
>>>
>>> Also I have cryptsetup install on my box with version 1.4.3 and kernel
>>> 3.14.5. I can't update cryptsetup on this box as I ciphered the hard
>>> drive
>>> with this version and I'm afraid to not be able to deciphered the hard
>>> drive if cryptsetup version change.
>>>
> On a short sidenote, you could still keep a copy of your current
> cryptsetup for safety or even compile a static build to keep on your
> 'desk' or some thumb drive just in case some issues arise with newer
> versions.
>
> Ragards
>
> -Sven
>
> P.S.: Aside from that you might want to fill in the details Arno asked for...
>
Ok thank you guys. I tried with a static version of cryptsetup and
everything worked fine now. So, I will update to the latest
version like Arno said but after a complete backup.
Thanks again
prev parent reply other threads:[~2015-05-05 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 14:51 [dm-crypt] External HD don't want to be deciphered janemba
2015-05-04 18:59 ` Sven Eschenberg
2015-05-05 18:47 ` janemba [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=55491040.2090400@gmail.com \
--to=cap.janemba@gmail.com \
--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