DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: scar <scar@drigon.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] unknown fstype, device is busy, device already exists
Date: Fri, 31 May 2013 20:51:00 -0700	[thread overview]
Message-ID: <kobrab$abn$1@ger.gmane.org> (raw)

i'm trying to boot an ubuntu 10.04 system with encrypted root partition,
suddenly unable to.  i'm typing the passphrase correctly, as i see "Key
slot 1 unlocked" on the console, but it is then followed by:

cryptsetup: unknown fstype, bad password or options?
Device sda5_crypt is busy.
Device sda5_crypt already exists

and then i am asked for the passphrase again.  after i type it again i
am told "cryptsetup failed, bad password or options?"

after a third time i receive the same message but then after about a
minute i am told "no init found" and dropped to a Busybox shell.

sounds like my disk suddenly crapped out or something, what kinds of
remedies are available?  thanks

             reply	other threads:[~2013-06-01  4:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01  3:51 scar [this message]
2013-06-01  5:49 ` [dm-crypt] unknown fstype, device is busy, device already exists scar
2013-06-01  6:52   ` Milan Broz
2013-06-01 11:30     ` scar

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='kobrab$abn$1@ger.gmane.org' \
    --to=scar@drigon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox