Hi,
I found many answers to my question, but they don’t really apply. I try to explain:
It’s a Leap 15 installed on a NVMe with LVM. It’s only a thin client to login to virtual machines, so the workload is not really big.
I didn’t notice any problems previous to this, but since last week the system booted twice into emergency mode, /var could not be mounted. After running fsck on all LVs the system booted fine both times. A colleague of mine also experienced a similar error on his Leap 15 laptop. I wouldn’t post this if it would be a one-time-action, but since it happened twice within a week I’m a little concerned and wondering if it’s a Leap issue? The hardware is pretty new, December 2018 IIRC.
These are all error messages from the last failed boot, dm-3 is the LV for /var:
leap15:~ # ll /dev/system/var
lrwxrwxrwx 1 root root 7 Feb 27 07:51 /dev/system/var -> ../dm-3
leap15:~ # zgrep -i error /var/log/messages-20190225.xz
Feb 25 08:31:54 leap15 mcelog[1239]: mcelog: Family 6 Model 92 CPU: only decoding architectural errors
Feb 25 08:31:54 leap15 rsyslogd: error during parsing file /etc/rsyslog.conf, on or before line 100: warnings occured in file '/etc/rsyslog.conf' around line 100 [v8.33.1 try http://www.rsyslog.com/e/2207 ]
Feb 25 08:31:54 leap15 kernel: 0.080875] mce: [Hardware Error]: Machine check events logged
Feb 25 08:31:54 leap15 kernel: 0.080878] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: e600000000020408
Feb 25 08:31:54 leap15 kernel: 0.080885] mce: [Hardware Error]: TSC 0 ADDR fef5d200
Feb 25 08:31:54 leap15 kernel: 0.080891] mce: [Hardware Error]: PROCESSOR 0:506c9 TIME 1551079903 SOCKET 0 APIC 0 microcode 32
Feb 25 08:31:54 leap15 kernel: 0.168744] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
Feb 25 08:31:54 leap15 kernel: 9.325939] EDAC pnd2: Failed to register device with error -22.
Feb 25 08:31:54 leap15 kernel: 9.357733] EDAC pnd2: Failed to register device with error -22.
Feb 25 08:31:56 leap15 kernel: 12.146348] EXT4-fs error (device dm-3): ext4_mb_free_metadata:4639: group 1, block 36873:Block already on to-be-freed list
Feb 25 08:31:59 leap15 kernel: 15.674855] EXT4-fs error (device dm-3): mb_free_blocks:1470: group 1, block 36600:freeing already freed block (bit 3832); block bitmap corrupt.
Feb 25 08:31:59 leap15 kernel: 15.674893] EXT4-fs error (device dm-3): ext4_mb_generate_buddy:758: group 1, block bitmap and bg descriptor inconsistent: 24846 vs 24847 free clusters
Feb 25 08:32:16 leap15 kernel: 32.063858] EXT4-fs error (device dm-3): ext4_lookup:1585: inode #119: comm logrotate: deleted inode referenced: 350
Feb 25 08:32:16 leap15 logrotate[1941]: error: error stat()ing state file /var/lib/misc/logrotate.status: Die Struktur muss bereinigt werden
Feb 25 08:32:16 leap15 kernel: 32.080243] EXT4-fs error (device dm-3): ext4_lookup:1585: inode #119: comm logrotate: deleted inode referenced: 350
Feb 25 08:32:16 leap15 logrotate[1941]: error: error creating state file /var/lib/misc/logrotate.status: Die Struktur muss bereinigt werden
Does this reveal anything I should check?
leap15:~ # uname -a
Linux nde29 4.12.14-lp150.12.22-default #1 SMP Sat Oct 13 05:05:16 UTC 2018 (09415e8) x86_64 x86_64 x86_64 GNU/Linux
leap15:~ # cat /etc/os-release
NAME="openSUSE Leap"
VERSION="15.0"
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.0"
PRETTY_NAME="openSUSE Leap 15.0"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.0"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/"