Bug#541823: installation-reports: Acer Aspire 3690
reassign 541823 partman-crypto
tags 541823 + moreinfo
retitle 541823 Installed system with root on crypto-pv fails to boot
thanks
Hi again,
since it seems the crypto-root is the only remaining topic in
this installation report, I'm reassigning it to partman-crypto so
we don't lose it amongst the 2000(?) other reports.
To highlight the remaining issue:
On Mon, Sep 21, 2009 at 04:16:48PM -0400, Celejar wrote:
> On Mon, 21 Sep 2009 22:03:57 +0200
> Max Vozeler <xam@debian.org> wrote:
> > > > 5) The showstopper: I installed the entire system (except
> > > > for /boot) onto LVM volumes in a vg on top of a LUKS volume
> > > > created out of a primary partition. When I rebooted, the system
> > > > wouldn't bring up the LUKS volume. The eventual fix that worked
> > > > is to add this line to /boot/grub/menu.lst:
> > > >
> > > > # kopt=cryptopts=target=hda4_crypt,source=/dev/hda4,lvm=lizzie-root
> > > > # root=/dev/mapper/lizzie-root ro
> > > >
> > > > This is:
> > > >
> > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492790
> > > >
> > > > and
> > > >
> > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522041
> > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507721
> > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503062
> >
> > Hmmm. This certainly *should* work.
> >
> > Celejar, did you configure a label on the root filesystem, or
> > remember setting anything unusual?
>
> Don't think so.
>
> > There are different issues that could lead to such symptoms,
> > as can be seen in the different bug reports you referenced, but
> > (AFAICT) none of those should affect current installer builds.
> >
> > It occurs to me that you might have hit a temporary problem we
> > had in daily builds after we switched to UUID by default. This
> > could lead to exactly those symptoms, and has since been fixed.
> >
> > Any chance you could retry the installation with a current image
> > and try to reproduce it there? I do realize this may not be
> > possible, but asking can't hurt. :-)
>
> Tell you what - I happen to have a lot of space on an external USB HDD
> that I use for backup and storage. It should be easy enough to do
> another install onto that disk, and I've been meaning to do so anyway
> to have a spare installation for when my main one breaks, so when I can
> find the time, perhaps I'll try it. I suppose that the conditions won't
> be quite the same as the original install, but let me know if it will
> still be useful.
>
> > Otherwise I think we should assume this was caused by the problem
> > we already fixed - unless someone sees this with a current image.
Max
Reply to: