Andreas, I had problems as well, but I used apt-get to upgrade and the initramfs of ..-amd64 did not get updated. I could not see the crypttab error message.
For me it helped to run a separate # update-initramfs after the upgrade. If that does not help, how does your /etc/crypttab look like? On 9/10/10, Andreas von Heydwolff <106624....@compuserve.com> wrote: > [stuff deleted] > >> Am Sonntag, den 29.08.2010, 02:35 +0200 schrieb Agustin Martin: >>> May this be related to #583917, mdadm: long delay (6-200 minutes) >>> during boot (root device detection) after upgrade on RAID/LVM/LUKS >>> setup? >> >> Am Samstag, den 04.09.2010, 04:22 +0100 schrieb Darren: >>> upgrading to mdadm 3.1.4-1+8efb9d1 from sid solved my boot problems. >>> That is for both, the VM I set up for testing, as well as my base PC. >>> Both are booting fine now. >> >> >> This *might* indeed be a duplicate of #594418: >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594418 >> >> Best regards >> >> Alexander Kurtz > > No joy here despite the upgrade of mdadm to 3.1.4-1+8efb9d1. The problem > remains the same for me (vg with root not found) in that there is a > complaint about the vg with the root fs not found (the correct name of > the vg is being used which may be new), then I get dropped to the > intiramdisk shell. From there I can manually unlock and start the > disk/vg and upon exiting the normal bootup process continues. > > However, I noticed that when I was installing the new mdadm package fro > sid cryptsetup had a problem at the end of generating the new > initramdisk, perhaps this is relevant? The messages are here: > > > # dpkg -i mdadm_3.1.4-1+8efb9d1_amd64.deb > (Lese Datenbank ... 68876 Dateien und Verzeichnisse sind derzeit > installiert.) > Vorbereiten zum Ersetzen von mdadm 3.1.1-1 (durch > mdadm_3.1.4-1+8efb9d1_amd64.deb) ... > Entpacke Ersatz für mdadm ... > Richte mdadm ein (3.1.4-1+8efb9d1) ... > Installiere neue Version der Konfigurationsdatei > /etc/logcheck/ignore.d.server/mdadm ... > Installiere neue Version der Konfigurationsdatei /etc/cron.d/mdadm ... > Generating array device nodes... done. > update-initramfs: deferring update (trigger activated) > insserv: script vmware-core: service VMware already provided! > insserv: script vmware-autostart: service VMware already provided! > insserv: script vmware-mgmt: service VMware already provided! > insserv: script vmware-core: service VMware already provided! > insserv: script vmware-autostart: service VMware already provided! > insserv: script vmware-mgmt: service VMware already provided! > Generating udev events for MD arrays...done. > Verarbeite Trigger für man-db ... > Verarbeite Trigger für initramfs-tools ... > update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 > cryptsetup: WARNING: invalid line in /etc/crypttab - > cryptsetup: WARNING: invalid line in /etc/crypttab - > > > Regards, > Andreas Heydwolff > > > > > -- > To unsubscribe, send mail to 594472-unsubscr...@bugs.debian.org. > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
