From: blobfish <blobfish@gmx.com>
To: cryptsetup@lists.linux.dev
Subject: Re: Looking for confirmation as I enter the acceptance stage.
Date: Wed, 26 Jul 2023 11:38:00 -0400 [thread overview]
Message-ID: <4863669.GXAFRqVoOG@laptop> (raw)
In-Reply-To: <a543a204-c0c7-4936-8eb0-38fd3ac825b9@home.arpa>
On Monday, July 24, 2023 12:03:13 PM EDT Michael Kjörling wrote:
> $ sudo dd if=/dev/sdb1 skip=126974 bs=256 count=1M of=sdb1.head.shift
>
> $ sudo cryptsetup luksDump ./sdb1.head.shift
>
> $ sudo file ./sdb1.head.shift
>
> Let's see what that gets you before we write this off as unfixable.
>
> For comparison, here's what I get when I do something very similar
> (using the same offsets) on what you have sent:
>
Finally finished the backup. Thanks for the ddrescue tip. Nice tool! I followed
your procedure from above and got the exact same output as you did from the
test data. Further I did:
sudo cryptsetup luksOpen sdb1.head.shift mapped1
I was prompted for passphrase and entered it.
command finished without error.
new path at /dev/mapper/mapped1
I am guessing that is a pretty good sign?
next prev parent reply other threads:[~2023-07-26 15:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 22:40 Looking for confirmation as I enter the acceptance stage blobfish
2023-07-23 23:04 ` Michael Kjörling
2023-07-24 0:00 ` blobfish
2023-07-24 16:03 ` Michael Kjörling
2023-07-24 18:17 ` Michael Kjörling
2023-07-24 18:45 ` blobfish
2023-07-26 15:38 ` blobfish [this message]
2023-07-26 15:50 ` Michael Kjörling
2023-07-26 16:10 ` blobfish
2023-07-26 17:49 ` Michael Kjörling
2023-07-27 14:12 ` blobfish
2023-07-28 13:17 ` Michael Kjörling
2023-07-28 15:23 ` blobfish
2023-07-28 18:50 ` Looking for confirmation as I enter the acceptance stage. -- SOLVED Michael Kjörling
2023-07-29 12:58 ` blobfish
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=4863669.GXAFRqVoOG@laptop \
--to=blobfish@gmx.com \
--cc=cryptsetup@lists.linux.dev \
/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