HP Laptop not booting after updates yesterday

English Install/Boot/Login
1

LEAP 42.3 KDE/Plasma, with Intel HD graphics.

This laptop hasn’t been updated for some time. Yesterday there where 100+ updates according to the online updater (the one on the notifications area, not Yast’s update).

First a few zypper packages were updated, that the session restarted, then the bulk of the updates, then when the update notified of two Mozilla updates, Firefox and Thunderbird IIRC.

After all updates I switched it off (bed time). Today the grub menu appeared normally, but when choosing the default kernel (version ending in -45) it started the (emergency?) boot splash, the one with 3 small rectangles instead of the fancy one with 3 circles.

Booting to other kernel versions (-42 and -39 IINM, not in recovery mode) the screen froze in a few seconds, ESC did nothing. In others ESC showed a cursor on the top left corner of a terminal, both in the laptop and in the TV connected to the HDMI port. This screen was also frozen except that every few seconds it alternated from a white cursor on black background to a green cursor on gray background.

Booting from a couple of the many snapshots, the grub menu just displayed a single option saying “If the boot works, run <snapper-something> from a terminal” - I don’t remember the exact text. Hitting ENTER, however, just displayed the same message again, with no other action.

Booting from the latest kernel in recovery mode the system boots OK to the desktop, although without compositing (3D effects) and also with no HDMI out.

How can I fix this?

Thanks,

Bruno

2

To bad this problem popped up, to fix the problem it would be good to get a better understanding on what went wrong with the unsuccessful boots. Try in the recovery mode:

journalctl -list-boots

And get the log for one of the failed boots using “journalctl -b -2” with “-2” replaced with the failed boot you want to see,

Check if there is anything near the end of this log that looks suspicious.

3

Hi, Marel, and thanks for the suggestions. I’ve checked the logs but didn’t see what could have gone wrong. both before and after logs are below.

First a correction: compositing is working normally, with 3D effects and all. The main problem right now is the lack of HDMI output. There’s no second monitor shown in system-settings>Display and, in system-settings-multimedia, only a grayed out HDMI audio entry, not functional.

Note: a check of the file system - specially available space - didn’t show any problems. Commands I tried:

~ df -h
# btrfs filesystem usage /
# /etc/cron.weekly/btrfs-balance
# /etc/cron.daily/suse.de-snapper

I can post the outputs if necessary.

Now the logs: Show below are part of the boot-logs list, the final lines of the first failed boot, and the corresponding part of the last normal boot (full log has 16K+ lines). This is the session where the updates were installed.

 -5 7e3db0946c97461598e0ae99030ea7ce Wed 2018-03-28 07:17:21 -03—Wed 2018-03-28 09:30:20 -03 <--- Normal session
 -4 a5caa6e38ec3479295f991af00b5c213 Thu 2018-03-29 10:38:31 -03—Fri 2018-03-30 00:56:21 -03  <--- Normal session where updates where installed
 -3 53e19271b168437ab789c5e4a1429c38 Fri 2018-03-30 14:40:22 -03—Fri 2018-03-30 14:43:18 -03  <--- Boot failure
 -2 b6a539dbf954455c8c4a90afee79df03 Fri 2018-03-30 14:52:10 -03—Fri 2018-03-30 14:54:20 -03  <--- Boot failure (snapper?)
 -1 9bfe0751289747849b0e40e4d1e37d39 Fri 2018-03-30 15:00:35 -03—Fri 2018-03-30 15:03:30 -03  <--- Boot failure (snapper?)
  0 e191fdeba8d04f20ad74bdbdcb4f8a33 Fri 2018-03-30 15:04:43 -03—Sat 2018-03-31 14:39:43 -03  <--- Boot in recovery mode

note: I haven’t looked yet at why the snapshot restore failed. It is probably on logs -2 and -1.

Last lines of failed log -3:

Mar 30 14:43:17 linux systemd[1]: Mounted /windowsD.
Mar 30 14:43:17 linux systemd[1]: Mounted /home.
Mar 30 14:43:17 linux systemd[1]: Mounted /tmp.
Mar 30 14:43:17 linux systemd[1]: Mounted /var/log.
Mar 30 14:43:17 linux systemd[1]: Starting Flush Journal to Persistent Storage...
Mar 30 14:43:17 linux systemd[1]: Reached target Local File Systems.
Mar 30 14:43:17 linux systemd[1]: Starting Preprocess NFS configuration...
Mar 30 14:43:17 linux systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Mar 30 14:43:17 linux systemd[1]: Starting Restore /run/initramfs on shutdown...
Mar 30 14:43:17 linux systemd[1]: Starting Security Auditing Service...
Mar 30 14:43:17 linux systemd[1]: Started Restore /run/initramfs on shutdown.
Mar 30 14:43:18 linux systemd-journald[413]: System journal (/var/log/journal/) is currently using 224.0M.
                                             Maximum allowed usage is set to 203.8M.
                                             Leaving at least 305.7M free (of currently available 1.6G of space).
                                             Enforced usage limit is thus 203.8M, of which 0B are still available.
Mar 30 14:43:18 linux systemd-journald[413]: Time spent on flushing to /var is 196.041ms for 1057 entries.

Corresponding normal boot log -4, with lines after the journald flush entry in bold. The failed boot froze before these lines where logged:

