Incompatible libdevmapper 1.01.03 and kernel driver

Bug #53475 reported by Thomas Haberland
2
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Fix Released
Low
Scott James Remnant (Canonical)

Bug Description

Binary package hint: linux-image-2.6.12-10-686-smp

System: Kubuntu 5.10

Since the kernel update linux-image-2.6.12-10-686-smp (2.6.12-10.35) a few days ago cryptdisks doesn't work anymore. Lauching the cryptdisks service into a konsole produces this error message:

/etc/init.d/cryptdisks start

/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
/proc/misc: No entry for device-mapper found
Is device-mapper driver missing from kernel?
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.01.03 (2005-06-13)(compat) and kernel driver
Command failed

Same error happens using the non SMP kernel environment. Also the last update to linux-image-2.6.12-10.36 doesn't solve this problem.

All available updates are installed.

Revision history for this message
Ben Collins (ben-collins) wrote : Re: [Bug 53475] Incompatible libdevmapper 1.01.03 and kernel driver

On Wed, 2006-07-19 at 20:12 +0000, Thomas Haberland wrote:
> /proc/misc: No entry for device-mapper found
> Is device-mapper driver missing from kernel?
> Failure to communicate with kernel device-mapper driver.
> /proc/misc: No entry for device-mapper found
> Is device-mapper driver missing from kernel?
> Failure to communicate with kernel device-mapper driver.
> Incompatible libdevmapper 1.01.03 (2005-06-13)(compat) and kernel driver
> Command failed

Did you check if the dm module is loaded?

Revision history for this message
Thomas Haberland (th-haberland) wrote :

> Did you check if the dm module is loaded?

unfortunately not. Because I never need to manually load the module and automatic mounting of the cryptdisks partition during system boot did work correctly since I installed Kubuntu 5.10 past year.
To be honest, in the meantime I found the correct module name for the required module (dm-crypt), the error message wasn't real helpfull.

After "modprobe dm-crypt" cryptdisks will start correctly.

So the final question is, what happened that a manual module load is required and the automatic mounting during system boot doesn't work anymore after a kernel security update.

Revision history for this message
Ben Collins (ben-collins) wrote :

Going to kick this over to udev, since I've no idea where else to put it. I do know that the dm-crypt module is not in the realm of "auto-loading", and since loading it makes everything work, then the kernel is no longer the culprit.

Something else needs to load this module.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

cryptsetup should do this, I've modified that package appropriately and now the module will be loaded

Changed in udev:
assignee: nobody → keybuk
importance: Untriaged → Low
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.