Booting fails after fail of shutdown - I need help with the logs

Hello friends,

my beloved system failes on starting up and I don't get that fixed.

Setup: T430s with newest Manjaro 64 and XFCE, Linux 4.9.58-1-MANJARO

After a shutdown got caught in a loop I interrupted it by pressing the on/off button for 3 seconds.
Now when starting up, grub finds the right entry, the kernel gets loaded and the the manjaro screen with the dots - before the loginscreen - gets stuck for at least hours with the dots still blinking, I don't believe time would fix that.

  • I reinstalled grub in a chroot session - no success
  • I ran the latest update including some critical stuff like systemd (update from 10/29) in another chroot session - no success

I didn't install anything between the last working session and the one that failed at shutdown, I was just - unsuccessfully - trying to make the macros of an .xlsm spreadsheet work properly

There are no logs with journalctl from the failed startups, but from the shutdown, that failed and the one before that worked. Now I'm obviously not deep enough into systemd to interprete these logs, maybe someone has had this difference before?

Last logs of the failed shutdown (I took out a usbstick, after a fiew minutes of not shutting down)

Nov 02 12:26:49 manjaro NetworkManager[500]: <info>  [1509622009.0866] manager: NetworkManager state is now DISCONNECTED
Nov 02 12:26:49 manjaro dbus[498]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.serv
Nov 02 12:26:49 manjaro dbus[498]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is
Nov 02 12:26:49 manjaro NetworkManager[500]: <warn>  [1509622009.0883] sup-iface[0x56475dcdb400,wlp3s0]: connection disconnected (reason -3)
Nov 02 12:26:49 manjaro NetworkManager[500]: <info>  [1509622009.0884] device (wlp3s0): supplicant interface state: completed -> disconnected
Nov 02 12:26:49 manjaro NetworkManager[500]: <info>  [1509622009.1013] ModemManager disappeared from bus
Nov 02 12:27:33 manjaro kernel: usb 3-2: USB disconnect, device number 2

The Equivalent of the last working shutdown

Nov 02 11:43:18 manjaro NetworkManager[491]: <info>  [1509619398.1118] manager:     NetworkManager state is now DISCONNECTED
Nov 02 11:43:18 manjaro NetworkManager[491]: <info>  [1509619398.1125] caught SIGTERM, shutting down normally.
Nov 02 11:43:18 manjaro dbus[489]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.serv
Nov 02 11:43:18 manjaro dbus[489]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is
Nov 02 11:43:18 manjaro NetworkManager[491]: <warn>  [1509619398.1135] sup-iface[0x564fc2a59da0,wlp3s0]: connection disconnected (reason -3)
Nov 02 11:43:18 manjaro NetworkManager[491]: <info>  [1509619398.1136] device (wlp3s0): supplicant interface state: completed -> disconnected
Nov 02 11:43:18 manjaro NetworkManager[491]: <info>  [1509619398.1263] device (wlp3s0): supplicant interface state: disconnected -> disabled
Nov 02 11:43:18 manjaro NetworkManager[491]: <info>  [1509619398.1263] device (wlp3s0): supplicant interface state: disabled -> disconnected
Nov 02 11:43:18 manjaro NetworkManager[491]: <info>  [1509619398.1265] ModemManager disappeared from bus
....About fifty more lines till "Journal stopped"

As I specified my system for my needs over years it would be a whole lot of work to set it up freshly. So any help or advice is highly appreciated - please tell me if you think more logs or other info might help to solve that problem.

Thank you a lot!
Jakob

EDIT:

  • I use the poweroff command to shut down
  • Reinstalling lightdm over a chroot session also didn't change a thing

Okay, silly me!
Pressing Esc while booting gives you the bootlogs instead of loading screen... telling me about a partition error and how to solve it with fsck.
Silly me, sorry for annoing, I'd delete this topic but I don't see that option.
Jakob

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by