old kernel loaded after dist upgrade

English Install/Boot/Login
1

I performed a dist upgrade via zypper dup from openSUSE 13.2 to Leap 42.1 (and later 42.2). The upgrade via zypper ran without any issues, but after
rebooting the system, the old kernel (3.16.7-35-default) was still loaded. I removed the old kernel version completely and checked the grub2 config and
rebooted the system again, but still the old kernel was loaded. I can’t really see where the old kernel should have it’s files. There are no initrd and vmlinuz files
for that version anymore under /boot. I than managed to load the Leap 42.1 kernel via kexec. No I wanted to upgrade the system to Leap 42.2 what again
works flawless with zypper dup. But still the old Kernel from 13.2 gets loaded. And now loading the Leap 42.2 Kernel version 4.4.49 does not work via kexec
(or network is not working anymore after performing kexec - it is a remote system).

This is a completely weird behaviour…

Not sure, if all of this is related to the fact that the system uses a software RAID1. It is a remote server, so I have no physical access to it. Doe anyone has an idea?

2

Are you certain that it not just the grub prompt? There have been reports in the past of insitu upgrades not updating the prompt but the newer kernel running

3

Are you sure? I think that may just be the naming in grub. Check reality with

uname -r

If necessary, you can correct the cosmetic naming to reflect reality.

4

For sure I have tested that. And as I wrote, it is a remote server, so I do not see any grub prompt. :wink:

buschmann@hbn:~> uname -r
3.16.7-35-default
buschmann@hbn:~> cat /proc/version
Linux version 3.16.7-35-default (geeko@buildhost) (gcc version 4.8.3 20140627 [gcc-4_8-branch revision 212064] (SUSE Linux) ) #1 SMP Sun Feb 7 17:32:21 UTC 2016 (832c776)

Also there is another problem when loading the old kernel. Network routes are not working (or not applied) and the static IPv4 address is not set. After loading the Leap 42.1 kernel via kexec,
bot worked. But now a I can not load the kernel via kexec anymore.

5

Content of fstab and mtab:

hbn:~ # cat /etc/fstab
proc /proc proc defaults 0 0
/dev/md0 none swap sw 0 0
/dev/md1 /boot ext3 defaults 0 0
/dev/md2 / ext4 defaults 0 0

hbn:~ # cat /etc/mtab
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,relatime 0 0
devtmpfs /dev devtmpfs rw,nosuid,size=8054596k,nr_inodes=2013649,mode=755 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
/dev/md2 / ext4 rw,relatime,data=ordered 0 0
rpc_pipefs /var/lib/nfs/rpc_pipefs rpc_pipefs rw,relatime 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=25,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/md1 /boot ext3 rw,relatime,stripe=4,data=ordered 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=1614752k,mode=700,uid=1000,gid=100 0 0
6

Disk layout as shown by fdisk:

hbn:~ # fdisk -l
Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 8E46AB52-3F30-42B2-BDBD-61B288A77DF6

Device        Start        End    Sectors  Size Type
/dev/sda1      4096   16781311   16777216    8G Linux RAID
/dev/sda2  16781312   17829887    1048576  512M Linux RAID
/dev/sda3  17829888 5860533134 5842703247  2.7T Linux RAID
/dev/sda4      2048       4095       2048    1M BIOS boot

Partition table entries are not in disk order.


Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: DDCFD852-7715-4688-BAE1-74F9DA061608

Device        Start        End    Sectors  Size Type
/dev/sdb1      4096   16781311   16777216    8G Linux RAID
/dev/sdb2  16781312   17829887    1048576  512M Linux RAID
/dev/sdb3  17829888 5860533134 5842703247  2.7T Linux RAID
/dev/sdb4      2048       4095       2048    1M BIOS boot

Partition table entries are not in disk order.


Disk /dev/mapper/TOSHIBA_DT01ACA300_23P0S8XTS: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 8E46AB52-3F30-42B2-BDBD-61B288A77DF6

Device                                            Start        End    Sectors  Size Type
/dev/mapper/TOSHIBA_DT01ACA300_23P0S8XTS-part1     4096   16781311   16777216    8G Linux RAID
/dev/mapper/TOSHIBA_DT01ACA300_23P0S8XTS-part2 16781312   17829887    1048576  512M Linux RAID
/dev/mapper/TOSHIBA_DT01ACA300_23P0S8XTS-part3 17829888 5860533134 5842703247  2.7T Linux RAID
/dev/mapper/TOSHIBA_DT01ACA300_23P0S8XTS-part4     2048       4095       2048    1M BIOS boot

Partition table entries are not in disk order.


Disk /dev/mapper/TOSHIBA_DT01ACA300_3375075GS: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: DDCFD852-7715-4688-BAE1-74F9DA061608

Device                                            Start        End    Sectors  Size Type
/dev/mapper/TOSHIBA_DT01ACA300_3375075GS-part1     4096   16781311   16777216    8G Linux RAID
/dev/mapper/TOSHIBA_DT01ACA300_3375075GS-part2 16781312   17829887    1048576  512M Linux RAID
/dev/mapper/TOSHIBA_DT01ACA300_3375075GS-part3 17829888 5860533134 5842703247  2.7T Linux RAID
/dev/mapper/TOSHIBA_DT01ACA300_3375075GS-part4     2048       4095       2048    1M BIOS boot

Partition table entries are not in disk order.


Disk /dev/md0: 8 GiB, 8585674752 bytes, 16768896 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md2: 2.7 TiB, 2991329640448 bytes, 5842440704 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md1: 511.7 MiB, 536543232 bytes, 1047936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
7

Ok, I think I found the problem:

Somehow the first hard disk (/dev/sda) was not part of the RAID anymore - for whatever reason.
I am currently adding it back to the RAID and will than see what happens. Seems the only imaginable
reason for me to the weird behavior. :slight_smile: