Gentoo Archives: gentoo-user

From: Mike Kazantsev <mk.fraggod@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] lvm problem -- is timing?
Date: Sat, 20 Jun 2009 05:36:17
Message-Id: 20090620113338.7d78293c@coercion
In Reply to: [gentoo-user] lvm problem -- is timing? by Maxim Wexler
1 On Fri, 19 Jun 2009 22:15:12 -0600
2 Maxim Wexler <maxim.wexler@×××××.com> wrote:
3
4 > Seems if I add the commands:
5 >
6 > vgscan --mknodes
7 > vgchange -a y
8 > mount -a
9 >
10 > to /etc/conf.d/bootmisc and add it to the boot runlevel, the eee boots
11 > to a coherent system BUT not before going through LVM failure, errors,
12 > inability to find volumes etc through many console lines until just
13 > after the line:
14 >
15 > *Configuring kernel parameters...
16 >
17 > comes
18 >
19 > Reading all physical volumes. This may take a while...
20 > Found volume group "vg" using metadata type lvm2
21 > 5 logical volume(s) in volume group "vg" now active
22 > ...
23 >
24 > And everything is fine after that. So it looks like a question of
25 > timing, of executing bootmisc or something like it earlier, say just
26 > after loading dm-mod and dm-crypt and just before the line in the
27 > console:
28 >
29 > *Setting up the Logical Volume Manager...
30 >
31 > When it all starts to fall apart.
32 >
33 > FWIW I'm using baselayout-2.
34
35 I've had such problem in the past, even filed the bug:
36
37 http://bugs.gentoo.org/show_bug.cgi?id=255237
38
39 For me, the problem was that "device-mapper" initscript started after
40 "lvm".
41
42 I believe there's "after device-mapper" line already in lvm-2.02.45, so
43 it should run fine, but as an additional precaution I have dm-crypt
44 script at sysinit runlevel, which starts device-mapper and dm-crypt
45 before lvm or even it's runlevel (boot).
46
47 It makes sense for me, since some lvm pv's (not root) are actually on
48 encrypted partitions, although I mount these even earlier, but should
49 initrd become incompatible w/ latest kernel, dm-crypt should do the job
50 instead.
51 Guess you can do the same, at least if you don't have dm-crypt
52 mappings, or you can try adding device-mapper to sysinit level directly.
53
54
55 Here's my boot sequence (from rc.log):
56
57
58 rc sysinit logging started at Fri Jun 12 04:24:55 2009
59
60 OpenRC 0.4.3 is starting up Gentoo Linux (i686)
61
62 Press I to enter interactive boot mode
63
64 * Mounting /proc...
65 [ ok ]
66 * Mounting /sys...
67 [ ok ]
68 * Mounting debug filesystem...
69 [ ok ]
70 * Mounting /dev...
71 [ ok ]
72 * Starting udevd...
73 [ ok ]
74 * Populating /dev with existing devices through uevents...
75 [ ok ]
76 * Waiting for uevents to be processed...
77 [ ok ]
78 * Mounting /dev/pts...
79 [ ok ]
80 * Mounting /dev/shm...
81 [ ok ]
82 * device-mapper uses addon code which is deprecated
83 * and may not be available in the future.
84 * Setting up dm-crypt mappings...
85 * dm-crypt mapping lvcrypt is already configured
86 [ ok ]
87
88 rc sysinit logging stopped at Fri Jun 12 04:24:55 2009
89
90
91 rc boot logging started at Fri Jun 12 04:24:55 2009
92
93 * Setting system clock using the hardware clock [Local Time]...
94 [ ok ]
95 * Autoloaded 0 module(s)
96 * lvm uses addon code which is deprecated
97 * and may not be available in the future.
98 * Setting up the Logical Volume Manager...
99 Locking type -1 initialisation failed.
100 [ ok ]
101 * Checking local filesystems ...
102 ...
103
104
105
106 --
107 Mike Kazantsev // fraggod.net

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-user] lvm problem -- is timing? Dirk Heinrichs <dirk.heinrichs@××××××.de>
Re: [gentoo-user] lvm problem -- is timing? Maxim Wexler <maxim.wexler@×××××.com>