[gentoo-user] genkernel-next will not mount /usr but genkernel will

[gentoo-user] genkernel-next will not mount /usr but genkernel will

[covici]

Hi folks.  I wanted to switch to using genkernel-next instead of
genkernel so eventually I could switch to using systemd.  However
genkernel-next-50 will not mount my /usr file system.  I have everything
on lvm volumes, except my /boot which is a regular partition.  With the
regular genkernel /usr is mounted, but I can't even test systemd
bedcause it looks for realinit before /usr is even mounted.  My
genkernel command line is:
genkernel --no-clean --no-splash --lvm --e2fsprogs
--kerneldir=/usr/src/linux-3.6.2-gentoo initramfs

Now when I use genkernel-next, it would not mount /usr because it said
no such file or directory -- I guess its mount point -- not sure of
that.  It would not execute udev because it said there was a missing
library.

So, how can this be fixed?  Is there a bug in genkernel-next?

Thanks in advance for any ideas.
-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

[gentoo-user] Re: genkernel-next will not mount /usr but genkernel will

[Greg Surbey]

 <covici <at> ccs.covici.com> writes:

> 
> Hi folks.  I wanted to switch to using genkernel-next instead of
> genkernel so eventually I could switch to using systemd.  However
> genkernel-next-50 will not mount my /usr file system.  I have everything
> on lvm volumes, except my /boot which is a regular partition.  With the
> regular genkernel /usr is mounted, but I can't even test systemd
> bedcause it looks for realinit before /usr is even mounted.  My
> genkernel command line is:
> genkernel --no-clean --no-splash --lvm --e2fsprogs
> --kerneldir=/usr/src/linux-3.6.2-gentoo initramfs
> 
> Now when I use genkernel-next, it would not mount /usr because it said
> no such file or directory -- I guess its mount point -- not sure of
> that.  It would not execute udev because it said there was a missing
> library.
> 
> So, how can this be fixed?  Is there a bug in genkernel-next?
> 
> Thanks in advance for any ideas.


Hi Covici,

I experienced a similar issue to yours and I thought I'd post a workaround
that worked for my situation.  What I did was add 'debug' as a kernel line
parameter so that the initramfs would drop me into a busybox commandline
before mounting the root file system.  I then went into /dev/vg/ and ran
this command 'ln -sf /dev/dm-0 usr'.  This changed the symbolic link from a
relative to an absolute path and thus fixed it so the mount command would
work correctly when called in the bootup script.  I typed 'exit' to continue
with the boot.

--
Greg Surbey

Re: [gentoo-user] Re: genkernel-next will not mount /usr but genkernel will

[covici]

Greg Surbey <gregsurbey@hotmail.com> wrote:

>  <covici <at> ccs.covici.com> writes:
> 
> > 
> > Hi folks.  I wanted to switch to using genkernel-next instead of
> > genkernel so eventually I could switch to using systemd.  However
> > genkernel-next-50 will not mount my /usr file system.  I have everything
> > on lvm volumes, except my /boot which is a regular partition.  With the
> > regular genkernel /usr is mounted, but I can't even test systemd
> > bedcause it looks for realinit before /usr is even mounted.  My
> > genkernel command line is:
> > genkernel --no-clean --no-splash --lvm --e2fsprogs
> > --kerneldir=/usr/src/linux-3.6.2-gentoo initramfs
> > 
> > Now when I use genkernel-next, it would not mount /usr because it said
> > no such file or directory -- I guess its mount point -- not sure of
> > that.  It would not execute udev because it said there was a missing
> > library.
> > 
> > So, how can this be fixed?  Is there a bug in genkernel-next?
> > 
> > Thanks in advance for any ideas.
> 
> 
> Hi Covici,
> 
> I experienced a similar issue to yours and I thought I'd post a workaround
> that worked for my situation.  What I did was add 'debug' as a kernel line
> parameter so that the initramfs would drop me into a busybox commandline
> before mounting the root file system.  I then went into /dev/vg/ and ran
> this command 'ln -sf /dev/dm-0 usr'.  This changed the symbolic link from a
> relative to an absolute path and thus fixed it so the mount command would
> work correctly when called in the bootup script.  I typed 'exit' to continue
> with the boot.

That is interesting, if true, there is a bug in genkernel-next -- I
wonder if they fixed it in 53 -- I was using -50.

Thanks for the hint.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com