[pkg-cryptsetup-devel] Bug#511840: initramfs-tools: Initrd fails to find root device after boot into system following install - INCLUDED PATCH solves the problem.

[maximilian attems]

[ please keep the bug report on CC,
  this is *not* private converstion ]

On Thu, 15 Jan 2009, Pyotr Berezhkov wrote:

> On 15 Jan 09, maximilian attems wrote:
> > i'd guess that grub is much better tested as it is the default.
> > any special reason why you'd picked lilo.
> > the default encrypted root install is afaik very well tested.
> >  
> Well, the encrypted root install with LVM _failed_ for me, which is why
> I reported the bug.  I didn't choose Lilo.  Lilo is chosen by the
> installer itself, as Grub doesn't support LVM.  So there's no choice
> but to use Lilo here, I'm afraid.  Here's my e-mail exchange with
> installer maintainer Ferenc Wagner on that subject.

how about you debug the real cause of the failure, see 
http://wiki.debian.org/InitramfsDebug for more hints.
 
> I wrote:
> >>> Why is the installer using Lilo (which I thought had gone out with
> >>> the dinosaurs)?
> He answered:
> >>Grub can't be used if /boot is on LVM or it isn't an ext2 (or ext3)
> >>partition.  The contents of /proc/mounts would help.
> 
> > i'm not the mantainer of that boot script,
> > but the patch you'd sent in looks fundamentaly wrong.
> >  
> The patch was applied, tested, and works, and I believe it follows the
> guidelines.  What package does /scripts/local-top/cryptroot belong in
> then?  The bug could be reassigned to them.
> 
>   -PGB

the bug is already reassigned to cryptsetup.
anyway the way you tried to solve it is out of question:
random script deleting the root device node.

-- 
maks