Bug 15979

logs, ... ?

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud

Hi Bobby,

I'm not sure re-installing is needed, maybe you installed only part of a set of packages that depend on each other, because the rest hadn't landed on your mirror, yet?

If you login to runlevel 3, the network should come up and you should be able to run (as root) "urpmi --auto-update" to fetch any missing packages.

If that fixes the issue, please tell us.

Anyway, for this bug report, please also run (as root):

journalctl --since="2015-05-18" > journalctl.txt

(assuming you installed the updates on the 18th, if it was longer ago then change the date accordingly, but keep the yyyy-mm-dd format)

and attach journalctl.txt to this report.

Cheers,
Marja

CC: (none) => marja11

Created attachment 6584 [details]
journalctl.txt

The log shows updates being installed that were released several months ago.  I am guessing that this was a fresh installation from an ISO that was then updated.  It's not clear at all what exactly was not working.  There wasn't an apparent issue in the log.  Please be more specific about exactly what was not working as expected and what you see.

Summary: updates this afternoon Monday, May 18, 2015 => unspecified issue on Mageia 4 system

I'd be interested to see the contents of /etc/fstab.

Bobbie, please post your comments to this bug and don't e-mail me directly.

He sent me this:

        I installed some updates yesterday afternoon and then put my
machine
into hibernation for a 40 minute ride to the SF-LUG meeting place,
    When i set up the notebook for the meeting it would not reboot.
    And when I tried each time to get it to reboot it ended up in the same
position telling about journalctl and various commands.

    It gave me two choices hit Cntl-D to continue or log in as root.
    Everytime I hit Cntl - D it went back to the same remarks,

    Finally i logged in a root and started the desktop environment.
I wanted to check the disk to see if I could figure out what had
gone wrong, but MCC would not start.

    I had noted the drak tools in the updates so I decided that was
connected to the problem.  Whether the updates were incomplete
or not I did not know/

    From the root desktop I got my password from my home directory
and filed the report.
    When I got home I re-installed.
    I am still setting up the system as I prefer it this morning.

    I hope that is enough information because I do not have any more.

    bliss

It is hard to narrow down what could have contributed to the problem when the updates shown as being installed date back at least as far as six months ago.  You really should install updates more often.

We would also need to know what the error message was as it booted into single-user mode it sounds; what caused it to do this.  That's something you would have seen on the screen, the journal would not show that.

As the system is now being reinstalled, this information can't be recovered and we can't do anything with this bug report.  If you have problems again, please give the needed details.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Just FYI he e-mailed me again.

        The system was re-installed last night.
    It had had updates done as they appeared,
for the last year or so.
    I tried to get more updates after the re-install
  last night but no luck with that even after I chose
all the mirrors that I use.


    This has been my practice since I started using Mandriva
about 2006.
    Marja has given me some information that may help with
future problems as has David W. Hodgins in the Usenet
newsgroup,  alt.os.linux.mageia.
    If you read the note I submitted I got a fresh batch
yesterday afternoon and installed them.  After that
it refused to boot.

    No I have more updates waiting but taking Hodgins advice
I will wait a while before I attempt to install.  Meantime I lost
about 4 hours of sleep and rest last night and for an old lady
that is making me ill.

    bliss

CC: (none) => luigiwalser