Bug 410418 - mount: unknown filesystem type 'crypto_LUKS'
Summary: mount: unknown filesystem type 'crypto_LUKS'
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Final
Hardware: PowerPC Linux
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Hendrik Vogelsang
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-18 16:20 UTC by Olaf Hering
Modified: 2009-03-09 14:24 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olaf Hering 2008-07-18 16:20:39 UTC 
fresh 11.0 on fig.suse.de
mount: unknown filesystem type 'crypto_LUKS'

there was an ext3 before on /dev/system/home, but now I tried a crypt home.

Why does mount and blkid return different results?
I think they both use libvolid.

fig:~ # df -hTlP
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/mapper/system-root ext3   15G  2.4G   12G  18% /
udev         tmpfs     93M   92K   93M   1% /dev
/dev/mapper/cr_home ext3   22G  173M   21G   1% /home
fig:~ # blkid
/dev/hda2: TYPE="hfs"
/dev/hda3: UUID="bm2s3l-ZmAh-vVi6-kodj-4IVh-1Vv5-jxJP21" TYPE="lvm2pv"
/dev/dm-0: UUID="84e04e09-cb5c-40b4-9175-16a4afc2f977" SEC_TYPE="ext2" TYPE="ext3"
/dev/dm-1: LABEL="fig_root" UUID="f8e3ba7b-0eac-4822-b074-9a5ae90865bf" TYPE="ext3"
/dev/dm-2: TYPE="swap" LABEL="fig_swap" UUID="eb0ddd22-8eee-4746-9e09-65f208b50cb2"
/dev/dm-3: UUID="37fd83eb-7487-413f-84b2-9dfe5598ae88" TYPE="ext3"
fig:~ # mount -voro /dev/dm-
dm-0  dm-1  dm-2  dm-3
fig:~ # mount -voro /dev/dm-0 /mnt/
mount: you didn't specify a filesystem type for /dev/dm-0
       I will try type crypto_LUKS
mount: unknown filesystem type 'crypto_LUKS'
fig:~ # mount -voro /dev/dm-3 /mnt/
mount: you didn't specify a filesystem type for /dev/dm-3
       I will try type ext3
mount: /dev/dm-3 already mounted or /mnt/ busy
Comment 1 Matthias Koenig 2008-07-28 11:17:16 UTC 
crypto_LUKS is not known to mount, because it is not a real filesystem.
So the crypto partition has to be set up either manually with cryptsetup or with the init scripts (boot.crypto,boot.crypto-early) before you can mount it.

mount is linked against libvolume_id from udev, while blkid uses libblkid both from e2fsprogs. They differ in some aspects, e.g. detection order, the issue here looks like the everlasting old signature problem.

How did you set up the crypto partition?
Do the crypto filesystem get set up properly by the init script magic?
Comment 2 Olaf Hering 2008-07-28 11:31:35 UTC 
crypto works.
Its just that blkid and mount have a different view on the metadata.
Comment 3 Matthias Koenig 2008-11-18 11:06:18 UTC 
I think the real problem is, that cryptsetup luksFormat should wipe existing signatures when formatting the device.
Comment 5 Hendrik Vogelsang 2009-03-09 14:24:27 UTC 
not really a bug and now that upstream works on unifying this i close this one