You are not logged in.
I'm attempting to install the hydrogen release on my laptop. In my most recent attempt I have run the 64-bit install from a CDROM. Once the install completed, I installed a few packages (nfs, tcsh, etc.) but the installation is still pretty minimal. I was having trouble with the ethernet connection, but this problem has been fixed. I tried to reboot again. During the reboot, the process failed into 'emergency mode'.
The runtime error message that came up is:
...
Starting Update UTMP about System Boot/Shutdown
[FAILED] to start Update UTMP about System Boot/Shutdown
See 'systemctl status systemd-update-utmp.service' for details.
[DEPEND] Dependency failed for Update about System Runlevel Changes.
...
I ran 'systemctl status systemd-update-utmp.service' with the output:
systemd-update-utmp.service - Update UTMP about System Boot/Shutdown
Loaded: loaded (/lib/systemd/system/systemd-update-utmp.service; static)
Active: failed (Result: exit-code) since Sun 2016-07-03 08:00:22 EDT; 19min ago
Docs: man:systemd-update-utmp.service(8)
man:utmp(5)
Process: 358 ExecStart=/lib/systemd/systemd-update-utmp reboot (code=exited, status=1/FAILURE)
Main PID: 358 (code=exited, status=1/FAILURE)
Jul 03 08:00:22 furillo systemd[1]: systemd-update-utmp.service: main process exited, code=exited, status=1/FAILURE
Jul 03 08:00:22 furillo systemd[1]: Failed to start Update UTMP about System Boot/Shutdown.
Jul 03 08:00:22 furillo systemd[1]: Unit systemd-update-utmp.service entered failed state.
I did internet searches for 'Failed to start Update UTMP about System Boot/Shutdown' and got some hits, but they did not look comparable to my current problem. For example, one person got this message when their tmp file system got filled up (mine is not).
Are they any ideas on why 'Update UTMP about System Boot/Shutdown' is failing?
Jim A.
Last edited by jjanderson5 (2016-07-03 14:38:07)
Offline
During the reboot, the process failed into 'emergency mode'.
I've never seen this mode. Do you mean this?
http://i.stack.imgur.com/7Dhyo.jpg
If so does journalctl give you anything?
What hardware do you have (computer name and model)?
I don't care what you do at home. Would you care to explain?
Offline
Please check your journal for utmp-related errors, and ensure that /var/run is a symlink to /run. The program that failes is https://github.com/systemd/systemd/blob … ate-utmp.c which is actually pretty trivial.
Offline
@hhh
I've never seen this mode. Do you mean this?
http://i.stack.imgur.com/7Dhyo.jpg
If you look at 7Dhyo.jpg, it say's 'Welcome to emergency mode!' Yes, when I see that, I am in emergency mode.
If so does journalctl give you anything?
No. It gives me the error message, but if I search on 'UTMP' or 'utmp' in the journal, there is no other reference to it.
What hardware do you have (computer name and model)?
I have an Asus X551M Notebook PC
Offline
@nobody
Please check your journal for utmp-related errors, and ensure that /var/run is a symlink to /run. The program that failes is https://github.com/systemd/systemd/blob … ate-utmp.c which is actually pretty trivial.
I have checked the journal and I don't see earlier utmp related errors. Also, I checked and /var/run is a symlink to /run.
Because the journal has no earlier error messages about 'utmp', I am wondering if the one other error message prior to the UTMP error, may put the system in a state where UTMP fails. The earlier message is:
failed to execute '/lib/udev/mtp-probe' 'mtp-probe /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1 1 2': No suce file of directo
[the rest of the message got clipped]
P.S. If I don't leave my computer now, my wife is going to shoot me because we have a commitment this afternoon. I will get back to this ASAP, but it will likely be 24 hours. It is not my lack of interest, but survival that takes me away - my apologies
Offline