Stuck booting after an update

English Install/Boot/Login
1

Hi,

The software management tool crashed while updating, and after that I had problems with network manager and the application launcher. I didn’t have connection to the Internet, so I updated again with the Tumbleweed offline image. Since then Tumbleweed is stuck in the booting process, safe mode doesn’t work neither. However, I can boot with 3 in linuxefi where everything seems to be working fine: terminal and startx.

https://susepaste.org/5758162
https://susepaste.org/5758162

Any advice about how to fix this? Thanks.

2

Hi and welcome to the Forum :slight_smile:
Can you show the output from the following;


/sbin/lspci -nnk | egrep -A3 "VGA|Display|3D"
3

Hi Malcolm, sure.


00:02.0 **VGA** compatible controller [0300]: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
        DeviceName: Onboard IGD
        Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079]
        Kernel driver in use: i915
4

Hi
Can you boot without using 3, then boot with 3 and look at the previous boot log with journalctl -b -1 and look for where things may be going wrong.

5

I see some red lines there, the whole output is here: https://paste.opensuse.org/98086055


nov 03 16:44:54 linux-openSUSE kernel: **Bluetooth: hci0: Malformed MSFT vendor event: 0x02**
nov 03 16:44:56 linux-openSUSE systemd-udevd[587]: **/etc/udev/rules.d/50-switch.rules:1 Invalid key/value pair, ignoring.**
nov 03 16:44:56 linux-openSUSE systemd-udevd[587]: **/etc/udev/rules.d/90-extraacl.rules:4 Invalid key '"KERNEL'**
nov 03 16:44:56 linux-openSUSE systemd-udevd[587]: **/etc/udev/rules.d/90-extraacl.rules:5 Invalid key '"KERNEL'**
nov 03 16:44:56 linux-openSUSE systemd-udevd[587]: **/etc/udev/rules.d/50-switch.rules:1 Invalid key/value pair, ignoring.**
nov 03 16:44:56 linux-openSUSE systemd-udevd[587]: **/etc/udev/rules.d/90-extraacl.rules:4 Invalid key '"KERNEL'
**nov 03 16:44:56 linux-openSUSE systemd-udevd[587]: **/etc/udev/rules.d/90-extraacl.rules:5 Invalid key '"KERNEL'**
nov 03 16:44:58 linux-openSUSE tlp[743]: **Error: tlp.service is not enabled, power saving will not apply on boot.**
nov 03 16:44:58 linux-openSUSE tlp[743]: **>>> Invoke 'systemctl enable tlp.service' to correct this!**
nov 03 16:44:58 linux-openSUSE kernel: **snd_hda_codec_conexant hdaudioC0D0: vmaster hook already present before cdev!**
nov 03 16:47:09 linux-openSUSE systemd-udevd[587]: **/etc/udev/rules.d/90-extraacl.rules:4 Invalid key '"KERNEL'**
nov 03 16:47:09 linux-openSUSE systemd-udevd[587]: **/etc/udev/rules.d/90-extraacl.rules:5 Invalid key '"KERNEL'**
nov 03 16:47:09 linux-openSUSE kernel: **watchdog: watchdog0: watchdog did not stop!**
6 
Nov 03 16:44:56 linux-openSUSE systemd[1]: Queued start job for default target Emergency Mode.

That is already wrong. emergency.target certainly is not supposed to be default. What is output of “systemctl get-default”?

Nov 03 16:45:29 linux-openSUSE systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Nov 03 16:47:09 linux-openSUSE systemd[1]: Received SIGINT.
Nov 03 16:47:09 linux-openSUSE systemd[1]: Activating special unit System Reboot...

So at 16:47:09 something sends SIGINT to PID 1 which triggers systemd reboot. Did you do something between 16:45:29 and 16:47:09?

7

I think the original information provided by the OP was less then complete. So I am afraid a lot of guessing is going on.

The software management tool crashed while updating

Which software management too? And what sort of update? And what was the error message or what did you see to happen?
I assume you didn’t do the normal way of updating Tumbleweed

zypper dup

else you probably would have said so. But that means we do not even know what you did.

8

Hi arvidjaar](https://forums.opensuse.org/member.php/69818-arvidjaar),

systemctl output is this, so I think the emergency mode is due to the 3 in linuxefi.

emergency.target
Note: found "3" on the kernel commandline, which overrides the default unit.

About the sencond part, I did that, I waited for 1 minute and a half and the pressed ctrl + alt + supr to boot again with 3 in linuxefi.

9

Hi hcvv,

I didn’t use zypper I used YaST Software Management GUI. Normal update, I only have the three stock repositories: Main Repository (NON-OSS), Main Repository (OSS) and Main Update Reporitory. I can’t remember the error message, but a message was shown in the middle of the update and the app closed.

10

When you run Tumbleweed, you should use

zypper dup

When you can run in single user mode my advice would be to try a zypper dup to try to repiri what went wrong and to see messages when it breaks.

11

For hassle-free upgrades always use “zypper dist-upgrade”. Run it in the system slice and it will never die prematurely. Systemd services are fully logged to the journal: https://forums.opensuse.org/entry.php/250-The-command-line-is-by-far-the-easiest-way-to-update-Tumbleweed

12

No. it is not. It is permanent setting. Normally default.target points to either multi-user.target (which corresponds to 3) or graphical.target (which corresponds to 5). And you can boot into multi-user.target which means your current problem is the wrong default.target.

13

You’re right arvidjaar](https://forums.opensuse.org/member.php/69818-arvidjaar), I don’t how and when the emergency mode was set by default, executing the following command made everything back to normal.

systemctl set-default graphical.target

Thank you all for your help and recommedations! I will use zypper for updates from now on :).

14

Not just zypper (which can be used for many things), but zypper dup (and never zypper up).

15

Ok, understood, thanks!