cryptdisks(-early) fail on boot with "Command failed: device-mapper: create ioctl failed: Device or resource busy"

[TStahl]

Binary package hint: cryptsetup

Kubuntu Karmic Development branch (9.10)

Since a couple of days, the previously working cryptdisks setup at boot fails. I am prompted for the passphrase as usual (well, except that I have to turn now the boot splash off, but that is another bug), but when I enter the passphrase, the message

Command failed: device-mapper: create ioctl failed: Device or resource busy

appears. When I log in as root and restart cryptdisks-early and cryptdisks, I have to re-enter the passphrase and the partition is mounted as expected.

Please let me know if you need further information.

cryptsetup 2:1.0.6+20090405.svn49-1ubuntu4
udev 147~-5

ProblemType: Bug
Architecture: i386
Date: Sun Oct 4 11:03:04 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: wl
Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu4
ProcEnviron:
 LANGUAGE=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: cryptsetup
Uname: Linux 2.6.31-11-generic i686

[Reinhard Tartler (siretart)]

TStahl <email address hidden> writes:

> Please let me know if you need further information.

please attach your /etc/fstab and /etc/crypttab

--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

[TStahl (mail-myname-tstahl)]

/etc/fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda5 during installation
UUID=f8b792d4-172c-47d2-939b-62cb2d25d0b3 / ext4 errors=remount-ro 0 1
# /home/txxx was on /dev/sda6 during installation
#UUID=460f9781-dade-4168-84ce-39a940619aa0 /home/t ext4 defaults 0 2
/dev/mapper/crypt /home/txxx ext4 defaults 0 1
# /home/txxx/Music was on /dev/sda7 during installation
UUID=1233e775-78ab-4dcd-b03b-7de5dd6e529e /home/xxx/Music ext3 defaults 0 2
# swap was on /dev/sda8 during installation
UUID=80a81706-18e9-4bcc-aac6-cbba79ed0700 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

/etc/crypttab:

# <target name> <source device> <key file> <options>
crypt /dev/sda6 none none

[TStahl (mail-myname-tstahl)]

BTW, could my email address be removed from comment #2? There is not much point in having an option not to have it displayed, if it gets included in the comments in this way.

[Reinhard Tartler (siretart)]

report looks complete, setting to confirmed.
note: I did not reproduce it myself.

[Chihiro Kuroki (9nzj7bot)]

I reproduced this bug without "quiet" and "splash" as kernel boot options.
Because processes of askpass and cryptsetup were not finished,
I had to kill these processes manually, otherwise tty1 was unavailable.

>TStahl

Please boot with quiet option and splash option if it is possible, and report what happened.
You may be able to enter your passphrase on the usplash screen, and mount your crypted disk on boot.

# my crypttab
cryptvol /dev/md2 none cipher=aes-cbc-essiv:sha256

#my fstab
UUID=02af6a7a-c43f-4b<truncated> /xxx ext3 relatime 0 2

Package: cryptsetup
Status: install ok installed
Priority: optional
Architecture: amd64
Version: 2:1.0.6+20090405.svn49-1ubuntu7

[Steve Langasek (vorlon)]

Thank you for taking the time to report this bug and helping to improve Ubuntu.

In lucid, this particular bug is resolved by making the cryptdisks and cryptdisks-early init scripts no-ops.

Please continue to report any other bugs you encounter.