From: Cory Coager <ccoager@gmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] LUKS header always disappears after reboot
Date: Tue, 03 Jan 2012 22:46:49 -0500 [thread overview]
Message-ID: <4F03CBA9.2000801@gmail.com> (raw)
I have a dedicated drive used just for data. The entire drive is
encrypted with cryptsetup & LUKS. Since the drive is 3tb in size I had
to create the partition with parted. The partition is aligned for
optimal performance.
fdisk -lu:
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util
fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT
parted:
GNU Parted 2.3
Using /dev/sdb
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: ATA Hitachi HDS5C303 (scsi)
Disk /dev/sdb: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 3001GB 3001GB
(parted) align-check opt 1
1 aligned
For some reason, every time I reboot the LUKS header is no longer
recognized. I checked to make sure the appropriate modules are loaded
into memory. The first time I just redid it thinking maybe I did
something wrong. The second time now this has happened I'm thinking
something else is going on. Why does this keep happening? How do I fix
it without redoing it as I have data on this drive.
# cryptsetup luksDump /dev/sdb1
Device /dev/sdb1 is not a valid LUKS device.
next reply other threads:[~2012-01-04 3:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 3:46 Cory Coager [this message]
2012-01-04 18:59 ` [dm-crypt] LUKS header always disappears after reboot Arno Wagner
2012-01-05 0:50 ` Cory Coager
2012-01-05 8:11 ` Arno Wagner
2012-01-06 1:11 ` Cory Coager
2012-01-06 9:37 ` Arno Wagner
2012-01-06 11:37 ` Cory Coager
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=4F03CBA9.2000801@gmail.com \
--to=ccoager@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.