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
150
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Fwd: Re: M3 won't complete boot after update
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Fwd%3A%20Re%3A%20%20M3%20won%27t%20complete%20boot%20after%20update&In-Reply-To=%3C50641277.50505%40kde.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="019051.html">
<LINK REL="Next" HREF="018978.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Fwd: Re: M3 won't complete boot after update</H1>
<B>Anne Wilson</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Fwd%3A%20Re%3A%20%20M3%20won%27t%20complete%20boot%20after%20update&In-Reply-To=%3C50641277.50505%40kde.org%3E"
TITLE="[Mageia-dev] Fwd: Re: M3 won't complete boot after update">annew at kde.org
</A><BR>
<I>Thu Sep 27 10:46:47 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="019051.html">[Mageia-dev] ANNOUNCE: RPM group Policy change taking effect
</A></li>
<LI>Next message: <A HREF="018978.html">[Mageia-dev] Fwd: Re: M3 won't complete boot after update
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18974">[ date ]</a>
<a href="thread.html#18974">[ thread ]</a>
<a href="subject.html#18974">[ subject ]</a>
<a href="author.html#18974">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 26/09/12 16:12, Marja van Waes wrote:
><i> Can you try doing "systemctl show prefdm.service | grep
</I>><i> ActiveEnter.*Mono" after a fresh boot.
</I>><i>
</I>><i> I don't need to know the results, just whether it's non-zero or
</I>><i> still at 0.
</I>><i>
</I>><i> Assuming it's still at zero, then we've not even tried to start the
</I>><i> graphical server.
</I>><i>
</I>><i> I suspect this is because we're considering your remote mounts as
</I>><i> critical to the user sessions (i.e. think of /home on NFS).
</I>><i> Normally, putting nofail in the fstab is enough to break this
</I>><i> linkage.
</I>><i>
</I>><i> Can you comment out all remote mounts entirely and see if you can
</I>><i> boot.
</I>><i>
</I>><i> If it still fails, then try starting prefdm.service manually
</I>><i> (systemctl start prefdm.service) and see what happens.
</I>
At this point I'm probably stuck. I've been doing these tests by
forcing a level 1 boot, but now even that may not be possible. These
are the latest boot messages:
broadcom-wl (....)Already exists on this kernel [OK]
Checking for new hardwareWelcome to rescue mode! Type "systemctl
default" or ^D to enter default mode ##Yes, that's how it looks, lines
joined.
Type "journalctl" to show system logs. Type "systemctl reboot" to
reboot. [OK]
##didn't do any of these as I was not watching the screen
Failed to issue method call: Transaction is destructive.
Last resort -
I edited out the "splash quiet" and called for level 1 again. This
time it completes, very quickly.
'systemctl show prefdm.service | grep ActiveEnter.*Mono" ' simply
returns to the prompt.
All the borg2 mounts are commented out for now.
><i> If it still fails, then try starting prefdm.service manually
</I>><i> (systemctl start prefdm.service) and see what happens.
</I>
Nothing at all happens. It returns to the prompt.
We have all spent a lot of time on this. There are files on the
netbook that I must recover, so now it's decision time. It would
probably be easier and quicker to grab the latest image (in which case
can you remind me where to go for that) but I am willing to continue
if there is any possibility that what we discover could save grief for
others.
What do you think?
Anne
- --
Need KDE help? Try
<A HREF="http://userbase.kde.org">http://userbase.kde.org</A> or
<A HREF="http://forum.kde.org">http://forum.kde.org</A>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - <A HREF="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</A>
iEYEARECAAYFAlBkEnMACgkQj93fyh4cnBe+EQCbBZPomC7KFvGJBLesO1GrTp7o
ZdAAn1V0Y427s9UMhjDN6LAPdPA8kHFX
=15Wv
-----END PGP SIGNATURE-----
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="019051.html">[Mageia-dev] ANNOUNCE: RPM group Policy change taking effect
</A></li>
<LI>Next message: <A HREF="018978.html">[Mageia-dev] Fwd: Re: M3 won't complete boot after update
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18974">[ date ]</a>
<a href="thread.html#18974">[ thread ]</a>
<a href="subject.html#18974">[ subject ]</a>
<a href="author.html#18974">[ 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>
|
