[Solved]Re: Unable to boot into encrypted file system after upgrade etch -- lenny

On 26 Mrz., 16:10, Michael Lange klappn...@web.de wrote: On Thu, 26 Mar 2009 10:41:26 +0200 snip Ok, there seems to be a bug in debian's initramfs-tools that resembles a lot the one described at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507721 . In the last few days I learned how to

Re: Unable to boot into encrypted file system after upgrade etch -- lenny

klappnase wrote: Hello, after I upgraded to lenny I am not able to boot the new kernel (2.6.26-1-686), however it still works using the old etch kernel (2.6.22-2-k7 from backports.org). About my system: There is an encrypted root partition on /dev/hda1 and a separate /boot partition on

Re: Unable to boot into encrypted file system after upgrade etch -- lenny

On Thu, 26 Mar 2009 10:41:26 +0200 Γιώργος Πάλλας gp...@ccf.auth.gr wrote: klappnase wrote: Hello, after I upgraded to lenny I am not able to boot the new kernel (2.6.26-1-686), however it still works using the old etch kernel (2.6.22-2-k7 from backports.org). About my system: There is

Unable to boot into encrypted file system after upgrade etch -- lenny

Hello, after I upgraded to lenny I am not able to boot the new kernel (2.6.26-1-686), however it still works using the old etch kernel (2.6.22-2-k7 from backports.org). About my system: There is an encrypted root partition on /dev/hda1 and a separate /boot partition on /dev/hda4. When booting the