Gentoo Archives: gentoo-user

From: covici@××××××××××.com
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] problems getting systemd to work
Date: Thu, 15 May 2014 11:50:18
Message-Id: 4040.1400154609@ccs.covici.com
In Reply to: Re: [gentoo-user] problems getting systemd to work by "Canek Peláez Valdés"
1 Canek Peláez Valdés <caneko@×××××.com> wrote:
2
3 > On Thu, May 15, 2014 at 1:18 AM, Canek Peláez Valdés <caneko@×××××.com> wrote:
4 > > On Wed, May 14, 2014 at 5:26 PM, <covici@××××××××××.com> wrote:
5 > > [snip]
6 > >>
7 > >> Well, the workaround sort of worked -- it went through the initrd -- I
8 > >> had debug in the kernel command line, but it did not stop for nothing!
9 > >> When it went to the real root, however it did not activate any of the
10 > >> lvm volumes I had except for what I specified in the kernel command
11 > >> line, causing things not to work well. Also, I noticed that if insisted
12 > >> on using the predictable network names, even though I have
13 > >> /etc/udev/rules.d/70-persistent-net.rules and
14 > >> /etc/udev/rules.d/80-name-slot.rules which work fine in openrc to give
15 > >> me back my eth* names. So all in all, it was a mess and took me to an
16 > >> emergency shell and that was the end of that. I did eventually activate
17 > >> some volumes by lvchange -aay, but obviously that would not work well.
18 > >
19 > > OK, I was a little mystified about why dracut-036 worked on my system
20 > > and 037 didn't. Before I tried any workaround, I wanted to know what
21 > > changed from the previous version to the current one.
22 > >
23 > > So I generated an initramfs with dracut-036-r4 and another one with
24 > > dracut-037-r1, and I tried to see what changed from one to the other.
25 > > The answer is surprisingly easy: in /etc/cmdline.d/, the following
26 > > files where in the 036-r4 version, but not in the 037-r4:
27 > >
28 > > 90crypt.conf
29 > > 90lvm.conf
30 > > 90mdraid.conf
31 > > base.conf
32 > >
33 > > Te contents of those files are (90crypt.conf is empty):
34 > >
35 > > 90lvm.conf
36 > > rd.lvm.lv=vg/vol1
37 > > rd.lvm.lv=vg/vol4
38 > > rd.lvm.lv=vg/vol3
39 > >
40 > > 90mdraid.conf
41 > > rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12
42 > >
43 > > base.conf
44 > > ro
45 > >
46 > > So I just changed my /etc/default/grub file:
47 > >
48 > > GRUB_CMDLINE_LINUX="init=/usr/lib/systemd/systemd quiet nosplash
49 > > rd.lvm.lv=vg/vol1 rd.lvm.lv=vg/vol4 rd.lvm.lv=vg/vol3
50 > > rd.md.uuid=f4a59e68:fbe4039f:a39fc86d:e9e91e12"
51 > >
52 > > I regenerated my GRUB2 config, and now again my LVM test system works
53 > > perfectly with the latest dracut version.
54 >
55 > I'm an idiot; I didn't saw the documentation about hostonly_cmdline;
56 > BTW Jc, you used host_cmdline, I think the former is the correct one.
57 >
58 > So, to resume: there is no bug, is just that before hostonly_cmdline
59 > was yes by default, and now is no by default. This change was
60 > documented, but I failed to notice it (and I think the ebuild in
61 > Gentoo should print an einfo message).
62 >
63 > Anyway, I think that explains all my problems; John, I don't know if
64 > it will solve yours. Again: did you used "dracut --print-cmdline" to
65 > get the command line? Also, have you tried to use -H to generate your
66 > initramfs? And finally, have you tried with --hostonly-cmdline?
67
68 OK, I was looking through the journal output and I think the key to the
69 lvm's not activating is the following:
70 4 12:54:57 ccs systemd[1]: Got notification message for unit
71 systemd-journald.service
72 4 12:54:57 ccs systemd[1]: systemd-journald.service: Got notification
73 message from PID 1750 (WATCHDOG=1...)
74 4 12:54:57 ccs systemd[1]: systemd-journald.service: got WATCHDOG=1
75 4 12:54:57 ccs systemd[1]: Received SIGCHLD from PID 2603 (lvm).
76 4 12:54:57 ccs systemd[1]: Child 2602 (lvm) died (code=exited,
77 status=5/NOTINSSTALLED)
78 4 12:54:57 ccs systemd[1]: Child 2603 (lvm) died (code=exited,
79 status=5/NOTINSSTALLED)
80 4 12:54:57 ccs systemd[1]: Child 2610 (lvm) died (code=exited,
81 status=5/NOTINSSTALLED)
82 4 12:54:57 ccs systemd[1]: Job
83 dev-mapper-linux\x2d\x2dfiles\x2dportage.device/start timed out.
84
85 So what is not installed?
86
87 Also, for the first two lines, I get hundreds of thatpair of lines, how
88 can I prevent such.
89 So, between the lvm problem and the udev renaming my eth0 devices these
90 are the key as to why things are going wrong -- with openrc udev is not
91 renaming eth0 at all.
92
93
94 --
95 Your life is like a penny. You're going to lose it. The question is:
96 How do
97 you spend it?
98
99 John Covici
100 covici@××××××××××.com

Replies

Subject Author
Re: [gentoo-user] problems getting systemd to work "Stefan G. Weichinger" <lists@×××××.at>