[SOLVED] Upgrading to 4.0.4 broke my UEFI boot

66666thats6sixes · 2015-05-25 03:11:20

I've since reverted to 3.19.3 and everything is fine, but I'd like to fix this issue because I can't boot with the new kernel. I get errors that it can't mount /boot and /media since 'vfat' and 'btrfs' are unsupported types and then it drops me into a recovery shell. A peak at journalctl shows that it was still trying to boot 3.19.3, like it didn't see the new kernel at all, and so I would assume that the problem lies there somewhere. Any idea what I need to do?

EDIT: Fixed by reinstalling grub, somehow managed to have two copies of /boot on different partitions.

Last edited by 66666thats6sixes (2015-05-26 02:51:02)

jasonwryan · 2015-05-25 03:38:33

Sounds like your /boot wan't mounted when you upgraded the kernel...

66666thats6sixes · 2015-05-25 04:28:47

That doesn't appear to be the case -- tried again ensuring that /boot was mounted, and no luck.

Head_on_a_Stick · 2015-05-25 10:17:54

Upgrade to the latest kernel then post the output of:

ls /boot

Trilby · 2015-05-25 11:06:40

Also, after updating, please post the output of the following:

pac -Q linux linux-headers

66666thats6sixes · 2015-05-25 18:39:38

[dsampson@tcl ~]$ ls /boot
EFI  grub  initramfs-linux-fallback.img  initramfs-linux.img  shellx64.efi  vmlinuz-linux
[dsampson@tcl ~]$ pacman -Q linux linux-headers
linux 4.0.4-2
error: package 'linux-headers' was not found

Scimmia · 2015-05-25 18:49:21

66666thats6sixes wrote:

That doesn't appear to be the case -- tried again ensuring that /boot was mounted, and no luck.

OK, so boot is mounted, is that where your bootloader is looking?

Head_on_a_Stick · 2015-05-25 18:51:04

Post your grub.cfg plz.

66666thats6sixes · 2015-05-25 19:12:13

[dsampson@tcl ~]$ cat /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt 
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  d0118cf0-b576-44fb-99d1-d9b11552a8e3
else
  search --no-floppy --fs-uuid --set=root d0118cf0-b576-44fb-99d1-d9b11552a8e3
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=1
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=1
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-d0118cf0-b576-44fb-99d1-d9b11552a8e3' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_gpt 
	insmod fat
	set root='hd0,gpt1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  A42D-5B4C
	else
	  search --no-floppy --fs-uuid --set=root A42D-5B4C
	fi
	echo	'Loading Linux linux ...'
	linux	/vmlinuz-linux root=UUID=d0118cf0-b576-44fb-99d1-d9b11552a8e3 rw  quiet
	echo	'Loading initial ramdisk ...'
	initrd	 /initramfs-linux.img
}
submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-d0118cf0-b576-44fb-99d1-d9b11552a8e3' {
	menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-d0118cf0-b576-44fb-99d1-d9b11552a8e3' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt 
		insmod fat
		set root='hd0,gpt1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  A42D-5B4C
		else
		  search --no-floppy --fs-uuid --set=root A42D-5B4C
		fi
		echo	'Loading Linux linux ...'
		linux	/vmlinuz-linux root=UUID=d0118cf0-b576-44fb-99d1-d9b11552a8e3 rw  quiet
		echo	'Loading initial ramdisk ...'
		initrd	 /initramfs-linux.img
	}
	menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-d0118cf0-b576-44fb-99d1-d9b11552a8e3' {
		load_video
		set gfxpayload=keep
		insmod gzio
		insmod part_gpt 
		insmod fat
		set root='hd0,gpt1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1  A42D-5B4C
		else
		  search --no-floppy --fs-uuid --set=root A42D-5B4C
		fi
		echo	'Loading Linux linux ...'
		linux	/vmlinuz-linux root=UUID=d0118cf0-b576-44fb-99d1-d9b11552a8e3 rw  quiet
		echo	'Loading initial ramdisk ...'
		initrd	 /initramfs-linux-fallback.img
	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###

