1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] System doen't boot with LVM
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20System%20doen%27t%20boot%20with%20LVM&In-Reply-To=%3C51223992.8020309%40colin.guthr.ie%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="022944.html">
<LINK REL="Next" HREF="022946.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] System doen't boot with LVM</H1>
<B>Colin Guthrie</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20System%20doen%27t%20boot%20with%20LVM&In-Reply-To=%3C51223992.8020309%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] System doen't boot with LVM">mageia at colin.guthr.ie
</A><BR>
<I>Mon Feb 18 15:24:18 CET 2013</I>
<P><UL>
<LI>Previous message: <A HREF="022944.html">[Mageia-dev] System doen't boot with LVM
</A></li>
<LI>Next message: <A HREF="022946.html">[Mageia-dev] System doen't boot with LVM
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#22945">[ date ]</a>
<a href="thread.html#22945">[ thread ]</a>
<a href="subject.html#22945">[ subject ]</a>
<a href="author.html#22945">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and Olivier Thauvin at 18/02/13 12:48 did gyre and gimble:
><i> So ok, I just update my freshly installed mga2 to cauldron using network
</I>><i> install (live upgrade don't work, it seems urpmi fail to find a way to
</I>><i> update the system w/o filesystem).
</I>><i>
</I>><i> I have the exact same result: it don't boot.
</I>
Hmm, re: live upgrade are you meaning just a urpmi based upgrade? If so,
I've done a few similar updates in the last week or so in VMs and it's
always been OK. I presume you installed the mageia-prepare-upgrade
package from mga2/core/updates_testing, rebooted to the boot menu entry
created by that package before upgrading?
If so, please detail the process you went through and at which point if
failed so I can debug this process more. I've not had many complaints
about it, and it's worked for a variety of different filesystems
structures for me, so I'm surprised it's failing here.
Regarding the network install based upgrade there may be issues relating
to bootloader config tools (in drakx) that related the use of the blkid
cache which might make it miss the whole LVM volume (I've seen it
manifest itself as putting "root=/dev/" into grubs menu.lst rather than
"root=/dev/mapper/foo").
I've fixed the calls in drakxtools, but it'll need a release to
propagate it through to stage2 used there which I don't think has been
done yet. I'll try and prep that tonight.
><i> * Colin Guthrie (<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>) wrote:
</I>>><i>
</I>>>><i> Dracut gi a shell, It seems 'lvm vgmknodes' has no effect (the swap lv
</I>>>><i> did existed already).
</I>>><i>
</I>>><i> In the dracut shell, what does /etc/cmdline.d/lvm.conf say? It should
</I>>><i> contain enough info to brink up both the root and the swap lvm.
</I>><i>
</I>><i> rd.lvm.lv=sagittarius/swap
</I>
OK, so this basically means that only the swap partition is configured
to be activated in the initrd (which is also what you observe so at
least it's behaving at that level!)
The problem is that dracut itself is not detecting that the LV needs
activating when it runs.
In order to get a booting system, just pass "rd.lvm.lv=sagitarius/slash"
on the command line (obviously substituting the real name of your
logical volume). This should make dracut initialise the lvm automatically.
You should (at least in theory) also just be able to type something like
"lvm vgchange -ay" into the dracut shell, then type exit (perhaps twice)
to continue the boot process.
Of course if your grub menu entry has been messed up (root=/dev/) then
you'll need to fix that up too.
Hopefully that should get you booting.
Col
--
Colin Guthrie
colin(at)mageia.org
<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
Day Job:
Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
Open Source:
Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="022944.html">[Mageia-dev] System doen't boot with LVM
</A></li>
<LI>Next message: <A HREF="022946.html">[Mageia-dev] System doen't boot with LVM
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#22945">[ date ]</a>
<a href="thread.html#22945">[ thread ]</a>
<a href="subject.html#22945">[ subject ]</a>
<a href="author.html#22945">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