Mar 29 10:38:37 linux systemd[1]: Mounted /windowsD.
Mar 29 10:38:38 linux ntfs-3g[1002]: Version 2013.1.13 external FUSE 29
Mar 29 10:38:38 linux ntfs-3g[1002]: Mounted /dev/sda4 (Read-Only, label "OS", NTFS 3.1)
Mar 29 10:38:38 linux ntfs-3g[1002]: Cmdline options: ro,noatime,noexec,nosuid,nodev,gid=100,fmask=133,dmask=022,locale=pt_BR.UTF-8,users
Mar 29 10:38:38 linux ntfs-3g[1002]: Mount options: ro,noexec,nosuid,nodev,users,allow_other,nonempty,noatime,default_permissions,fsname=/dev/sda4,blkdev,blksize=4096
Mar 29 10:38:38 linux ntfs-3g[1002]: Global ownership and permissions enforced, configuration type 1
Mar 29 10:38:38 linux ntfs-3g[1002]: Warning : using problematic uid==0 and gid!=0
Mar 29 10:38:38 linux systemd[1]: Mounted /windowsC.
Mar 29 10:38:38 linux kernel: XFS (sda7): Ending clean mount
Mar 29 10:38:38 linux systemd[1]: Mounted /tmp.
Mar 29 10:38:38 linux kernel: XFS (sda9): Mounting V5 Filesystem
Mar 29 10:38:38 linux kernel: XFS (sda8): Ending clean mount
Mar 29 10:38:38 linux systemd[1]: Mounted /var/log.
Mar 29 10:38:38 linux systemd[1]: Starting Flush Journal to Persistent Storage...
Mar 29 10:38:39 linux systemd-journald[427]: System journal (/var/log/journal/) is currently using 216.0M.
                                             Maximum allowed usage is set to 203.8M.
                                             Leaving at least 305.7M free (of currently available 1.6G of space).
                                             Enforced usage limit is thus 203.8M, of which 0B are still available.
Mar 29 10:38:39 linux systemd-journald[427]: Time spent on flushing to /var is 687.436ms for 1072 entries.
**Mar 29 10:38:40 linux kernel: XFS (sda9): Ending clean mount
Mar 29 10:38:39 linux auditd[1026]: Started dispatcher: /sbin/audispd pid: 1028
Mar 29 10:38:39 linux systemd[1]: Mounted /home.
Mar 29 10:38:39 linux audispd[1028]: priority_boost_parser called with: 4
Mar 29 10:38:39 linux systemd[1]: Reached target Local File Systems.
Mar 29 10:38:39 linux audispd[1028]: max_restarts_parser called with: 10
Mar 29 10:38:39 linux systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Mar 29 10:38:39 linux audispd[1028]: No plugins found, exiting
Mar 29 10:38:39 linux systemd[1]: Starting Restore /run/initramfs on shutdown...
Mar 29 10:38:39 linux auditd[1026]: Init complete, auditd 2.3.6 listening for events (startup state enable)
Mar 29 10:38:39 linux systemd[1]: Starting Preprocess NFS configuration...
Mar 29 10:38:39 linux systemd[1]: Starting Security Auditing Service...
Mar 29 10:38:39 linux systemd[1]: Started Restore /run/initramfs on shutdown.
Mar 29 10:38:39 linux systemd[1]: Started Preprocess NFS configuration.
Mar 29 10:38:39 linux systemd[1]: Reached target NFS client services.
Mar 29 10:38:39 linux systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
Mar 29 10:38:39 linux systemd[1]: Started Security Auditing Service.
Mar 29 10:38:40 linux systemd[1]: Started Flush Journal to Persistent Storage.
Mar 29 10:38:40 linux systemd[1]: Starting Create Volatile Files and Directories...
Mar 29 10:38:40 linux auditctl[1032]: No rules
Mar 29 10:38:40 linux auditctl[1032]: AUDIT_STATUS: enabled=1 flag=1 pid=1026 rate_limit=0 backlog_limit=320 lost=34 backlog=0
Mar 29 10:38:40 linux systemd-tmpfiles[1041]: Cannot set file attribute for '/var/log/journal', value=0x00800000, mask=0x00800000: Operation not supported
Mar 29 10:38:40 linux systemd-tmpfiles[1041]: Cannot set file attribute for '/var/log/journal/01bf0cc55823391e6d8f0b215a43193f', value=0x00800000, mask=0x00800000: Operation not supported
Mar 29 10:38:40 linux systemd[1]: Started Create Volatile Files and Directories.
Mar 29 10:38:40 linux systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Mar 29 10:38:40 linux systemd[1]: Started Update UTMP about System Boot/Shutdown.
Mar 29 10:38:40 linux systemd[1]: Reached target System Initialization.**

Any suggestions, including how to restore HDMI output, will be most appreciated.

Thank you,

Bruno

4

Boot failure (snapper?)

Possibly a Btrfs issue:

5

I was going to try and solve this today, but decided to update the system first. Lo and behold, it rebooted normally and everything is working.

6

Now that is good to hear … er, read. :slight_smile:

7

Have a similar problem. After seeing a problem with MTRR in the journal log, I rebooted but the Toshiba notebook keeps going into emergency mode.
With the openSuse 42.3 dvd in the drive, and the optical drive first on the boot list in the BIOS, power cycles immediately went to the grub screen then into emergency mode. Also the arrow keys seemed to stop working for a few boots. Changed the BIOS config from ‘fast’ to ‘normal’ boot speed which got the install disk started. But the reboot after install went back to emergency mode.
During the latest install from disk, the swap and / partitions were formatted, but not /home. Is there something in /home that might cause the problem?

8

Another item from log:
your CPUs have inconsistent MTRR values

9

Yours is a different problem. As per Forum rules, you should be starting a new thread instead of tacking onto the end of this thread.

Please start your own thread so others can look into your issue for you.

This thread is closed.