Re: What are the two roots in grub?
On Mon, Feb 19, 2007 at 03:16:06PM -0800, Andrew Sackville-West wrote:
> On Mon, Feb 19, 2007 at 01:48:37PM -0500, hendrik@topoi.pooq.com wrote:
> > On Mon, Feb 19, 2007 at 01:15:58PM -0500, Greg Folkert wrote:
> > > On Mon, 2007-02-19 at 12:46 -0500, hendrik@topoi.pooq.com wrote:
> > > > Do I understand this correctly?
> > > >
> > > > In my /boot/grub/menu.lst there is a stanza
> > > >
> > > > title other: Debian GNU/Linux, kernel 2.6.18-3-486
> > > > root (hd0,7)
> > > ^^^^
> > > This particular "root" is the "grub installation root" IOW it will load
> > > the following line like this
> > >
> > > (hd0,7)/vmlinuz-2.6.18-3-486 root=/dev/mapper/lovesong-other ro
> > >
> > > > kernel /vmlinuz-2.6.18-3-486 root=/dev/mapper/lovesong-other ro
> > > ^^^^
> > > That root is the "root" of your machine. and it is passed onto your
> > > kernel as a command line option.
> >
> > I see... so (hd0,7) is the partition where grub looks up all the
> > unadorned filenames bentioned in the stanza. And the other root is the
> > root of the filesystem in the to-be-booted system.
> > >
>
> yup.
>
> Maybe you're problem is in the initrd. If it is built to look for / in
> place and you've moved it (which you've done by changing the root=
> parameter, then maybe that is the problem. Try chrooting into the new
> system and building a new initrd from within the chroot. It has worked
> for me before (etch) when moving partitions around.
>
> A
Perhaps the simple solution to the original problem is to install etch
from scratch rather than try to upgrade sarge.
Still ... that makes it seem too much like Windows.
-- hendrik
Reply to: