You are not logged in.

#1 2019-07-21 20:55:02

ticianolage
Member
Registered: 2017-02-15
Posts: 25

Can't boot after bios update

I have an arch dual boot with Windows on my laptop. After updating the bios firmware I can't boot at arch anymore, with my root partition not being located and going to emergency mode.

I'm using systemd-boot and used persistent block naming by label, but since the problem I've tried changing the arch entry to PARTUUID and also directly to the partition of root device (/dev/nvme0n1p5). It won't recognize anyway.

I've also tried to install grub, which worked but after loading everything freezed before the graphical interface shows up (and with no access to other tty).

I'm stuck with what to try next...

Offline

#2 2019-07-21 21:27:39

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: Can't boot after bios update


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2019-07-21 21:31:49

ticianolage
Member
Registered: 2017-02-15
Posts: 25

Re: Can't boot after bios update

This is not the problem. I can get into the arch boot entry, the problem is the boot not detecting my root partition.

Offline

#4 2019-07-21 21:39:46

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: Can't boot after bios update

Post the output of blkid and your systemd conf file. Also the output of efibootmgr.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#5 2019-07-22 13:40:53

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 15,515

Re: Can't boot after bios update

uefi/Bios firmware updates sometimes change defaults of values and reset them to the new value,  check your settings.

Especially settings related to 'secure boot' , 'fast boot' , choosing between windows 7 or windows 8/10 could have this effect.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Board footer

Powered by FluxBB