Stop booting after "Loading initial ramdisk..."

SUSE Linux Enterprise Desktop SLED Install-Boot
1

I have SLED12 SP1 on HP ProBook 4515s. Since kernel update 3.12.51-52.31
my laptop can’t boot up with new kernel, it stop after “Loading initial
ramdisk…” message. Booting with kernel 3.12.48-52.27 is fine, I am use
it by choice advanced options in grub. The other day I upgrade SLED
installation to SP1 in the hope of fix this issue, but on kernel
3.12.51-60.20 the same thing and I steel have to use 3.12.48-52.27.
How to fixing that?

2

Hi
At the grub menu, highlight the kernel your having issues with, press e
(to edit) and in the menu etry for the kernel options add

nomodeset

Then press F10.

Are you booting via grub or via efi?

If the above doesn’t work, boot into the working kernel and post the
output from;

df -k
btrfs fi usage

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.2|3.12.51-60.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

3

В Fri, 08/01/2016 в 22:21 +0000, malcolmlewis wrote: [color=blue]

Hi
At the grub menu, highlight the kernel your having issues with, press e
(to edit) and in the menu etry for the kernel options add

nomodeset

Then press F10.

Are you booting via grub or via efi?

If the above doesn’t work, boot into the working kernel and post the
output from;

df -k
> btrfs fi usage

[/color]
Hi Malcolme.
nomodeset doesn’t work. I am booting via grub, efi is not used.

~> df -k
Файловая система 1K-блоков Использовано  Доступно Использовано%
Cмонтировано в
/dev/sda1        268435456     49463020 217401100           19% /
devtmpfs           3907580            0   3907580            0% /dev
tmpfs              3950024          152   3949872            1% /dev/shm
tmpfs              3950024        10456   3939568            1% /run
tmpfs              3950024            0   3950024
0% /sys/fs/cgroup
tmpfs              3950024           32   3949992            1% /tmp
/dev/sda5        309506048     57377220 236393096           20% /home
# btrfs fi usage /
root's password:
Overall:
Device size: 256.00GiB
Device allocated:   51.07GiB
Device unallocated: 204.93GiB
Device missing:      0.00B
Used:   46.67GiB
Free (estimated): 207.33GiB (min: 104.87GiB)
Data ratio:       1.00
Metadata ratio:       2.00
Global reserve: 512.00MiB (used: 0.00B)

Data,single: Size:41.01GiB, Used:38.61GiB
/dev/sda1   41.01GiB

Metadata,DUP: Size:5.00GiB, Used:4.03GiB
/dev/sda1   10.00GiB

System,DUP: Size:32.00MiB, Used:12.00KiB
/dev/sda1   64.00MiB

Unallocated:
/dev/sda1 204.93GiB
4

Hi
OK, so disk space issues. So if you boot from the old kernel and check
down in /boot, do the newer kernel vmlinux, initrd exist?

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.2|3.12.51-60.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

5

On Sat, 09/01/2016 00:56 +0000, malcolmlewis wrote: [color=blue]

[QUOTE]
Hi
OK, so disk space issues. So if you boot from the old kernel and check
down in /boot, do the newer kernel vmlinux, initrd exist?
[/QUOTE][/color]
Hi!
At first glance everything is fine…

