[SOLVED] Kernel won't update with pacman -Syu

ifif14 · 2017-07-20 10:01:08

Hello everybody,

well, it's not the first time that after a full system upgrade my actual kernel (uname -a) is the version 4.10.13-1-ARCH. But the pacman -Qi linux points to the newest available kernel.

That causes core dumps of sddm, xorg etc. unless I rollback with pacman -U to the version 4.10.13-1-ARCH.

I checked the /boot directory. It seems to be mounted within my single partition. It is also writable by root.

I would appreciate any feedback.

Thanks

Last edited by ifif14 (2017-07-20 15:09:01)

Lone_Wolf · 2017-07-20 10:29:22

You did reboot after the kernel was upgraded, right ?

ifif14 · 2017-07-20 10:35:54

Yes, of course

Lone_Wolf wrote:

You did reboot after the kernel was upgraded, right ?

Slithery · 2017-07-20 10:43:27

Can you post the outputs of...

lsblk -f
cat /etc/fstab
mount

ifif14 · 2017-07-20 10:55:29

Here you go

$ lsblk -f
NAME        FSTYPE LABEL UUID                                 MOUNTPOINT
nvme0n1                                                       
├─nvme0n1p1 vfat   ESP   267E-43F3                            
├─nvme0n1p2 vfat   OS    1CA8-B9BE                            
├─nvme0n1p3 ext4         b705d74e-9248-4f4c-8924-babfd2058bb2 /
└─nvme0n1p4 swap         6378a200-9d15-403c-ba2c-8052f11d79ce [SWAP]


$ cat /etc/fstab
# 
# /etc/fstab: static file system information
#
# <file system> <dir>   <type>  <options>       <dump>  <pass>
# /dev/nvme0n1p3
UUID=b705d74e-9248-4f4c-8924-babfd2058bb2       /               ext4            rw,relatime,data=ordered        0 1
efivarfs        /sys/firmware/efi/efivars       efivarfs        ro,nosuid,nodev,noexec,noatime 0 0
# /dev/nvme0n1p3
UUID=b705d74e-9248-4f4c-8924-babfd2058bb2       /               ext4            rw,relatime,data=ordered        0 1



$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=8152860k,nr_inodes=2038215,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
efivarfs on /sys/firmware/efi/efivars type efivarfs (ro,nosuid,nodev,noexec,noatime)
/dev/nvme0n1p3 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1631456k,mode=700,uid=1000,gid=1000)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

slithery wrote:

Can you post the outputs of...
lsblk -f
cat /etc/fstab
mount

loqs · 2017-07-20 11:22:41

What is the output of

$ pacman -Q linux
$ file /boot/vmlinuz-linux

Then mount the ESP. Is there a vmlinuz-linux in the root of that filesystem? If so what is the output of file on that vmlinuz-linux?
Edit:
removed duplicate file
Edit2:
that not hat

Last edited by loqs (2017-07-20 11:49:28)

WorMzy · 2017-07-20 11:23:04

Your ESP is not mounted. I am going to guess that you have confused the efivars with your ESP. Your ESP is /dev/nve0n1p1 and you should be mounting it to /boot. You don't need the efivars line in fstab, and you don't need to specify your root partition twice.

You may need to downgrade your kernel to the one reported by 'uname -a' before you are able to mount your ESP, due to you needing the vfat kernel module to mount it. Once you have the ESP mounted, reinstall your kernel and make sure to add a line in your fstab for the ESP.

ifif14 · 2017-07-20 11:36:03

Well, that's after rolling back, the versions match

$ file /boot/vmlinuz-linux
/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 4.10.13-1-ARCH (builduser@tobias) #1 SMP PREEMPT Thu Apr 27 12:15:09 CEST 2017, RO-rootFS, swap_dev 0x4, Normal VGA
$ pacman -Q linux
linux 4.10.13-1

loqs wrote:

What is the output of
$ pacman -Q linux
$ file /boot/vmlinuz-linux
Then mount the ESP. Is there a vmlinuz-linux in the root of that filesystem? If so what is the output of file on hat vmlinuz-linux?
Edit:
removed duplicate file

ifif14 · 2017-07-20 14:10:53

That has worked, I added

LABEL=ESP       /boot vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0      2

to my /etc/fstab, now I'm up to the newest kernel.

That was very confusing, that the /boot folder is also on the root partition (probably created during previous updates).

Thanks a lot. Can be closed.

WorMzy wrote:

Your ESP is not mounted. I am going to guess that you have confused the efivars with your ESP. Your ESP is /dev/nve0n1p1 and you should be mounting it to /boot. You don't need the efivars line in fstab, and you don't need to specify your root partition twice.
You may need to downgrade your kernel to the one reported by 'uname -a' before you are able to mount your ESP, due to you needing the vfat kernel module to mount it. Once you have the ESP mounted, reinstall your kernel and make sure to add a line in your fstab for the ESP.

Slithery · 2017-07-20 14:14:47

This thread doesn't need closing, you need to edit your 1st post and prepend [SOLVED] to the title.

Arch Linux

#1 2017-07-20 10:01:08

[SOLVED] Kernel won't update with pacman -Syu

#2 2017-07-20 10:29:22

Re: [SOLVED] Kernel won't update with pacman -Syu

#3 2017-07-20 10:35:54

Re: [SOLVED] Kernel won't update with pacman -Syu

#4 2017-07-20 10:43:27

Re: [SOLVED] Kernel won't update with pacman -Syu

#5 2017-07-20 10:55:29

Re: [SOLVED] Kernel won't update with pacman -Syu

#6 2017-07-20 11:22:41

Re: [SOLVED] Kernel won't update with pacman -Syu

#7 2017-07-20 11:23:04

Re: [SOLVED] Kernel won't update with pacman -Syu

#8 2017-07-20 11:36:03

Re: [SOLVED] Kernel won't update with pacman -Syu

#9 2017-07-20 14:10:53

Re: [SOLVED] Kernel won't update with pacman -Syu

#10 2017-07-20 14:14:47

Re: [SOLVED] Kernel won't update with pacman -Syu

Board footer