Arch Linux

carlosv

Member

Registered: 2019-04-29

Posts: 3

Can't boot after linux-lts upgrade to 4.19.37-1

I've been using arch just fine for the last couple of months, but a few hours ago linux-lts upgraded (for the first time since I started using arch, according to pacman log) from 4.19.34-1 to 4.19.37-1. On rebooting, I was faced with the following error:

:: running early hook [udev]
Warning: /lib/modules/4.19.37-1-lts/modules.devname not found - ignoring
Starting version 242.16-1-arch
:: running hook [udev]
:: Triggering uevents...
Waiting 10 seconds for device /dev/disk/by-uuid/<MYUUID> ...
Error: device 'UUID=<MYUUID>' not found. Skipping fsck.
:: mounting 'UUID=<MYUUID>' on real root
mount: /new_root: can't find UUID=<MYUUID>.
You are now being dropped into a emergency shell.
sh: can't access tty; job control turned off

The "emergency shell" below this was unresponsive.

After reading on a lot of similar questions, I booted from a live usb and mounted my root and boot partitions with no problems.
So, after trying to upgrade the system further, verifying UUID on boot loader (rEFInd) and on fstab, downgrading systemd (which had also just been upgraded) from 241.93-1 to 242.16-1, running mkinitcpio again, a bunch of different stuff, the only thing that worked was downgrading linux-lts back to 4.19.34-1.

So, I guess it works for now, but... Should I wait for the next linux-lts update and try again with that? Could it just be a problem with my machine/setup? Should I report it on the arch bug tracker?

Please let me know if there's any further information that could help answer any of these questions.

Last edited by carlosv (2019-05-03 01:27:44)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: Can't boot after linux-lts upgrade to 4.19.37-1

Looks like you're actually booting the -lts kernel, not the normal Arch kernels.

carlosv

Member

Registered: 2019-04-29

Posts: 3

Re: Can't boot after linux-lts upgrade to 4.19.37-1

Looks like you're actually booting the -lts kernel, not the normal Arch kernels.

Well, you're right in that it was actually the linux-lts upgrade that caused this problem and its downgrade that fixed it, not the actual linux upgrade (I'll edit the post to reflect that).
But, I believe I am running the actual linux kernel, not linux-lts. Below is the output of "uname -a":

Linux archlinux 5.0.9-arch1-1-ARCH #1 SMP PREEMPT Sat Apr 20 15:00:46 UTC 2019 x86_64 GNU/Linux

If I were running linux-lts, wouldn't that version show here instead of "5.0.9-arch1"?

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 78,516

Re: Can't boot after linux-lts upgrade to 4.19.37-1

linux is at 5.0.10 since 5 days.
You're most likely facing the same problem w/ linux and linux-lts, being you forget to mount the /boot partition when updating, thus the installed and booted kernel (lts or not) drop out of sync.

Output of "lsblk -f"?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: Can't boot after linux-lts upgrade to 4.19.37-1

Obviously that uname output was not obtained from the same boot as the error.

linux is at 5.0.10 since 5 days.
You're most likely facing the same problem w/ linux and linux-lts, being you forget to mount the /boot partition when updating, thus the installed and booted kernel (lts or not) drop out of sync.

Output of "lsblk -f"?

No, this isn't the /boot not mounted problem, the initramfs is getting updated, but not the kernel itself. Most likely a bootloader config issue.

Last edited by Scimmia (2019-05-03 14:00:45)

carlosv

Member

Registered: 2019-04-29

Posts: 3

Re: Can't boot after linux-lts upgrade to 4.19.37-1

Output of "lsblk -f"?

NAME   FSTYPE LABEL            UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                                
├─sda1 vfat   SYSTEM           E6BA-AFD7                               1.8G     9% /boot
├─sda2                                                                             
├─sda3 ntfs                    E4C4BB6EC4BB419A                                    
├─sda4 swap                    0f082da0-70d1-41c5-b5e9-488976a25512                [SWAP]
├─sda5 ext4                    43a1c22e-1956-4b93-aab1-99add09f1c49  228.3G     8% /
├─sda6 ntfs   Windows RE tools DC00BBA500BB84D5                                    
├─sda7 ntfs   SAMSUNG_REC2     A25E9B4C5E9B17DD                                    
└─sda8 vfat   SAMSUNG_REC      9EBE-875E                                           

sda5's UUID is the 'MYUUID' in the error output
sda3 is a windows root partition, sda2 microsoft reserved partition, and sda6-8 windows "recovery environments"

Last edited by carlosv (2019-05-03 17:15:10)

nomorewindows

Member

Registered: 2010-04-03

Posts: 3,544

Re: Can't boot after linux-lts upgrade to 4.19.37-1

Updated to linux-5.0.11 and seems to boot okay.

Obviously that uname output was not obtained from the same boot as the error.

linux is at 5.0.10 since 5 days.
You're most likely facing the same problem w/ linux and linux-lts, being you forget to mount the /boot partition when updating, thus the installed and booted kernel (lts or not) drop out of sync.

Output of "lsblk -f"?

No, this isn't the /boot not mounted problem, the initramfs is getting updated, but not the kernel itself. Most likely a bootloader config issue.

Hmmm....the vmlinuz with the initramfs-linux-lts.img no doubt...

Last edited by nomorewindows (2019-05-05 04:42:09)

---

I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.