~> ls -l /boot
итого 87152
-rw-r--r-- 1 root root      512 окт 31  2014 backup_mbr
-rw-r--r-- 1 root root     1725 окт  7 13:36 boot.readme
-rw-r--r-- 1 root root   135645 окт  5 20:29
config-3.12.48-52.27-default
-rw-r--r-- 1 root root   135645 ноя 26 18:04
config-3.12.51-52.31-default
-rw-r--r-- 1 root root   136452 дек 11 18:05
config-3.12.51-60.20-default
drwxr-xr-x 1 root root        0 ноя 12 04:22 dracut
drwxr-xr-x 1 root root      148 янв  6 14:45 grub2
lrwxrwxrwx 1 root root       28 янв  6 14:37 initrd ->
initrd-3.12.51-60.20-default
-rw-r--r-- 1 root root 14435720 янв  6 14:44
initrd-3.12.48-52.27-default
-rw-r--r-- 1 root root 14438324 янв  6 14:44
initrd-3.12.51-52.31-default
-rw-r--r-- 1 root root 14440712 янв  6 14:45
initrd-3.12.51-60.20-default
-rw-r--r-- 1 root root   415744 янв  6 14:34 message
-rw-r--r-- 1 root root   723361 окт  5 20:55
symtypes-3.12.48-52.27-default.gz
-rw-r--r-- 1 root root   698805 окт  5 23:16
symtypes-3.12.48-52.27-xen.gz
-rw-r--r-- 1 root root   723159 ноя 26 18:20
symtypes-3.12.51-52.31-default.gz
-rw-r--r-- 1 root root   698602 ноя 26 18:18
symtypes-3.12.51-52.31-xen.gz
-rw-r--r-- 1 root root   748497 дек 11 18:20
symtypes-3.12.51-60.20-default.gz
-rw-r--r-- 1 root root   723014 дек 11 18:18
symtypes-3.12.51-60.20-xen.gz
-rw-r--r-- 1 root root   250436 окт  5 20:54
symvers-3.12.48-52.27-default.gz
-rw-r--r-- 1 root root   250484 ноя 26 18:20
symvers-3.12.51-52.31-default.gz
-rw-r--r-- 1 root root   253065 дек 11 18:19
symvers-3.12.51-60.20-default.gz
-rw-r--r-- 1 root root      409 окт  5 20:54
sysctl.conf-3.12.48-52.27-default
-rw-r--r-- 1 root root      409 ноя 26 18:20
sysctl.conf-3.12.51-52.31-default
-rw-r--r-- 1 root root      409 дек 11 18:19
sysctl.conf-3.12.51-60.20-default
-rw-r--r-- 1 root root  2616736 окт  5 20:52
System.map-3.12.48-52.27-default
-rw-r--r-- 1 root root  2617473 ноя 26 18:18
System.map-3.12.51-52.31-default
-rw-r--r-- 1 root root  2640328 дек 11 18:18
System.map-3.12.51-60.20-default
-rw-r--r-- 1 root root  5741841 окт  5 20:55
vmlinux-3.12.48-52.27-default.gz
-rw-r--r-- 1 root root  5745434 ноя 26 18:21
vmlinux-3.12.51-52.31-default.gz
-rw-r--r-- 1 root root  5797780 дек 11 18:21
vmlinux-3.12.51-60.20-default.gz
lrwxrwxrwx 1 root root       29 янв  6 14:37 vmlinuz ->
vmlinuz-3.12.51-60.20-default
-rw-r--r-- 1 root root  4911968 окт  5 22:26
vmlinuz-3.12.48-52.27-default
-rw-r--r-- 1 root root  4916064 ноя 26 19:11
vmlinuz-3.12.51-52.31-default
-rw-r--r-- 1 root root  4966880 дек 11 19:21
vmlinuz-3.12.51-60.20-default
6

Hi
Ok if you boot into the old kernel and check it is all updated;

zypper ref -f
zypper -t patch

If no patches, lets try re-installing the latest kernel;

zypper in -f kernel-default

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.2|3.12.51-60.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

7

[QUOTE][color=blue]

Hi
Ok if you boot into the old kernel and check it is all updated;

zypper ref -f
> zypper -t patch

If no patches, lets try re-installing the latest kernel;

zypper in -f kernel-default [/QUOTE][/color]
I did it. Nothing helped.

8

Hi
OK, lets see if rebuilding grub helps, boot into the system via the old kernel, switch to root user and run;

grub2-mkconfig -o /boot/grub2/grub.cfg

Can you post back the output please.

9

[QUOTE]Hi
OK, lets see if rebuilding grub helps, boot into the system via the old

kernel, switch to root user and run;

Code:

grub2-mkconfig -o /boot/grub2/grub.cfg

Can you post back the output please.[/QUOTE]
Rebuilding grub did not help.

~> sudo grub2-mkconfig -o /boot/grub2/grub.cfg root's password: Generating grub configuration file ... Найдена тема: /boot/grub2/themes/SLE/theme.txt Найден образ linux: /boot/vmlinuz-3.12.51-60.20-default Найден образ initrd: /boot/initrd-3.12.51-60.20-default Найден образ linux: /boot/vmlinuz-3.12.51-52.31-default Найден образ initrd: /boot/initrd-3.12.51-52.31-default Найден образ linux: /boot/vmlinuz-3.12.48-52.27-default Найден образ initrd: /boot/initrd-3.12.48-52.27-default завершено

10

Recently I upgrade kernel to 3.12.51-60.25.1. Next one version with
broken boot…

11

Hi
Do the softlinks point to the correct kernel?

ls -la initrd vmlinuz
lrwxrwxrwx 1 root root 28 Jan 21 06:46 initrd -> initrd-3.12.51-60.25-default
lrwxrwxrwx 1 root root 29 Jan 21 06:46 vmlinuz -> vmlinuz-3.12.51-60.25-default

So does this mean the one you had issues with now boots, but not the
latest?

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 SP1|GNOME 3.10.4|3.12.51-60.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

12

24/01/2016 at 15:53 +0000, malcolmlewis wrote:[color=blue]

So does this mean the one you had issues with now boots, but not the
latest?[/color]

t> ls -la initrd vmlinuz
lrwxrwxrwx 1 root root 28 янв 23 15:42 initrd ->
initrd-3.12.51-60.25-default
lrwxrwxrwx 1 root root 29 янв 23 15:42 vmlinuz ->
vmlinuz-3.12.51-60.25-default

I still can boot with kernel 3.12.48-52.27, but can not with others.

13

After few updates issue is gone! I can boot from last kernel without
problem!