From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glkdd-dm-crypt@m.gmane.org>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id t-zoL7i1tLJw for <dm-crypt@saout.de>;
 Sat,  1 Jun 2013 13:30:33 +0200 (CEST)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Sat,  1 Jun 2013 13:30:33 +0200 (CEST)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <glkdd-dm-crypt@m.gmane.org>) id 1Uik12-0006Oe-Nv
 for dm-crypt@saout.de; Sat, 01 Jun 2013 13:30:32 +0200
Received: from ip70-190-192-118.ph.ph.cox.net ([70.190.192.118])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Sat, 01 Jun 2013 13:30:32 +0200
Received: from scar by ip70-190-192-118.ph.ph.cox.net with local (Gmexim 0.1
 (Debian)) id 1AlnuQ-0007hv-00
 for <dm-crypt@saout.de>; Sat, 01 Jun 2013 13:30:32 +0200
From: scar <scar@drigon.com>
Date: Sat, 01 Jun 2013 04:30:19 -0700
Message-ID: <kocm08$amq$1@ger.gmane.org>
References: <kobrab$abn$1@ger.gmane.org> <koc21e$466$1@ger.gmane.org>
 <51A99A20.3050505@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
In-Reply-To: <51A99A20.3050505@gmail.com>
Subject: Re: [dm-crypt] unknown fstype, device is busy, device already exists
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

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....