All of lore.kernel.org
 help / color / mirror / Atom feed
* [dm-crypt] unknown fstype, device is busy, device already exists
@ 2013-06-01  3:51 scar
  2013-06-01  5:49 ` scar
  0 siblings, 1 reply; 4+ messages in thread
From: scar @ 2013-06-01  3:51 UTC (permalink / raw)
  To: dm-crypt

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dm-crypt] unknown fstype, device is busy, device already exists
  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
  0 siblings, 1 reply; 4+ messages in thread
From: scar @ 2013-06-01  5:49 UTC (permalink / raw)
  To: dm-crypt

booted with SystemRescueCD and SMART status looks ok
(http://pastebin.com/wfZ5q5TL)
fdisk:
Disk /dev/sda: 300.1 GB, 300069052416 bytes, 586072368 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c3127

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63      192779       96358+  83  Linux
/dev/sda2          192780   586067264   292937242+   5  Extended
/dev/sda5          192843   586067264   292937211   83  Linux

if i try to unlock /dev/sda5 it works and lvdisplay shows my logical
volumes (http://pastebin.com/v9gqjchL) but when i try to mount
/dev/ubuntu/root i get "special device /dev/ubuntu/root does not exist"
so unsure if that is a limitation of sysrescuecd or a problem with my
LVM in which case i needa move to another mailing list??

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dm-crypt] unknown fstype, device is busy, device already exists
  2013-06-01  5:49 ` scar
@ 2013-06-01  6:52   ` Milan Broz
  2013-06-01 11:30     ` scar
  0 siblings, 1 reply; 4+ messages in thread
From: Milan Broz @ 2013-06-01  6:52 UTC (permalink / raw)
  To: scar; +Cc: dm-crypt



On 06/01/2013 07:49 AM, scar wrote:
> booted with SystemRescueCD and SMART status looks ok
> if i try to unlock /dev/sda5 it works and lvdisplay shows my logical
> volumes (http://pastebin.com/v9gqjchL) but when i try to mount

Didn't you forget to activate LVs?

Use "vgchange -a y" and try to mount them again.

Milan

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dm-crypt] unknown fstype, device is busy, device already exists
  2013-06-01  6:52   ` Milan Broz
@ 2013-06-01 11:30     ` scar
  0 siblings, 0 replies; 4+ messages in thread
From: scar @ 2013-06-01 11:30 UTC (permalink / raw)
  To: dm-crypt

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2013-06-01 11:30 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.