On 2010-09-18 18:33, Alexander Kurtz wrote:
-snip-
Ok, let me summarize:
* You did have[1] the problem that was caused by mdadm bug #583917[2].
However, after upgrading to mdadm 3.1.4 that is solved.
Yes
* You did have[3] some issue with cryptsetups initramfs hook.
However, for some reason that is gone now.
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 -
* You do still have the problem that for some reason your root file
system is not correctly mounted during initramfs stage.
Yes
Everything correct so far? If so we can focus on tackling the last
point!
Would be great if you could help me here.
Kind regards,
Andreas v. Heydwolff
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
