Your message dated Mon, 31 Aug 2009 01:15:32 +0200
with message-id <20090830231531.ga6...@resivo.wgnet.de>
and subject line Re: [pkg-cryptsetup-devel] Bug#542928: cryptsetup fail with
kernel 2.6.30-6
has caused the Debian Bug report #542928,
regarding cryptsetup fail with kernel 2.6.30-6
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.)
--
542928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:1.0.7-1
Severity: critical
Justification: breaks the whole system
Hello,
Since upgrade of the kernel to 2.6.30-6, my laptop fail to start and doesn't
ask for the lucks passphrase so my LVM setup can't start and the system lost
debian-root and debian-swap filesystem...
Rebooting with 2.6.29 old kernel start properly.
Best regards,
Guillaume JAOUEN.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: lang=fr...@euro, lc_ctype=fr...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages cryptsetup depends on:
ii dmsetup 2:1.02.36-2 The Linux Kernel Device Mapper use
ii libc6 2.9-25 GNU C Library: Shared libraries
ii libdevmapper1.02.1 2:1.02.36-1 The Linux Kernel Device Mapper use
ii libpopt0 1.14-4 lib for parsing cmdline parameters
ii libuuid1 2.16-3 Universally Unique ID library
cryptsetup recommends no packages.
Versions of packages cryptsetup suggests:
ii dosfstools 3.0.5-1 utilities for making and checking
ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs
ii udev 0.141-2 /dev/ and hotplug management daemo
-- no debconf information
--- End Message ---
--- Begin Message ---
ok, closing the bugreport with this mail.
greetings,
jonas
On 31/08/2009 Guillaume JAOUEN wrote:
> Hello,
>
> Since the last update with dselect, all is now ok. So you can close
> this bug report.
>
> I wish to thank you very much for all your great work and help :o)))))
>
> Best regards,
> Guillaume JAOUEN.
>
> Jonas Meurer wrote:
> >hey,
> >
> >On 27/08/2009 Guillaume JAOUEN wrote:
> >>I start again the laptop with kernel 2.6.30-1 amd64 and write
> >>carefully the output during the boot :
> >>
> >>...
> >>Begin : Assembling all MD arrays... mdadm : No arrays found in
> >>config file or automatically
> >>Failure : failed to assemble all arrays.
> >>done.
> >> Volume group "debian" not found
> >>Skipping volume group debian
> >>Unable to find LVM volume /debian/root
> >> Volume group "debian" not found
> >>Skipping volume group debian
> >>Unable to find LVM volume /debian/swap_1
> >>done.
> >
> >up to here, everything seems fine: mdadm is started but no software raid
> >configured, then lvm is started but no volume group available yet.
> >
> >>Begin: Waiting for root file system... done
> >>Gave up waiting for root device.
> >
> >that one indicates that the root device is not available to cryptroot.
> >for some reason, the encrypted device (/dev/sda5) is not available.
> >either missing hardware driver or wrong device might be reasons.
> >
> >>Common problems:
> >>- Boot args (cat /proc/cmdline)
> >> - Check rootdelay= (did the system wait long enough?)
> >> - Check root= (did the system wait for the right device ?)
> >>- Missing modules (cat /proc/modules;ls /dev)
> >>ALERT! /dev/mapper/debian-root does not exist. Dropping to a shell !
> >>BusyBox v1.13.3 (Debian 1:1.13.3-1) built-in shell (ash).
> >>Enter 'help' for a list of built-in commands.
> >>/bin/sh : can't access tty : job control turned off
> >>(initramfs)
> >
> >in the initramfs emergency shell, please give output of the following
> >commands:
> >
> >cat /conf/conf.d/cryproot
> >
> >ls -al /dev/sda5
> >
> >and if the device file exists, try unlocking it manually:
> >
> >cryptsetup luksOpen /dev/sda5 sda5_crypt
> >lvm vgchange -a y
> >ls -al /dev/mapper/debian-root
> >
> >if the device doesn't exist, then please give output of 'ls -al /dev'
> >from initramfs as well.
> >
> >>You'll find the output of this command in attachement :
> >>dell-xps:/boot/grub# sh -x mkinitramfs
> >>--supported-target-version="2.6.30-1-amd64" \
> >>>-o /tmp/initramfs-2.6.30-1-amd64 2>/tmp/initramfs-log
> >>dell-xps:/boot/grub#
> >
> >sorry, the command was wrong. please use the following instead:
> >
> >sh -x mkinitramfs -o /tmp/initramfs 2.6.30-1-amd64 2>/tmp/initramfs.log
> >
> >and attach /tmp/initramfs.log to the mail.
> >
> >also, please update your initramfs, try to reboot with the broken
> >kernel afterwards and seee whether that helps:
> >
> >mv /boot/initramfs-2.6.30-1-amd64 /boot/initramfs-2.6.30-1-amd64.orig
> >update-initramfs -c -k 2.6.30-1-amd64
> >
> >sorry for asking that many questions, but i simply don't have a straight
> >idea what the problem on your system might be. apparently the same
> >kernel and system setup works for me.
> >
> >greetings,
> > jonas
>
>
>
signature.asc
Description: Digital signature
--- End Message ---
