diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-September/018978.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-September/018978.html | 185 | 
1 files changed, 185 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-September/018978.html b/zarb-ml/mageia-dev/2012-September/018978.html new file mode 100644 index 000000000..2f8b2ebe6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-September/018978.html @@ -0,0 +1,185 @@ +<!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=%3C50641947.4050700%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="018974.html"> +   <LINK REL="Next"  HREF="018981.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> +   <H1>[Mageia-dev] Fwd: Re:  M3 won't complete boot after update</H1> +    <B>Colin Guthrie</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=%3C50641947.4050700%40colin.guthr.ie%3E" +       TITLE="[Mageia-dev] Fwd: Re:  M3 won't complete boot after update">mageia at colin.guthr.ie +       </A><BR> +    <I>Thu Sep 27 11:15:51 CEST 2012</I> +    <P><UL> +        <LI>Previous message: <A HREF="018974.html">[Mageia-dev] Fwd: Re:  M3 won't complete boot after update +</A></li> +        <LI>Next message: <A HREF="018981.html">[Mageia-dev] Fwd: Re:  M3 won't complete boot after update +</A></li> +         <LI> <B>Messages sorted by:</B>  +              <a href="date.html#18978">[ date ]</a> +              <a href="thread.html#18978">[ thread ]</a> +              <a href="subject.html#18978">[ subject ]</a> +              <a href="author.html#18978">[ author ]</a> +         </LI> +       </UL> +    <HR>   +<!--beginarticle--> +<PRE>'Twas brillig, and Anne Wilson at 27/09/12 09:46 did gyre and gimble: +><i> On 26/09/12 16:12, Marja van Waes wrote: +</I>>><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>><i>  +</I>><i> At this point I'm probably stuck.  I've been doing these tests by +</I>><i> forcing a level 1 boot, but now even that may not be possible.  These +</I>><i> are the latest boot messages: +</I> +Does it work when forcing a runlevel 3 boot instead. This is closer to a +proper boot and likely a better testing environment. I presume the +getty's are showing for you in level 3? + +><i> broadcom-wl (....)Already exists on this kernel [OK] +</I>><i> Checking for new hardwareWelcome to rescue mode! Type "systemctl +</I>><i> default" or ^D to enter default mode ##Yes, that's how it looks, lines +</I>><i> joined. +</I> +Interesting that they are joined up... + +><i> Type "journalctl" to show system logs. Type "systemctl reboot" to +</I>><i> reboot. [OK] +</I>><i> ##didn't do any of these as I was not watching the screen +</I>><i>  +</I>><i> Failed to issue method call: Transaction is destructive. +</I> +I've seen this before, but it's basically indicative of some kind of +transaction ordering deadlock. I'll investigate to see if I can +reproduce that here. + +I have seen it when you have SINGLE=/sbin/sulogin rather than +SINGLE=/sbin/sushell in /etc/sysconfig/init. + +><i> Last resort - +</I>><i>  +</I>><i> I edited out the "splash quiet" and called for level 1 again.  This +</I>><i> time it completes, very quickly. +</I>><i>  +</I>><i> 'systemctl show prefdm.service | grep ActiveEnter.*Mono" ' simply +</I>><i> returns to the prompt. +</I> +This shouldn't happen. These should be printed even if they have zero +values I believe, although with a level 1 or level 3 boot this might not +be the case (I've not tested). It would certainly *always* be 0 if they +are shown tho', + +The results of this test are only really valuable if you do a normal +boot to runlevel 5 as this is when the service should be started. + +What I'm trying to work out here is if the job relating to starting the +prefdm.service had to be ejected due to some kind of conflict. + +If there is a conflict then the values will be 0 and this will explain +why your graphical desktop does not start. + +><i> All the borg2 mounts are commented out for now. +</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>><i>  +</I>><i> Nothing at all happens.  It returns to the prompt. +</I> +This is curious. Does this also occur at runelevel 3? What does +systemctl status prefdm.service tell you after it returns you to the prompt? + +Is there anything useful in the kdm log file about why kdm failed to +launch X11? + +><i> We have all spent a lot of time on this.  There are files on the +</I>><i> netbook that I must recover, so now it's decision time.  It would +</I>><i> probably be easier and quicker to grab the latest image (in which case +</I>><i> can you remind me where to go for that) but I am willing to continue +</I>><i> if there is any possibility that what we discover could save grief for +</I>><i> others. +</I>><i>  +</I>><i> What do you think? +</I> +Plenty more to debug if you want to continue. + +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="018974.html">[Mageia-dev] Fwd: Re:  M3 won't complete boot after update +</A></li> +	<LI>Next message: <A HREF="018981.html">[Mageia-dev] Fwd: Re:  M3 won't complete boot after update +</A></li> +         <LI> <B>Messages sorted by:</B>  +              <a href="date.html#18978">[ date ]</a> +              <a href="thread.html#18978">[ thread ]</a> +              <a href="subject.html#18978">[ subject ]</a> +              <a href="author.html#18978">[ 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>  | 
