[SOLVED] After kernel 4.19 can't mount UEFI partition during boot

MickeyRat · 2018-12-31 17:57:10

I've been trying to fix this all morning.

System info:

Dual boot windows/arch UEFI
Grub boot loader
/root and /home are LVM partitions
1GB FAT32 UEFI partition mounted at /boot

After kernel 4.19 upgrade the /boot partition fails to mount. When I enter the root password to get to the maintenance console and attempt to mount the partition manually, I get unknown file system type vfat.

Windows still boots fine.

What I've tried:

arch-chroot from arch CD with all linux partitions mounted and UEFI partition mounted at /boot.
pacman -S linux <---- upgraded to 4.20 kernel and performed mkinitcpio
grub-mkconfig -o /boot/grub/grub.cfg

While I was at it, I made sure there is nothing in the /boot partition prior to mounting the UEFI partition there.

So far nothing's worked. Any help would be appreciated.

Last edited by MickeyRat (2019-01-01 18:31:31)

loqs · 2018-12-31 18:12:05

When you reach the maintenance console what is the output of

uname -a
pacman -Q linux

MickeyRat · 2018-12-31 18:49:31

Thanks for the reply.

uname -a 4.19 kernel
pacman -Q linux 4.20 kernel

loqs · 2018-12-31 19:57:40

What is the contents of /boot/grub/grub.cfg and the output of

efibootmgr -v
# parted -l
# blkid

MickeyRat · 2018-12-31 21:16:02

Thanks for the reply.

I have a bit of addiional data. I tried creating a 1GB FAT32 partition on a flash drive. When I tried to mount it from the maintenance console, I got the same unknown file system error. I think that confirms that the issue is with the UEFI filesystem type and not the contents.

There's also some info I neglected to mention. On this system, windows was installed with a 100MB UEFI partition. That turned out to be too small even for windows. I created a 1GB partition, copied the contents of the original MS EFI partition there, set the partition flags to reflect the change and updated fstab. It's been working for both windows and Linux until this kernel upgrade. It still works for windows.

efibootmgr -v

BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0006,0002,0004,0000,0001,0003
Boot0000* Hitachi HTS545025B9A300 0 	BBS(16,,0x0)
Boot0001* TS32GMSA370                             	BBS(17,,0x0)
Boot0002* Windows Boot Manager	HD(2,GPT,aaebb590-7d80-4272-b94c-41ed9bae502f,0xfa000,0x31800)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...,................
Boot0003* SATA2:TSSTcorp CDDVDW SH-S203N	BBS(19,,0x0)
Boot0004* UEFI: Built-in EFI Shell	VenMedia(5023b95c-db26-429b-a648-bd47664c8012)
Boot0006* GRUB	HD(2,GPT,aaebb590-7d80-4272-b94c-41ed9bae502f,0xfa000,0x31800)/File(\EFI\GRUB\grubx64.efi)

parted -l

Model: ATA TS32GMSA370 (scsi)
Disk /dev/sda: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  32.0GB  32.0GB                     lvm


Model: Hitachi HTS545025B9A300 (scsi)
Disk /dev/sdb: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name  Flags
 1      1049kB  250GB  250GB  ext4


Model: ATA Samsung SSD 850 (scsi)
Disk /dev/sdc: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  524MB   523MB   ntfs         Basic data partition          hidden, diag
 2      524MB   628MB   104MB   fat32        Microsoft reserved            msftdata
 3      628MB   645MB   16.8MB               Microsoft reserved partition  msftres
 6      645MB   1719MB  1074MB  fat32        EFI Partition                 boot, esp
 4      1719MB  160GB   158GB   ntfs         Basic data partition          msftdata
 5      161GB   512GB   351GB                                              lvm


Model: ATA ExcelStor Techno (scsi)
Disk /dev/sdd: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name  Flags
 1      1049kB  25.8GB  25.8GB  linux-swap(v1)

blkid

