All of lore.kernel.org
 help / color / mirror / Atom feed
From: tada <tada@riseup.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Another LUKS problem
Date: Sun, 10 Jun 2012 15:03:43 +0300	[thread overview]
Message-ID: <4FD48D1F.7030907@riseup.net> (raw)
In-Reply-To: <20120609110936.GA3519@tansi.org>

Well everything worked really good.
After restoration of partition table i got my LUKS header back which was
part of the good news. The other part was about knowing exact start and
end sectors of the LUKS partition. So i just moved end sector to the one
i knew and got back my LUKS partition.

On 06/09/2012 02:09 PM, Arno Wagner wrote:
> 
> I do hope you have a LUKS header backup, what you are doing
> comes with an extreme high risk of damaging the header or
> key-slot aream with the associated permanent data-loss. 
> 
> That said, the simplest thing would be to enlarge sdb1 to
> start at the same place and span the rest of the disk. 
> Everything else risks putting in a partition header into
> data, unless you know the sector-exact size the partition
> had before or only use primary partitions. The filesystem 
> inside the LUKS container will still be its original size 
> and prevent overwriting of any other data.
> 
> Arno
> 
> 
> On Sat, Jun 09, 2012 at 01:50:34AM -0700, tada@riseup.net wrote:
>> Hey guys.
>>
>> Straigh to the problem:
>> somehow partition table of my external harddrive got corrupted after last
>> reboot. I did managed to restore the whole table with testdisk, but
>> somehow the program was able to set up LUKS partition only to 1MB (i
>> suppose it was able to figure only the header of the partition). The
>> partition is at very beginning of the drive - starts at 63 and ends at
>> 2118 (giving 2048 total sectors for the header)
>>
>> So the first question - is the header proper sized? I mean can it get
>> corrupted by testdisk partition table writing procedure?
>>
>> And the other question - if i resize partition with fdisk (deleting and
>> recreating it with restoring LUKS header at the very beginning) will it
>> give me the possibility to access the data again? The thingy for now is
>> that whenever i try to luksOpen the 1MB partition it returns me "Requested
>> offset is beyond real size of device /dev/sdb1" which i suppose is good,
>> and only thing i need is resizing the partition.
>>
>> _______________________________________________
>> dm-crypt mailing list
>> dm-crypt@saout.de
>> http://www.saout.de/mailman/listinfo/dm-crypt
>>
> 

      reply	other threads:[~2012-06-10 12:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-09  8:50 [dm-crypt] Another LUKS problem tada
2012-06-09 11:09 ` Arno Wagner
2012-06-10 12:03   ` tada [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=4FD48D1F.7030907@riseup.net \
    --to=tada@riseup.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 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.