Am Samstag, den 18.09.2010, 23:04 +0200 schrieb Andreas von Heydwolff: > It is gone because I replaced in line 185 of > > /usr/share/initramfs-tools/hooks/cryptroot > > echo "cryptsetup: WARNING: invalid line in /etc/crypttab - $opt" >&2 > > with > > echo "cryptsetup: WARNING: invalid line in /etc/crypttab - $opt > (target=$target, extraopts=$extraopts, @=$@)" > > as you suggested. When I revert to the old line I again get this situation: > > # update-initramfs -u > 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 - Ehm... I suggested to change that line for *diagnosing only*. The "fix" was that apparently you forgot the ">&2" part at the end, therefore the output is not redirected to stderr. Please re-read my old mail.
> > * You do still have the problem that for some reason your root file > > system is not correctly mounted during initramfs stage. > > Yes Questions: * What exactly fails at booting during the initramfs stage? Do the raid devices get assembled correctly? Do the crypto devices get unlocked? What about LVM? In short: What works, what doesn't? * What exactly do you have to do to boot your system manually after being thrown to a rescue shell (precise commands)? * The double-UUID-problem: What is /dev/mapper/vg-md1dm0? Do somehow manually create it when booting the system by hand? What happens if you use *only* "vgscan; vgchange -ay" to activate all logical volumes? Best regards Alexander Kurtz [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594472#159
signature.asc
Description: This is a digitally signed message part
