Canek Peláez Valdés <[email protected]> wrote:
> On Wed, May 14, 2014 at 10:55 AM, Jc García <[email protected]> wrote:
> > 2014-05-14 9:51 GMT-06:00 Canek Peláez Valdés <[email protected]>:
> >> On Wed, May 14, 2014 at 10:42 AM, <[email protected]> wrote:
> >>> Canek Peláez Valdés <[email protected]> wrote:
> >>>
> >>>> On Wed, May 14, 2014 at 10:05 AM, <[email protected]> wrote:
> >>>> [snip]
> >>>> > I am using version 037 and the command line was very simple
> >>>>
> >>>> As I told you in [1], the 037 version has problems with LVM; please
> >>>> also check the thread in [2], specially the post in [3].
> >>>>
> >>>> Please try again with dracut-036-r4.
> >>>>
> >>>> Regards.
> >>>>
> >>>> [1] http://article.gmane.org/gmane.linux.gentoo.user/274340
> >>>> [2] http://thread.gmane.org/gmane.linux.gentoo.user/274152
> >>>> [3]
> >>>> http://www.mail-archive.com/[email protected]/msg145647.html
> >>>> (for some reason it doesn't appear in gmane).
> >>> portage won't let me downgrade unless I downgrade systemd to 2.10 --
> >>> should I do that?
> >>
> >> You mean 210. I'm on 208; my LVM test system is basically stable.
> >>
> >> However Jc says he's got it to work with dracut 037-r1; perhaps try
> >> that version first?
> >>
> >> What I do know is that with dracut 037, me and Stefan ran intro troubles.
> >>
> > I described it as a 'workaround' in my first post, aware of the fact
> > that the behavior is not normal, but dracut acctually gives help
> > finding this workaround, wich is telling the kernel what LVs to use at
> > boot.
>
> Sorry, I forgot about that.
>
> I just tried my test LVM system with dracur-037-r1 and it didn't work.
> I have not tried yet your workaround, but there is obviously something
> fishy going on with the latest version of dracut; I would stay with
> 036-r4.
>
> I will try your workaround, although my system is a little more
> complicated, since it uses RAID and LUKS besides LVM.
Well, the workaround sort of worked -- it went through the initrd -- I
had debug in the kernel command line, but it did not stop for nothing!
When it went to the real root, however it did not activate any of the
lvm volumes I had except for what I specified in the kernel command
line, causing things not to work well. Also, I noticed that if insisted
on using the predictable network names, even though I have
/etc/udev/rules.d/70-persistent-net.rules and
/etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
me back my eth* names. So all in all, it was a mess and took me to an
emergency shell and that was the end of that. I did eventually activate
some volumes by lvchange -aay, but obviously that would not work well.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
[email protected]
