From: blobfish <blobfish@gmx.com>
To: cryptsetup@lists.linux.dev
Subject: Re: Looking for confirmation as I enter the acceptance stage.
Date: Sun, 23 Jul 2023 20:00:23 -0400 [thread overview]
Message-ID: <5860622.MhkbZ0Pkbq@laptop> (raw)
In-Reply-To: <a59bcd66-474e-4844-b9d1-1996ce503ebb@home.arpa>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
On Sunday, July 23, 2023 7:04:54 PM EDT Michael Kjörling wrote:
> Please post the full output of `blkid /dev/sdb1` and `lsblk -bJO
> /dev/sdb1`, along with the output from running `cryptsetup luksOpen`
> on the container with `--debug` specified.
>
> Also a clarification: you mention that you know the passphrase. Did
> the container have more than one active key slot? (Say, one with a
> passphrase you've memorized, and one with the key file you attached.)
>
> Also, would it be possible for you to post the corresponding data
> unencoded?
> sudo dd if=/dev/sdb1 of=sdb1.head bs=32525167 count=1
> sudo gzip sdb1.head
> and post the resulting sdb1.head.gz.
Thanks for the response. I believe I have all the information you requested in
the attached files. Let me know, if not.
Yes I had two active key slots. One with a passphrase that was created from
the initial encryption setup. Another I created later to auto mount at boot,
which I sent in the previous mail.
[-- Attachment #2: blkidResults.txt --]
[-- Type: text/plain, Size: 59 bytes --]
/dev/sdb1: PARTUUID="abcd9acd-027f-47ac-a4c0-8974a5aeaf5e"
[-- Attachment #3: lsblkResults.txt --]
[-- Type: text/plain, Size: 1853 bytes --]
{
"blockdevices": [
{
"alignment": 0,
"disc-aln": 0,
"dax": false,
"disc-gran": 0,
"disc-max": 0,
"disc-zero": false,
"fsavail": null,
"fsroots": [
null
],
"fssize": null,
"fstype": null,
"fsused": null,
"fsuse%": null,
"fsver": null,
"group": "disk",
"hctl": null,
"hotplug": true,
"kname": "sdb1",
"label": null,
"log-sec": 512,
"maj:min": "8:17",
"min-io": 4096,
"mode": "brw-rw----",
"model": null,
"name": "sdb1",
"opt-io": 0,
"owner": "root",
"partflags": null,
"partlabel": null,
"parttype": "0fc63daf-8483-4772-8e79-3d69d8477de4",
"parttypename": "Linux filesystem",
"partuuid": "abcd9acd-027f-47ac-a4c0-8974a5aeaf5e",
"path": "/dev/sdb1",
"phy-sec": 4096,
"pkname": "sdb",
"pttype": "gpt",
"ptuuid": "dd9a66b6-66d3-4235-a425-c129153fecc0",
"ra": 128,
"rand": true,
"rev": null,
"rm": false,
"ro": false,
"rota": true,
"rq-size": 60,
"sched": "mq-deadline",
"serial": null,
"size": 8001562156032,
"start": 2048,
"state": null,
"subsystems": "block:scsi:usb:pci",
"mountpoint": null,
"mountpoints": [
null
],
"tran": null,
"type": "part",
"uuid": null,
"vendor": null,
"wsame": 0,
"wwn": null,
"zoned": "none",
"zone-sz": 0,
"zone-wgran": 0,
"zone-app": 0,
"zone-nr": 0,
"zone-omax": 0,
"zone-amax": 0
}
]
}
[-- Attachment #4: luksOpenDebug.txt --]
[-- Type: text/plain, Size: 2074 bytes --]
# cryptsetup 2.6.1 processing "cryptsetup --debug luksOpen /dev/sdb1 mapped1"
# Verifying parameters for command open.
# Running command open.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
# Allocating context for crypt device /dev/sdb1.
# Trying to open and read device /dev/sdb1 with direct-io.
# Initialising device-mapper backend library.
# Trying to load any crypt type from device /dev/sdb1.
# Crypto backend (OpenSSL 3.0.9 30 May 2023 [default][legacy]) initialized in cryptsetup library version 2.6.1.
# Detected kernel Linux 6.1.0-9-amd64 x86_64.
# Loading LUKS2 header (repair disabled).
# Acquiring read lock for device /dev/sdb1.
# Opening lock resource file /run/cryptsetup/L_8:17
# Verifying lock handle for /dev/sdb1.
# Device /dev/sdb1 READ lock taken.
# Trying to read primary LUKS2 header at offset 0x0.
# Opening locked device /dev/sdb1
# Verifying locked device handle (bdev)
# Trying to read secondary LUKS2 header at offset 0x4000.
# Reusing open ro fd on device /dev/sdb1
# Trying to read secondary LUKS2 header at offset 0x8000.
# Reusing open ro fd on device /dev/sdb1
# Trying to read secondary LUKS2 header at offset 0x10000.
# Reusing open ro fd on device /dev/sdb1
# Trying to read secondary LUKS2 header at offset 0x20000.
# Reusing open ro fd on device /dev/sdb1
# Trying to read secondary LUKS2 header at offset 0x40000.
# Reusing open ro fd on device /dev/sdb1
# Trying to read secondary LUKS2 header at offset 0x80000.
# Reusing open ro fd on device /dev/sdb1
# Trying to read secondary LUKS2 header at offset 0x100000.
# Reusing open ro fd on device /dev/sdb1
# Trying to read secondary LUKS2 header at offset 0x200000.
# Reusing open ro fd on device /dev/sdb1
# Trying to read secondary LUKS2 header at offset 0x400000.
# Reusing open ro fd on device /dev/sdb1
# LUKS2 header read failed (-22).
# Device /dev/sdb1 READ lock released.
# Releasing crypt device /dev/sdb1 context.
# Releasing device-mapper backend.
# Closing read only fd for /dev/sdb1.
Command failed with code -1 (wrong or missing parameters).
[-- Attachment #5: sdb1.head.gz --]
[-- Type: application/gzip, Size: 48255 bytes --]
next prev parent reply other threads:[~2023-07-24 0:00 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 [this message]
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
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=5860622.MhkbZ0Pkbq@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