Your message dated Mon, 3 May 2010 11:41:06 +0200
with message-id <20100503094105.gc5...@resivo.wgnet.de>
and subject line Re: [pkg-cryptsetup-devel] Bug#552412: More info as requested
has caused the Debian Bug report #552412,
regarding cryptsetup: encypted lvm2 partition consistantly fails to boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
552412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:1.1.0~rc2-1
Severity: important
After recent upgrade kernel version 2.6.30-2 fails to boot with this message:
Enter passphrase for /dev/hda3: <correctr passwd entered>
device-mapper: ioctl: unable to remove open device temporary-cryptsetup-677
device-mapper: remove ioctl failed: Device or resource busy
Key slot 0 unlocked.
...[several other messages which I didn't capture] ...
and eventually I end up at the busybox prompt.
Two other kernels, 2.6.30-1 and 2.6.26-2-686 still boot OK.
I'm not sure this is a cryptsetup error but it seems the only relevant
package that was recently upgraded.
/dev/mapper/hda3_crypt exists and looks correct after the failure.
-- Package-specific info:
-- /proc/cmdline
root=/dev/mapper/vulteeVG-rootLV ro vga=791
-- /etc/crypttab
hda3_crypt /dev/hda3 none luks
-- /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/vulteeVG-rootLV / ext2 errors=remount-ro 0 1
/dev/hda2 /boot ext2 defaults 0 2
/dev/mapper/vulteeVG-vulteeLV /vultee ext3 noatime 0 2
/dev/mapper/vulteeVG-swapLV none swap sw 0 0
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/hda1 /xp ntfs-3g
defaults,users,gid=users,umask=022,locale=en_US.utf8 0 0
-- lsmod
Module Size Used by
sg 20296 0
ppdev 6348 0
lp 8012 0
parport 31144 2 ppdev,lp
powernow_k8 12260 0
cpufreq_userspace 2768 0
cpufreq_stats 3520 0
cpufreq_conservative 6256 0
cpufreq_powersave 1292 0
nfsd 204900 9
exportfs 3792 1 nfsd
nfs 221580 10
lockd 57972 2 nfsd,nfs
fscache 34440 1 nfs
nfs_acl 2640 2 nfsd,nfs
auth_rpcgss 31416 2 nfsd,nfs
sunrpc 163772 34 nfsd,nfs,lockd,nfs_acl,auth_rpcgss
fuse 47752 3
ext3 107172 1
jbd 41036 1 ext3
loop 13324 0
snd_intel8x0 26584 2
snd_ac97_codec 91264 1 snd_intel8x0
ac97_bus 1456 1 snd_ac97_codec
snd_pcm_oss 32232 0
snd_mixer_oss 12368 1 snd_pcm_oss
snd_pcm 62420 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_seq_midi 5688 0
snd_rawmidi 18596 1 snd_seq_midi
snd_seq_midi_event 6212 1 snd_seq_midi
snd_seq 42436 2 snd_seq_midi,snd_seq_midi_event
snd_timer 17436 2 snd_pcm,snd_seq
snd_seq_device 6136 3 snd_seq_midi,snd_rawmidi,snd_seq
snd 49060 13
snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
i2c_nforce2 6448 0
k8temp 3984 0
soundcore 6184 1 snd
psmouse 37528 0
i2c_core 20844 1 i2c_nforce2
snd_page_alloc 8180 2 snd_intel8x0,snd_pcm
pcspkr 2104 0
serio_raw 4560 0
evdev 8028 10
processor 34504 1 powernow_k8
button 5060 0
ext2 54120 2
mbcache 6924 2 ext3,ext2
sha256_generic 11216 0
aes_i586 8092 2
aes_generic 27436 1 aes_i586
cbc 3012 1
dm_crypt 11092 1
dm_mod 49992 13 dm_crypt
raid1 18476 0
md_mod 77780 1 raid1
ide_cd_mod 24484 0
cdrom 30316 1 ide_cd_mod
ide_gd_mod 19852 4
ide_pci_generic 3632 0
ata_generic 4340 0
ohci_hcd 19880 0
sata_nv 19688 0
amd74xx 5428 3
ehci_hcd 29680 0
ide_core 88100 4 ide_cd_mod,ide_gd_mod,ide_pci_generic,amd74xx
libata 150904 2 ata_generic,sata_nv
scsi_mod 131800 2 sg,libata
forcedeth 46584 0
usbcore 126004 3 ohci_hcd,ehci_hcd
floppy 46220 0
thermal 12580 0
fan 4044 0
thermal_sys 13140 3 processor,thermal,fan
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968)
(ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash
Versions of packages cryptsetup depends on:
ii dmsetup 2:1.02.36-4 The Linux Kernel Device Mapper use
ii libc6 2.10.1-1 GNU C Library: Shared libraries
ii libdevmapper1.02.1 2:1.02.38-2 The Linux Kernel Device Mapper use
ii libpopt0 1.15-1 lib for parsing cmdline parameters
ii libuuid1 2.16.1-4 Universally Unique ID library
cryptsetup recommends no packages.
Versions of packages cryptsetup suggests:
pn dosfstools <none> (no description available)
ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs
ii udev 146-5 /dev/ and hotplug management daemo
-- no debconf information
--- End Message ---
--- Begin Message ---
hey steve,
first sorry for the long delay, i'm rather busy at the moment.
On 06/03/2010 SteveM wrote:
> Wow, you're still working this? Time has passed and my hardware has
> changed. I can't remember the exact situation of the original bug
> report, but I think, since then, I've re-installed lenny on that machine
> and then gone on to a sid upgrade. To answer your question, no, I can
> not reproduce the original bug. Very sorry.
ok, so closing the original bugreport with this mail.
> While I have your attention though, the lenny to sid upgrade brings in a
> new kernel (lenny:2.6.26-2-amd64 -> sid:2.6.30-2-amd64) which fails to
> find the volume group on my encrypted disk. I repeated the
> install/upgrade procedure multiple times with the same results. sid has
> since moved to 2.6.32-trunk-amd64 which exhibits the same symptoms. So,
> on the surface, I have the same problem as before.
and downgrading to an old kernel fixes the issue? please provide more
information about how to reproduce the bug. if i got you right, you did
a clean installation of debian/sid, and this installation fails to boot
because the lvm is not found on the successfully unlocked encrypted
disk, right?
greetings,
jonas
signature.asc
Description: Digital signature
--- End Message ---
