[dm-crypt] unknown fstype, device is busy, device already exists
scar at drigon.com
Sat Jun 1 13:30:19 CEST 2013
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
More information about the dm-crypt