DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: scar <scar@drigon.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] unknown fstype, device is busy, device already exists
Date: Sat, 01 Jun 2013 04:30:19 -0700	[thread overview]
Message-ID: <kocm08$amq$1@ger.gmane.org> (raw)
In-Reply-To: <51A99A20.3050505@gmail.com>

Milan Broz @ 05/31/2013 11:52 PM:
> Didn't you forget to activate LVs?
> Use "vgchange -a y" and try to mount them again.

thanks, yes, i did.  i'm in unknown waters here!  after making LVs
available and trying to mount again i'm getting "NTFS signature is
missing" (which makes no sense since i've never used NTFS before).  if i
add '-t ext3' i get "wrong fs type, bad option, bad superblock on
/dev/mapper/ubuntu-root, missing codepage or helper program...." so i
ran fsck and it fixed a number of errors....

bad magic number in super-block
superblock invalid, trying backup blocks....
Superblock needs_recovery flag is clear, but journal has data
Recovery flag not set in backup superblock, so running journal anyway
/dev/mapper/ubuntu-root: recovering journal

and then alot of things i fix... free blocks count wrong, directories
count wrong, free inodes count wrong.  but after fixing i am able to
mount the filesystem and boot the system normally.  *sigh of relief*
i'm pleased the FS was able to be repaired but what caused it still irks
me....

      reply	other threads:[~2013-06-01 11:30 UTC|newest]

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

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='kocm08$amq$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