PDA

View Full Version : SLES 12 Update to Kernel Default 3.12.44.52 / System doesn't come up



felixschaefer
08-Oct-2015, 15:21
Hello,

I installed a fresh trial of SLES12 64 Bit on a Microsoft Server 2012 (not R2) Hyper-V VM.

The Linux VM works fine, until I update with yast or zypper to kernel-Default-3.12.44.52.18.1 package.

After the reboot, Linux doesn't come up. It hangs while loading the new kernel.
It seems that an issue with the modules by udev is the Problem.

Please the error Messages after zypper update command:

Thanks.

Felix

Messages:
proxy:~ # zypper update
Refreshing service 'SUSE_Linux_Enterprise_Server_12_x86_64'.
Loading repository data...
Reading installed packages...

The following NEW package is going to be installed:
kernel-default-3.12.44-52.18.1

The following package is going to be upgraded:
p11-kit

1 package to upgrade, 1 new.
Overall download size: 31.8 MiB. Already cached: 0 B After the operation, additional 137.0 MiB will be used.
Continue? [y/n/? shows all options] (y): y
Retrieving package kernel-default-3.12.44-52.18.1.x86_64 (1/2), 31.8 MiB (137.0 MiB unpacked)
Retrieving: kernel-default-3.12.44-52.18.1.x86_64.rpm .................................................. .................................[done (333.2 KiB/s)]
Retrieving package p11-kit-0.20.3-4.1.x86_64 (2/2), 85.0 KiB (224.3 KiB unpacked)
Retrieving delta: ./x86_64/p11-kit-0.20.3-1.6_4.1.x86_64.drpm, 15.9 KiB
Retrieving: p11-kit-0.20.3-1.6_4.1.x86_64.drpm .................................................. .................................................. ....[done]
Applying delta: ./p11-kit-0.20.3-1.6_4.1.x86_64.drpm .................................................. ................................................[done]
Checking for file conflicts: .................................................. .................................................. ......................[done]
(1/2) Installing: kernel-default-3.12.44-52.18.1 .................................................. .................................................. ..[done]
Additional rpm output:
C
Creating initrd: /boot/initrd-3.12.44-52.18-default
Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-3.12.44-52.18-default 3.12.44-52.18-default
*** Including module: bash ***
*** Including module: warpclock ***
*** Including module: i18n ***
*** Including module: ifcfg ***
*** Including module: drm ***
*** Including module: plymouth ***
*** Including module: btrfs ***
*** Including module: kernel-modules ***
Failed to install module unix
Failed to install module ehci-platform
Failed to install module atkbd
Failed to install module i8042
Failed to install module pcmcia
Failed to install module sdhci_acpi
Failed to install module swap
*** Including module: resume ***
*** Including module: rootfs-block ***
*** Including module: terminfo ***
*** Including module: udev-rules ***
Skipping udev rule: 91-permissions.rules
Skipping udev rule: 80-drivers-modprobe.rules
*** Including module: haveged ***
*** Including module: systemd ***
Failed to install module ipv6
*** Including module: usrmount ***
*** Including module: base ***
*** Including module: fs-lib ***
*** Including module: shutdown ***
*** Including module: suse ***
*** Including modules done ***
*** Installing kernel module dependencies and firmware ***
*** Installing kernel module dependencies and firmware done ***
*** Resolving executable dependencies ***
*** Resolving executable dependencies done***
*** Hardlinking files ***
*** Hardlinking files done ***
*** Stripping files ***
*** Stripping files done ***
*** Generating early-microcode cpio image ***
*** Constructing GenuineIntel.bin ****
*** Store current command line parameters ***
Stored kernel commandline:
resume=UUID=9cd83469-59ab-4e96-b610-ef36ac7f1cdc
root=UUID=f693ad70-5db3-41d1-8758-4eef456b4172 rootflags=rw,relatime,space_cache rootfstype=btrfs
*** Creating image file ***
*** Creating image file done ***
Some kernel modules could not be included:
unix
ehci-platform
atkbd
i8042
pcmcia
sdhci_acpi
swap
ipv6
Update bootloader...


(2/2) Installing: p11-kit-0.20.3-4.1 .................................................. .................................................. ..............[done]
p

jmozdzen
12-Oct-2015, 12:02
Hi Felix,

it might be you're barking up the wrong tree: I've seen these dracut messages (with other distributions) quite often and have never had a problem booting up the system.

Can you select the original kernel during boot, and boot up fine then? Do you have any specific output you can share, or is the VM just stalling after the grub step?

Regards,
Jens

felixschaefer
13-Oct-2015, 10:51
Hi Felix,

it might be you're barking up the wrong tree: I've seen these dracut messages (with other distributions) quite often and have never had a problem booting up the system.

Can you select the original kernel during boot, and boot up fine then? Do you have any specific output you can share, or is the VM just stalling after the grub step?

Regards,
Jens

Hi Jens,

the shipped in original kernel starts without errors.

If is select the new kernel (now: 3.12.48-52.27-default) with recovery mode I can see very much messages from udev:
The complete Screen is flooded with These udev Messages.
*** A start Job is running for udev Wait to complete device Init. (time Infos).

After two minutes the Login Screen appears and the Server run normally.

Thanks.

Felix

jmozdzen
13-Oct-2015, 12:20
Hi Felix,


If is select the new kernel (now: 3.12.48-52.27-default) with recovery mode I can see very much messages from udev:
The complete Screen is flooded with These udev Messages.
*** A start Job is running for udev Wait to complete device Init. (time Infos).

After two minutes the Login Screen appears and the Server run normally.

so did I get it right that the actual problem is the delay (plus excessive messages) until boot completes?

(In other words, to me it sounds as if the server is fully operational after those two minutes.)

There may well be a change in device initialization that came with the update, leading to an intermediate situation where required devices are not yet available, but the system keeps polling. I remember having had the reverse problem with an earlier release, which led to a changed boot sequence that gave exactly that behavior. Maybe someone had a similar problem, hence this changed procedures you're seeing...

If, on the other hand, *it only works for you in recovery mode*, then this would need to be looked after. Do you have a SUSE pre-sales contact?

Regards,
Jens