Head_on_a_Stick · 2015-05-25 19:17:55

Sorry, I should have asked for this as well:

lsblk -f

66666thats6sixes · 2015-05-25 19:37:21

[dsampson@tcl boot]$ lsblk -f
NAME   FSTYPE LABEL  UUID                                 MOUNTPOINT
sda                                                       
├─sda1 vfat          A42D-5B4C                            /boot
└─sda2 ext4          d0118cf0-b576-44fb-99d1-d9b11552a8e3 /
sdb                                                       
├─sdb1                                                    
├─sdb2 btrfs  mainhd a0a86b17-c75f-473a-8078-9ecdebd63f79 
├─sdb3 swap          d626d5d0-7f74-4043-86d3-4dd30f0e35ab 
└─sdb4 ext4          c159d88f-5c5c-49e5-aee9-8ae30304cbeb 
sdc    btrfs         c5d7abfe-2c1f-4e10-b3c7-9d027545a381 /media

The way I have it set up now sdb isn't doing anything, it's an old hard drive that was replaced by sda (an ssd).

Last edited by 66666thats6sixes (2015-05-25 19:38:21)

Head_on_a_Stick · 2015-05-25 19:47:03

66666thats6sixes wrote:

A peak at journalctl shows that it was still trying to boot 3.19.3

Can we see those logs?

Some tips here on extracting data from journalctl:
http://0pointer.de/blog/projects/journalctl.html

66666thats6sixes · 2015-05-25 20:05:05

Here is a reduced (-p 5) version of journalctl from the last boot before I reverted to the old kernel:

Linux version 3.19.3-3-ARCH (builduser@tobias) (gcc version 4.9.2 20150304 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Apr 8 14:10:00 CEST 2015
ACPI: RSDP 0x00000000BB114000 000024 (v02 ALASKA)
ACPI: XSDT 0x00000000BB114070 00005C (v01 ALASKA A M I    01072009 AMI  00010013)
ACPI: FACP 0x00000000BB11B9A0 0000F4 (v04 ALASKA A M I    01072009 AMI  00010013)
ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20141107/tbfadt-649)
ACPI: DSDT 0x00000000BB114168 007832 (v02 ALASKA A M I    00000000 INTL 20051117)
ACPI: FACS 0x00000000BBE75F80 000040
ACPI: APIC 0x00000000BB11BA98 00009E (v03 ALASKA A M I    01072009 AMI  00010013)
ACPI: FPDT 0x00000000BB11BB38 000044 (v01 ALASKA A M I    01072009 AMI  00010013)
ACPI: MCFG 0x00000000BB11BB80 00003C (v01 ALASKA A M I    01072009 MSFT 00010013)
ACPI: HPET 0x00000000BB11BBC0 000038 (v01 ALASKA A M I    01072009 AMI  00000005)
ACPI: SSDT 0x00000000BB11BC88 001714 (v01 AMD    POWERNOW 00000001 AMD  00000001)
ACPI: BGRT 0x00000000BB11BC50 000038 (v00 ALASKA A M I    01072009 AMI  00010013)
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=d0118cf0-b576-44fb-99d1-d9b11552a8e3 rw quiet
ACPI: All ACPI Tables successfully acquired
Ignoring BGRT: invalid status 0 (expected 1)
ACPI: Executed 2 blocks of module-level executable AML code
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20141107/hwxface-580)
ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20141107/hwxface-580)
Initialise system trusted keyring
VFS: Disk quotas dquot_6.5.2
Key type big_key registered
Loading compiled-in X.509 certificates
random: systemd-tmpfile urandom read with 1 bits of entropy available
SCSI subsystem initialized
scsi 0:0:0:0: Direct-Access     ATA      SSD2SC120G1CS175 1101 PQ: 0 ANSI: 5
scsi 1:0:0:0: Direct-Access     ATA      ST3160812AS      E    PQ: 0 ANSI: 5
scsi 2:0:0:0: Direct-Access     ATA      WDC WD20EFRX-68E 0A80 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 1:0:0:0: [sdb] 312581808 512-byte logical blocks: (160 GB/149 GiB)
sd 2:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
sd 2:0:0:0: [sdc] 4096-byte physical blocks
sd 1:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdc] Write Protect is off
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] Attached SCSI disk
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 2:0:0:0: [sdc] Attached SCSI disk
systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
Failed to start Load Kernel Modules.
Unit systemd-modules-load.service entered failed state.
systemd-modules-load.service failed.
Failed to lookup alias 'vboxdrv': Function not implemented
random: nonblocking pool is initialized
media.mount mount process exited, code=exited status=32
Failed to mount /media.
Dependency failed for Local File Systems.
Job local-fs.target/start failed with result 'dependency'.
Unit media.mount entered failed state.
boot.mount: Directory /boot to mount over is not empty, mounting anyway.
boot.mount mount process exited, code=exited status=32
Failed to mount /boot.
Unit boot.mount entered failed state.
Device dev-disk-by\x2dpartlabel-Linux\x5cx20filesystem.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:11.0/ata1/host0/target
Failed at step EXEC spawning /bin/plymouth: No such file or directory
Job sys-subsystem-net-devices-enp2s0.device/start timed out.
Timed out waiting for device sys-subsystem-net-devices-enp2s0.device.
Job sys-subsystem-net-devices-enp2s0.device/start failed with result 'timeout'.
Shutting down.

