All of lore.kernel.org
 help / color / mirror / Atom feed
From: machiner <machiner@gmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] My sequence of failure
Date: Sat, 4 Sep 2010 08:11:29 -0400	[thread overview]
Message-ID: <20100904081129.625a599d@lapbox> (raw)

[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]


Hello,

I reinstalled Debian a few weeks ago (dselect).  Last night I plugged my backup drive
in that I may resume normal backup procedures.  In a fit of stupid, I probably lost
my backup data forever.  Here is what I did.

Upon plugging the USB drive in I was greeted with a small dialog box that informed
me that /dev/sdb1 was encrypted and that I needed to input the password.  I did.

Then...

1 - # cryptsetup luksOpen /dev/sdb1 backup
2 - # mkfs.ext3 /dev/mapper/backup
3 - # mount /dev/mapper/backup /mnt/backup

Of course when I went to look upon my existing backups the drive was empty.  Of
course I overwrote the file system.  I did a number of things wrong....Large
quantities of alcohol were involved.

I tried testdisk with varying failures.  Stuff was seen, ish, but it ended there. P
to list files aborted testdisk.  Ran it looking for Intel partitions and also for
'none'.

I see 3 instances of the drive when I run testdisk with no arguments.


Disk /dev/sdb - 320 GB / 298 GiB - WDC WD32 00BEVT-60ZCT0
Disk /dev/mapper/backup - 320 GB / 298 GiB
Disk /dev/dm-0 - 320 GB / 298 GiB


I looked around the mailing list and saw things like headers and salts and figured I
was doomed.  But I'm here anyway asking if there's anything I can do to attempt to
retrieve my existing backups.

Thanks.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2010-09-04 12:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-04 12:11 machiner [this message]
2010-09-04 12:24 ` [dm-crypt] My sequence of failure Rick Moritz
2010-09-04 14:05 ` Heinz Diehl
2010-09-04 22:50   ` Roscoe
2010-09-05  9:46     ` Heinz Diehl
2010-09-04 14:33 ` Arno Wagner

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=20100904081129.625a599d@lapbox \
    --to=machiner@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 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.