After installing latest March-17 update on my rbp3-osmc-mediacenter-osmc-17.0.0-15: "Failed to start login service" is displayed

Hi,

When I started my RBP-3 I got a message “updates where not installed”. Then I manually checked for updates and installed it and it was successful without any issues. But after the reboot I am getting the error “Failed to start login service”. After 2-3 minuts home screen will appear. Some times again it will go back to the boot screen and I am getting the same “failed to start login service” error.

Please help.

Thanks,
Sivabalan K

Provide the URL returned by grab-logs -A please.

Problem logs:

Mar 23 09:58:56 SarveshMediaCenter systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Mar 23 09:58:56 SarveshMediaCenter dbus[288]: [system] Failed to activate service ‘org.freedesktop.systemd1’: timed out
Mar 23 09:58:56 SarveshMediaCenter systemd[1]: Failed to start Login Service.
Mar 23 09:58:56 SarveshMediaCenter systemd[1]: Unit systemd-logind.service entered failed state.
****Mar 23 09:58:56 SarveshMediaCenter systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
Mar 23 09:58:56 SarveshMediaCenter systemd[1]: Stopping Login Service…
Mar 23 09:58:56 SarveshMediaCenter systemd[1]: Starting Login Service…
Mar 23 09:58:56 SarveshMediaCenter dbus[288]: [system] Failed to activate service ‘org.freedesktop.UDisks’: timed out
Mar 23 09:58:56 SarveshMediaCenter udisks-glue[300]: Unable to enumerate the devices: Activation of org.freedesktop.UDisks timed out
Mar 23 09:58:56 SarveshMediaCenter systemd[1]: udisks-glue.service: main process exited, code=exited, status=1/FAILURE
Mar 23 09:58:56 SarveshMediaCenter systemd[1]: Unit udisks-glue.service entered failed state.
Mar 23 09:58:56 SarveshMediaCenter dbus[288]: [system] Failed to activate service ‘fi.w1.wpa_supplicant1’: timed out
Mar 23 09:58:56 SarveshMediaCenter dbus[288]: [system] Failed to activate service ‘org.freedesktop.hostname1’: timed out
Mar 23 09:59:02 SarveshMediaCenter nmbd[453]: [2017/03/23 09:59:02.473440, 0] …/source3/nmbd/nmbd_become_lmb.c:533(become_local_master_browser)
Mar 23 09:59:02 SarveshMediaCenter nmbd[453]: become_local_master_browser: Error - cannot find server SARVESHMEDIACENTER in workgroup WORKGROUP on subnet 10.100.7.3
Mar 23 09:59:10 SarveshMediaCenter dbus[288]: [system] Failed to activate service ‘org.freedesktop.login1’: timed out
Mar 23 09:59:10 SarveshMediaCenter dbus[288]: [system] Activating systemd to hand-off: service name=‘org.freedesktop.login1’ unit=‘dbus-org.freedesktop.login1.service’
Mar 23 09:59:21 SarveshMediaCenter dbus[288]: [system] Failed to activate service ‘org.freedesktop.systemd1’: timed out
Mar 23 09:59:21 SarveshMediaCenter systemd-logind[490]: Failed to enable subscription: Activation of org.freedesktop.systemd1 timed out
Mar 23 09:59:21 SarveshMediaCenter systemd-logind[490]: Failed to fully start up daemon: Connection timed out
Mar 23 09:59:21 SarveshMediaCenter systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Mar 23 09:59:21 SarveshMediaCenter systemd[1]: Failed to start Login Service.
Mar 23 09:59:21 SarveshMediaCenter systemd[1]: Unit systemd-logind.service entered failed state.
Mar 23 09:59:21 SarveshMediaCenter systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
Mar 23 09:59:21 SarveshMediaCenter systemd[1]: Stopping Login Service…
Mar 23 09:59:21 SarveshMediaCenter systemd[1]: Starting Login Service…

Full logs location:

log location

http://paste.osmc.io/ayixukurid

Around line 1293 od the debug log it says:

Mar 22 09:43:14 SarveshMediaCenter dbus-daemon[288]: Encountered error 'Error in file /etc/dbus-1/system.d/org.freedesktop.systemd1.conf, line 94, column 3: not well-formed (invalid token)
                                                     ' while parsing '/etc/dbus-1/system.d/org.freedesktop.systemd1.conf'

This is an XML parsing error and appears to have caused dbus problems later on: therre’s also a whole bunch of dbus-related errors later in the log.

Could you run the command:

md5sum /etc/dbus-1/system.d/org.freedesktop.systemd1.conf

and tell us what it returns?

As root:
root@SarveshMediaCenter:/home/osmc# md5sum /etc/dbus-1/system.d/org.freedesktop.systemd1.conf
6b7598e89fc8ff8f500d0485f1a8323d /etc/dbus-1/system.d/org.freedesktop.systemd1.conf
root@SarveshMediaCenter:/home/osmc#

As osmc user:
osmc@SarveshMediaCenter:~$ md5sum /etc/dbus-1/system.d/org.freedesktop.systemd1.conf
6b7598e89fc8ff8f500d0485f1a8323d /etc/dbus-1/system.d/org.freedesktop.systemd1.conf
osmc@SarveshMediaCenter:~$

Also one more issue today. My storage device got removed automatically. I disconnected and connected the 1TB HDD again but its not getting mounted.

Seems you version is being altered.

osmc@osmc:~$ md5sum /etc/dbus-1/system.d/org.freedesktop.systemd1.conf
46533268285a0df22b1f1667ddc05642 /etc/dbus-1/system.d/org.freedesktop.systemd1.conf

Provide ouput of cat /etc/dbus-1/system.d/org.freedesktop.systemd1.conf | paste-log

While it may or may not be related to the dbus issues you but first think to ensure that your power supply is up to the job.

Is the 1TB HDD on a powered hub or connected directly to the Pi3? It is generally unwise to connect an external HDD directly to a Pi.

And, as @fzinken has already noted, the md5 hash for the dbus XML file is incorrect, suggesting some kind of file corruption. Unfortunately, there is a reasonable chance that the corruption is not limited to only one file. That said, I’d probably try to fix the XML file first and see how it goes before considering a complete reinstall.

Edit: Here is the correct XML file http://paste.osmc.io/pijigusowi Before you overwrite the bad file, don’t forget to follow fzinken’s instructions and let us see the bad file.

I am using Samsung 2A mobile charger and my 1TB HDD is separately powered.

Sure thanks!! Will follow the instructions.

That’s not sufficient and the PSU likely doesn’t provide 2A.

1 Like

I am from India and please suggest me a good power supply that is compatible with RBP3.

Thanks,
Sivabalan K

1 Like

http://paste.osmc.io/elizodinij

Thanks!!

The file is corrupted towards the end which could indicate a file system corruption. I suggest a reinstall best on a new SD card.

You mean I have to change the SD card?? I had bought a new SD card for this :frowning:

Well the only other explanation for a filesystem corruption is that you have unplugged the power without shutting down the Pi!

No, not necessarily… Just reinstall.

1 Like

Sure thanks!!

Guys Have reinstalled the latest OSMC and everything is fine. Now I am ensuring an disk image backup and settings backup. :slight_smile: