[Mageia-dev] M3 won't complete boot after update

Anne Wilson annew at kde.org
Tue Sep 25 16:02:48 CEST 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sent yesterday, but not seen on-list, so apologies if this is a duplicate.

I finally got around to connecting my netbook, which has been running
Cauldron for some time.  This was fully up to date before my holidays,
and apart from the recent display problem (which as Angelo Naselli
suspected, is a KDE problem) it has behaved beautifully.  Today,
though, needed almost 3 weeks worth of updates, and when it finished,
it won't boot.

There are obviously problems with my remote mounts, but we are talking
in detail about that on another thread.  Mostly things look to be
going well up to that stage, then I see messages like

Started RPC bind service
Reached target Remote File Systems (Pre).
Mounting /mnt/QNAS-Lydgate-Data...
Mounting /mnt/borg2/home...
Mounting /mnt/borg2_Data1...
Reached target RPC Port Mapper.
Failed to mount /mnt/QNAS-Lydgate-Data.
See systemctl status /mnt-QNAS\x2dLydgate\x2dData.mount for details.
.... (other similar pairs of lines)
Dependency failed for Remote File Systems

After these lines, suddenly two of the QNAS mounts (one of which is
/mnt/QNAS/Lydgate-Data mentioned above) do succeed.  The two borg2
mounts still fail, as do some of the other QNAS mounts.

A few more lines, and all looks reasonable, until

[FAILED] Failed to start Wait for Plymouth Boot Screen to Quit

then
Reached target Multi-User
Reached target Graphical Interface

and there it freezes.

Later:

I tried booting from the older kernel.  On the graphical screen, it
appears to get a lot further, 5 bubbles instead of 2, but when I tried
it again watching the messages it appears to follow the same path as
the new kernel boot, ending at the same place.

Interestingly, though, the nfs mount that succeeds, after saying it
had failed, was not the same one as yesterdays.  Still, that's
probably a side-issue.

The situation now is that I appear to have a completely unusable M3.
The line

[DEPEND] Dependency failed for Remote File Systems

is obviously important.  Not knowing what that dependency is, I don't
know whether it could do more damage than failing to mount remote
systems.  It doesn't sound likely, but....

Anne
- - --
Need KDE help? Try
http://userbase.kde.org or
http://forum.kde.org
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBgssYACgkQj93fyh4cnBfLsQCfc533FaIzXCMGL3d/l6YRKWLF
UJIAnA7gmR5+6+MdTmLv1COAgYej6DIJ
=qnxG
- -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBhuX8ACgkQj93fyh4cnBcObQCggPTTm3Y+AYK3I1X368/KA63o
SLUAn34TkjeAz4nN4VWduE0VpHdJskUf
=DQKu
-----END PGP SIGNATURE-----


More information about the Mageia-dev mailing list