You are not logged in.

#1 2020-06-25 19:25:18

graham
Member
From: South Africa
Registered: 2020-06-25
Posts: 2
Website

[SOLVED] System not booting after kernel upgrade to 5.7.x

Hello all,

After upgrading to linux-5.7.x I can no longer boot the system successfully.
This is happening to a HP and a Thinkpad laptop.

Both systems can be recovered by booting with a USB, mounting the disk and downgrading to linux-5.6.15
I am using an efistub to boot both systems

HP

Booting after upgrade.

:: running early hook [udev]
Starting version 245.6-8-arch
:: running early hook [lvm2]
:: running hook [udev]
:: Triggering uevent...
ERROR: device '' not found. Skipping fschk.
:: mounting '' on real root
mount: /new_root: no filesystem type specified.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off

Output of efibootmgr.

[graham@slaine ~]$ efibootmgr --verbose
BootCurrent: 0001
Timeout: 10 seconds
BootOrder: 0001,0002
Boot0001* Arch nvidia DRM Linux HD(1,GPT,c43c0d00-8949-f540-94d0-081c9b3307ec,0x800,0x200000)/File(\boot\vmlinuz-linux)i.n.i.t.r.d.=./.b.o.o.t./.i.n.t.e.l.-.u.c.o.d.e...i.m.g. .i.n.i.t.r.d.=./.b.o.o.t./.i.n.i.t.r.a.m.f.s.-.l.i.n.u.x...i.m.g. .r.o.o.t.=./.d.e.v./.s.d.a.2. .q.u.i.e.t. .s.p.l.a.s.h. .r.w. .r.e.s.u.m.e.=./.d.e.v./.s.d.a.1. .n.v.i.d.i.a.-.d.r.m...m.o.d.e.s.e.t.=.1.
Boot0002* Grahams Linux HD(1,GPT,c43c0d00-8949-f540-94d0-081c9b3307ec,0x800,0x200000)/File(\boot\vmlinuz-linux)i.n.i.t.r.d.=./.b.o.o.t./.i.n.t.e.l.-.u.c.o.d.e...i.m.g. .i.n.i.t.r.d.=./.b.o.o.t./.i.n.i.t.r.a.m.f.s.-.l.i.n.u.x...i.m.g. .r.o.o.t.=./.d.e.v./.s.d.a.2. .r.w. .r.e.s.u.m.e.=./.d.e.v./.s.d.a.1. .n.v.i.d.i.a.-.d.r.m...m.o.d.e.s.e.t.=.1.

Output of fdisk:

[root@slaine graham]# fdisk -l
Disk /dev/sda: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000LM007-1R81
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: A1B30982-F3E6-FA4E-BAC3-D67282108606

Device         Start        End    Sectors  Size Type
/dev/sda1       2048    2099199    2097152    1G EFI System
/dev/sda2    2099200  211814399  209715200  100G Linux filesystem
/dev/sda3  211814400  278923263   67108864   32G Linux swap
/dev/sda4  278923264 3907029134 3628105871  1.7T Linux home

Lenovo
Hangs with a blank screen and then lands on the BIOS Boot menu where the EFI entry is available.
Selecting it just goes through the same cycle, blank and back to boot menu so lets ignore the Lenovo for now.
I only mention it here to point out that this is happening to two different models.

Any advice would be most welcome.

Last edited by graham (2020-06-26 09:25:19)

Offline

#2 2020-06-25 19:48:25

loqs
Member
Registered: 2014-03-06
Posts: 11,699

Re: [SOLVED] System not booting after kernel upgrade to 5.7.x

As the efibootmgr output shows forward slashes have you read https://bbs.archlinux.org/viewtopic.php?id=256273?
Edit:
5.7.6.arch1-1 contains the fix for the forward slash incompatibility.

Last edited by loqs (2020-06-25 20:17:55)

Offline

#3 2020-06-26 09:18:28

graham
Member
From: South Africa
Registered: 2020-06-25
Posts: 2
Website

Re: [SOLVED] System not booting after kernel upgrade to 5.7.x

loqs wrote:

5.7.6.arch1-1 contains the fix for the forward slash incompatibility.

This stopped working after 5.7.2 however as I can boot using the efi console I can confirm that my boot entry is indeed incorrect.

None the less fixing my forward slashes fixes the issue.
I was aware of this but had a brain burn moment *sigh* sad thanks for pointing me in the right direction.


Many thanks
Graham

Offline

Board footer

Powered by FluxBB