/dev/sda1: UUID="8Dgxy0-Mwes-SKpZ-9d7a-9Xfb-hRwZ-7Yvn96" TYPE="LVM2_member" PARTUUID="89dbbd54-ca2b-3241-b8ec-4f2a0d9c60f3"
/dev/sdc1: LABEL="Recovery" UUID="A85E75F65E75BD9E" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="f1736ea1-3202-4078-b2a6-39bba11f0191"
/dev/sdc2: UUID="1C78-0C8F" TYPE="vfat" PARTLABEL="Microsoft reserved" PARTUUID="aaebb590-7d80-4272-b94c-41ed9bae502f"
/dev/sdc3: PARTLABEL="Microsoft reserved partition" PARTUUID="6ff03d96-fb52-4206-811e-e103ac6a0fad"
/dev/sdc4: UUID="9288803E888022B9" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="db43de21-ca16-48f5-91c8-cd3b73750741"
/dev/sdc5: UUID="woC2bD-ripn-35Gk-fK70-YGfD-jxPF-xbqCMJ" TYPE="LVM2_member" PARTUUID="9995e3de-c5b1-7e40-bf84-a4c947e98bf3"
/dev/sdc6: UUID="0A14-E4C3" TYPE="vfat" PARTLABEL="EFI Partition" PARTUUID="2ad4827f-f7b2-49db-98aa-e7fd1d25b050"
/dev/sdb1: UUID="5637fe41-3a9b-4889-8669-1f1a0a61e9f6" TYPE="ext4" PARTUUID="b1241196-3cf7-47cc-be9b-a87fb29bfc6f"
/dev/sdd1: UUID="8d51c6ae-a9b7-4101-918a-631079305d9e" TYPE="swap" PARTUUID="b10bff95-8872-304b-aedc-4eaeea463351"
/dev/mapper/vg1-sys: UUID="c81a62b9-caba-4d6f-8f3a-f949e1f8747a" TYPE="ext4"
/dev/mapper/vg1-home: UUID="cc8b8078-b0cd-4847-b764-951525eebc99" TYPE="ext4"

Last edited by MickeyRat (2018-12-31 21:21:28)

jasonwryan · 2018-12-31 21:17:30

MickeyRat wrote:

Thanks for the reply.
uname -a 4.19 kernel
pacman -Q linux 4.20 kernel

That isn't the actual output of either command; why are you obscuring it?

loqs · 2018-12-31 21:21:39

You changed the ESP in the fstab but did not change it in efibootmgr.
Edit:
I believe grub, the kernel and initrd are still being loaded from the original ESP.

Last edited by loqs (2018-12-31 21:22:37)

MickeyRat · 2018-12-31 21:29:17

There's no reason to assume that I was trying to obscure it. I just didn't want to type it or bother mounting a flash drive to capture. I thought the kernel version was what you were after. Here's the actual output:

uname -a

Linux groucho 4.19.12-arch1-1-ARCH #1 SMP PREEMPT Fri Dec 21 13:56:54 UTC 2018 x86_64 GNU/Linux

pacman -Q linux

linux 4.20.arch1-1

jasonwryan · 2018-12-31 21:32:47

MickeyRat wrote:

There's no reason to assume that I was trying to obscure it.

Other than the fact that you have a history of posting here about non-Arch systems.

Linux groucho 4.19.12-arch1-1-ARCH #1 SMP PREEMPT Fri Dec 21 13:56:54 UTC 2018 x86_64 GNU/Linux

pacman -Q linux

linux 4.20.arch1-1

So, that's why you can't access the necessary modules.

MickeyRat · 2019-01-01 18:30:56

loqs wrote:

You changed the ESP in the fstab but did not change it in efibootmgr.
Edit:
I believe grub, the kernel and initrd are still being loaded from the original ESP.

You were correct. I managed to get everything moved back to the original partition but, I was still determined to get more room on the EFI partition. That took a reinstall of Windows but, I was able to retain the Arch installation.

Thanks everyone for your help.

Arch Linux

#1 2018-12-31 17:57:10

[SOLVED] After kernel 4.19 can't mount UEFI partition during boot

#2 2018-12-31 18:12:05

Re: [SOLVED] After kernel 4.19 can't mount UEFI partition during boot

#3 2018-12-31 18:49:31

Re: [SOLVED] After kernel 4.19 can't mount UEFI partition during boot

#4 2018-12-31 19:57:40

Re: [SOLVED] After kernel 4.19 can't mount UEFI partition during boot

#5 2018-12-31 21:16:02

Re: [SOLVED] After kernel 4.19 can't mount UEFI partition during boot

#6 2018-12-31 21:17:30

Re: [SOLVED] After kernel 4.19 can't mount UEFI partition during boot

#7 2018-12-31 21:21:39

Re: [SOLVED] After kernel 4.19 can't mount UEFI partition during boot

#8 2018-12-31 21:29:17

Re: [SOLVED] After kernel 4.19 can't mount UEFI partition during boot

#9 2018-12-31 21:32:47

Re: [SOLVED] After kernel 4.19 can't mount UEFI partition during boot

#10 2019-01-01 18:30:56

Re: [SOLVED] After kernel 4.19 can't mount UEFI partition during boot

Board footer