Head_on_a_Stick · 2015-05-25 20:10:00

66666thats6sixes wrote:

boot.mount: Directory /boot to mount over is not empty, mounting anyway.

Unmount your current /boot partition and see if there is anything "underneath" it:

# umount -R /dev/sda1
ls /
ls /boot # if it's there, of course...

66666thats6sixes · 2015-05-25 20:13:17

Aha! There is another copy of boot files hiding there. I'm going to copy those to a backup directory and remove them and see what happens.

EDIT: That was a terrible idea. Had to muck around in grub rescue mode but when I did get it booted I had the same problem is before. While in grub rescue I tried to boot using the boot partition on sda but it said "unknown filesystem" or something similar. Anyways, how should I go about fixing this?

Last edited by 66666thats6sixes (2015-05-25 20:23:49)

Head_on_a_Stick · 2015-05-25 20:46:22

66666thats6sixes wrote:

While in grub rescue I tried to boot using the boot partition on sda but it said "unknown filesystem" or something similar.

You have to load the correct GRUB modules first for that to work:

insmod fat
insmod part_gpt
insmod gzio

I think what is happening here is that GRUB is parsing your "hidden" /boot and the configuration files contained within and these are not being updated whilst /dev/sda1 is mounted in your running system.

I think you should try re-installing GRUB and regenerate the configuration file.

66666thats6sixes · 2015-05-26 02:12:25

Success!

[dsampson@tcl ~]$ uname -a
Linux tcl.sics.co 4.0.4-2-ARCH #1 SMP PREEMPT Fri May 22 03:05:23 UTC 2015 x86_64 GNU/Linux

Thanks for all of your help!

ewaller · 2015-05-26 02:48:49

Great! Remember to edit your first post and modify the title by prepending [SOLVED]

Arch Linux

#1 2015-05-25 03:11:20

[SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#2 2015-05-25 03:38:33

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#3 2015-05-25 04:28:47

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#4 2015-05-25 10:17:54

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#5 2015-05-25 11:06:40

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#6 2015-05-25 18:39:38

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#7 2015-05-25 18:49:21

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#8 2015-05-25 18:51:04

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#9 2015-05-25 19:12:13

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#10 2015-05-25 19:17:55

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#11 2015-05-25 19:37:21

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#12 2015-05-25 19:47:03

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#13 2015-05-25 20:05:05

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#14 2015-05-25 20:10:00

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#15 2015-05-25 20:13:17

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#16 2015-05-25 20:46:22

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#17 2015-05-26 02:12:25

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

#18 2015-05-26 02:48:49

Re: [SOLVED] Upgrading to 4.0.4 broke my UEFI boot

Board footer