Re: Unable to boot into encrypted file system after upgrade etch --> lenny
On Thu, 26 Mar 2009 10:41:26 +0200
Γιώργος Πάλλας <gpall@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 an
> > encrypted root partition on /dev/hda1 and a separate /boot partition
> > on /dev/hda4. When booting the new kernel I get "Waiting for root file
> > system" and a while later I am being dropped to a busy box shell. I
> > have seen, the docs suggest that the problem might be a /dev/hda - /
> > dev/sda confusion with a new kernel, however before the boot hangs
> > there is a bunch of messages that addresses the hard disk as "/dev/
> > hda". Furthermore I followed the docs' suggestion to add label
> > descriptors to the hard disk partitions to avoid these confusions.
> >
>
> Did you run a
> 'update-initramfs' ?
> Normally you wouldn't have to, but try it...
>
> G.
>
>
Yes I did. Even worse, in my first post I hoped that all that is wrong is that
some necessary kernel modules are missing from /etc/initramfs-tools/modules .
Now I found that I can run the debian-rescue live-cd which uses the very same
kernel (2.6.26-1-686) and I am able to mount the encrypted partition from there;
so I tried adding everything lsmod returns there to /etc/initramfs-tools/modules
and re-run update-initramfs, yet without success. I also tried adding rootdelay=9
to the kernel line in grub/menu.lst as it has been suggested somewhere, but it did not
change anything, except that I had to wait 9 seconds for "Waiting for root file system" :(
Does anyone have another idea?
Michael
Reply to: