<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] 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%20M3%20won%27t%20complete%20boot%20after%20update&In-Reply-To=%3C5061CFB0.6080904%40kde.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="018921.html">
<LINK REL="Next" HREF="018925.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] 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%20M3%20won%27t%20complete%20boot%20after%20update&In-Reply-To=%3C5061CFB0.6080904%40kde.org%3E"
TITLE="[Mageia-dev] M3 won't complete boot after update">annew at kde.org
</A><BR>
<I>Tue Sep 25 17:37:20 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="018921.html">[Mageia-dev] M3 won't complete boot after update
</A></li>
<LI>Next message: <A HREF="018925.html">[Mageia-dev] M3 won't complete boot after update
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18924">[ date ]</a>
<a href="thread.html#18924">[ thread ]</a>
<a href="subject.html#18924">[ subject ]</a>
<a href="author.html#18924">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 25/09/12 15:41, Colin Guthrie wrote:
><i> 'Twas brillig, and Anne Wilson at 25/09/12 15:02 did gyre and
</I>><i> gimble:
</I>>><i> Sent yesterday, but not seen on-list, so apologies if this is a
</I>>><i> duplicate.
</I>>><i>
</I>>><i> I finally got around to connecting my netbook, which has been
</I>>><i> running Cauldron for some time. This was fully up to date
</I>>><i> before my holidays, and apart from the recent display problem
</I>>><i> (which as Angelo Naselli suspected, is a KDE problem) it has
</I>>><i> behaved beautifully. Today, though, needed almost 3 weeks worth
</I>>><i> of updates, and when it finished, it won't boot.
</I>>><i>
</I>>><i> There are obviously problems with my remote mounts, but we are
</I>>><i> talking in detail about that on another thread. Mostly things
</I>>><i> look to be going well up to that stage, then I see messages like
</I>>><i>
</I>>><i> Started RPC bind service Reached target Remote File Systems
</I>>><i> (Pre). Mounting /mnt/QNAS-Lydgate-Data... Mounting
</I>>><i> /mnt/borg2/home... Mounting /mnt/borg2_Data1... Reached target
</I>>><i> RPC Port Mapper. Failed to mount /mnt/QNAS-Lydgate-Data. See
</I>>><i> systemctl status /mnt-QNAS\x2dLydgate\x2dData.mount for details.
</I>>><i> .... (other similar pairs of lines) Dependency failed for Remote
</I>>><i> File Systems
</I>>><i>
</I>>><i> After these lines, suddenly two of the QNAS mounts (one of which
</I>>><i> is /mnt/QNAS/Lydgate-Data mentioned above) do succeed. The two
</I>>><i> borg2 mounts still fail, as do some of the other QNAS mounts.
</I>>><i>
</I>>><i> A few more lines, and all looks reasonable, until
</I>>><i>
</I>>><i> [FAILED] Failed to start Wait for Plymouth Boot Screen to Quit
</I>>><i>
</I>>><i> then Reached target Multi-User Reached target Graphical
</I>>><i> Interface
</I>>><i>
</I>>><i> and there it freezes.
</I>>><i>
</I>>><i> Later:
</I>>><i>
</I>>><i> I tried booting from the older kernel. On the graphical screen,
</I>>><i> it appears to get a lot further, 5 bubbles instead of 2, but when
</I>>><i> I tried it again watching the messages it appears to follow the
</I>>><i> same path as the new kernel boot, ending at the same place.
</I>>><i>
</I>>><i> Interestingly, though, the nfs mount that succeeds, after saying
</I>>><i> it had failed, was not the same one as yesterdays. Still, that's
</I>>><i> probably a side-issue.
</I>>><i>
</I>>><i> The situation now is that I appear to have a completely unusable
</I>>><i> M3. The line
</I>>><i>
</I>>><i> [DEPEND] Dependency failed for Remote File Systems
</I>>><i>
</I>>><i> is obviously important. Not knowing what that dependency is, I
</I>>><i> don't know whether it could do more damage than failing to mount
</I>>><i> remote systems. It doesn't sound likely, but....
</I>><i>
</I>><i> If the remote mounts are not critical, just add nofail to the
</I>><i> fstab options.
</I>><i>
</I>><i> I suspect strongly that any issues with these mounts is entirely
</I>><i> separate to the actual graphical boot.
</I>><i>
</I>Agreed. Adding nofail makes no difference. I've also tried removing
all options, down to a minimum defaults. However, they shouldn't stop
boot. FWIW, I'm still seeing that message about a dependency failure
for remote file systems.
><i> Personally, I was seeing crashes with qt4... perhaps try switching
</I>><i> to gdm as you're DM and see if the graphical boot comes up OK,
</I>><i> that way we could see easily if it's something high level.
</I>><i>
</I>No, gdm doesn't get that far either.
><i> Also you could try and look and see what systemctl status
</I>><i> prefdm.service says to you (you might need to switch to tty2).
</I>><i>
</I>prefdm.service - Display Manager
Loaded: loaded (/usr/lib/systemd/system/prefdm.service: static)
Active: inactive (dead)
CGroup: name=systemd:system/prefdm.service
(This from looking over my shoulder, so ignore any typos)
I'll worry about the mounts later - the first thing is to get the
system back :-)
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>
iEYEARECAAYFAlBhz60ACgkQj93fyh4cnBc0zACeKZNtAcz5uSSQurNldG3FP7kU
oRgAnjJuoMzcRLDM5R65apeiiwv0khpo
=Bs3x
-----END PGP SIGNATURE-----
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="018921.html">[Mageia-dev] M3 won't complete boot after update
</A></li>
<LI>Next message: <A HREF="018925.html">[Mageia-dev] M3 won't complete boot after update
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18924">[ date ]</a>
<a href="thread.html#18924">[ thread ]</a>
<a href="subject.html#18924">[ subject ]</a>
<a href="author.html#18924">[ 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>