Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Dale Amon <amon@vnl.com>
To: linux-crypto@vger.kernel.org
Cc: amon@vnl.com
Subject: cryptsetup stopped working
Date: Thu, 12 Apr 2012 23:59:40 +0100	[thread overview]
Message-ID: <20120412225940.GA3257@vnl.com> (raw)

Here is a trace of shell script I am working on. I got
through the cryptsetup earlier this evening but for some
reason it just stopped working. 

Just in case, I've rebooted to see if anything needed 
tidied up. Nope.

I also tried using loop1 instead. Also no difference.

When the cfdisk ran, I gave it a single Primary 
partition that takes all the space and is not marked 
Bootable.

At the point of failure /dev/mapper/loop9p1 exists and
I can 'cat' it, so the kpartx is happy enough with the file.

Ideas welcome...

-------------------------------------------------------------

+ dd if=/dev/zero of=/MyDisk/foo.raw count=2097152
2097152+0 records in
2097152+0 records out
1073741824 bytes (1.1 GB) copied, 28.2482 s, 38.0 MB/s
+ losetup /dev/loop0 /MyDisk/foo.raw
+ badblocks -c 10240 -s -w -t random -v /dev/loop0
Checking for bad blocks in read-write mode
>From block 0 to 1048575
Testing with random pattern: done                                
Reading and comparing: done                                
Pass completed, 0 bad blocks found.
+ cfdisk /dev/loop0

+ kpartx -a /dev/loop0
+ cryptsetup --verbose --verify-passphrase luksFormat /dev/mapper/loop0p1

WARNING!
========
This will overwrite data on /dev/mapper/loop0p1 irrevocably.

Are you sure? (Type uppercase yes): yes
Command failed with code 22: Invalid argument

             reply	other threads:[~2012-04-12 23:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12 22:59 Dale Amon [this message]
2012-04-12 23:43 ` cryptsetup stopped working Dale Amon

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=20120412225940.GA3257@vnl.com \
    --to=amon@vnl.com \
    --cc=linux-crypto@vger.kernel.org \
    /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