Arch Linux

Syncopated

Member

Registered: 2015-02-07

Posts: 14

Lots of things fail after upgrade to linux-4.0.7-2 and reboot

I was running 4.0.5-1 initially. Then I upgraded to 4.0.6-1 and then to 4.0.7-2. After that, I rebooted. All this was over a span of 1-2 weeks.

After I rebooted, SDDM stopped being able to read my keyboard or mouse input. dmesg had an error about "Failed to start Load Kernel Modules". "ip link" showed only the "lo" interface. Even though "pacman -Qi" showed that 4.0.7-2 was installed, "uname -a" showed that 4.0.5-1 was running. Neither reinstalling 4.0.7-2 nor downgrading to 4.0.6-1 help. Downgrading to 4.0.5-1 did and it seems my system is back to normal. Any idea what's going on and what I can do to make the kernel upgrade work?

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: Lots of things fail after upgrade to linux-4.0.7-2 and reboot

Sounds like you upgraded without /boot mounted.

Syncopated

Member

Registered: 2015-02-07

Posts: 14

Re: Lots of things fail after upgrade to linux-4.0.7-2 and reboot

I've booted into 4.0.5-1 and /boot is not mounted. In fact, every line in my /etc/fstab is commented out or empty, although /dev/sda2 does look like a boot partition. Is there supposed to be an entry in /etc/fstab for the /boot parttion? If so, I don't know how /etc/fstab got into its current state. Should I manually add an entry for /boot? My linux command-line looks like this:

initrd=\intel-ucode.img initrd=\initramfs-linux.img root=/dev/mapper/root rootfstype=ext4 rw rootflags=rw,noatime,discard,data=ordered cryptdevice=/dev/sda3:root cgroup_disable=memory add_efi_memmap

Last edited by Syncopated (2015-07-09 14:51:42)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: Lots of things fail after upgrade to linux-4.0.7-2 and reboot

Personally, yes, I mount my boot partition in fstab. Others rely on systemd's auto-generated mount units.

post

Member

Registered: 2015-02-15

Posts: 32

Re: Lots of things fail after upgrade to linux-4.0.7-2 and reboot

Same here, linux-4.0.7-2 not booting properly upgrading from 4.0.6-1.

/etc/fstab is empty, /boot currently is a simple folder in / which contains the updated initramfs-linux.img etc.

I once installed gummiboot, /dev/sda1 (gpt, fat32, boot, esp) should be my $esp.

With the wrong /boot, bootctl status says:

File system "/boot" is not a FAT EFI System Partition (ESP) file system.

How shall we fix it (without editing fstab)? Delete the wrong /boot folder and issue bootctl install? Would it create the systemd automount for the boot unit?

post

Member

Registered: 2015-02-15

Posts: 32

Re: Lots of things fail after upgrade to linux-4.0.7-2 and reboot

Ok, I deleted the local /boot folder, added an /boot entry into /etc/fstab for my /dev/sda1 (is this necessary/recommended?), mounted it, did gummiboot remove and bootctl install. After pacman -Syu and reboot, uname -r shows 4.0.7-2-ARCH. Cheers