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