reassign 594472 mdadm forcemerge 583917 594472 thanks Hi Toni,
Everybody else's problems were definitely caused[1][2] by mdadm bug #583917[3]. Could you try upgrading to mdadm 3.1.4 (has reached squeeze already), regenerate your initramfs and report whether this solves your booting problems? If your system doesn't currently boot at all, please see my former mail[4] for instructions. When doing so, please make sure that you use the right names (compared to /etc/crypttab) when unlocking your crypto devices. Not doing so was why Andreas could still not boot after upgrading mdadm[5]. Best regards Alexander Kurtz [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594472#119 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594472#199 [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583917 [4] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594472#164 [5] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594472#204
signature.asc
Description: This is a digitally signed message part
