[probably solved: just bad partition mapping] kernel 5.4.2 breaks boot

lman · 2019-12-11 08:54:35

Hi guys,

after trying to upgrade to 5.4.2 I can no longer boot:

Module vfat was not found, Can't mount /boot

When I try to modprobe vfat I get something like

No such module in /lib/modules/5.4.1-*

So there is something wrong with the initramfs build... or hooks that are supposed to generate them, since it's still looking for 5.4.1 build...
For now I've solved this by downgrading linux to 5.4.1. I've tried upgrading again to 5.4.2. The same result.
Any advice?

Last edited by lman (2019-12-11 12:30:17)

V1del · 2019-12-11 09:03:12

Well what's the output of the initramfs build? FWIW most of the time this happens if you have your kernel images on your UEFIs ESP and forgot to mount said ESP partition to /boot prior to doing the upgrade. (Or the less common other variant of this, you actually did have the ESP mounted on /boot but use a boot loader that expects the initramfs on the root partition.

lman · 2019-12-11 10:28:53

$ sudo pacman -S linux                               (12-11 11:18)
resolving dependencies...
looking for conflicting packages...

Package (1)  Old Version    New Version    Net Change

core/linux   5.4.1.arch1-1  5.4.2.arch1-1    0.03 MiB

Total Installed Size:  73.15 MiB
Net Upgrade Size:       0.03 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                       [---------------------------] 100%
(1/1) checking package integrity                     [---------------------------] 100%
(1/1) loading package files                          [---------------------------] 100%
(1/1) checking for file conflicts                    [---------------------------] 100%
(1/1) checking available disk space                  [---------------------------] 100%
:: Running pre-transaction hooks...
(1/1) Removing linux initcpios...
:: Processing package changes...
(1/1) upgrading linux                                [---------------------------] 100%
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.4.2-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [encrypt]
  -> Running build hook: [lvm2]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 5.4.2-arch1-1
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
  -> Running build hook: [encrypt]
  -> Running build hook: [lvm2]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

mounted stuff:

$ cat /proc/mounts                                        (12-11 11:20)
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
sys /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
dev /dev devtmpfs rw,nosuid,relatime,size=16349420k,nr_inodes=4087355,mode=755 0 0
run /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0
efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
/dev/mapper/root / ext4 rw,relatime 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup2 /sys/fs/cgroup/unified cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
none /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/rdma cgroup rw,nosuid,nodev,noexec,relatime,rdma 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=18583 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0
mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,nosuid,nodev,noexec,relatime 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0
configfs /sys/kernel/config configfs rw,nosuid,nodev,noexec,relatime 0 0
/dev/nvme1n1p1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/mapper/tmp /tmp tmpfs rw,relatime 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=3272544k,mode=700,uid=1000,gid=1000 0 0
gvfsd-fuse /run/user/1000/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
fusectl /sys/fs/fuse/connections fusectl rw,nosuid,nodev,noexec,relatime 0 0

After the upgrade I can see

/lib/modules/5.4.2-*

folder, but not after reboot...
This thing is really weird. As if the data didn't get written to the disk by the encryption (using LUKS).

Lone_Wolf · 2019-12-11 12:08:47

/dev/mapper/root / ext4 rw,relatime 0 0

/dev/nvme1n1p1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/mapper/tmp /tmp tmpfs rw,relatime 0 0

Looks weird, please post lsblk -f .

Why are you mounting /dev/mapper/tmp to /tmp with filesystem tmpfs ?
What bootloader are you using ?

Edit : Are you using a Silicon Motion 2263 controller for the nvme-drive ?
https://bbs.archlinux.org/viewtopic.php?id=251178

Last edited by Lone_Wolf (2019-12-11 12:11:21)

lman · 2019-12-11 12:25:01

Ohh, you are onto something. FFS - I installed linux on a completely separate drive, but seemingly the device mapping got f* up.

$ lsblk -f                                            (12-11 13:22)
NAME     FSTYPE LABEL  UUID                                   FSAVAIL FSUSE% MOUNTPOINT
nvme1n1                                                                      
├─nvme1n1p1
│        vfat   SYSTEM 52FE-CCB2                               197.1M    33% /boot
├─nvme1n1p2
│                                                                            
├─nvme1n1p3
│        BitLoc                                                              
├─nvme1n1p4
│        ntfs   WinRE tools
│                      50F2FFB0F2FF9904                                      
└─nvme1n1p5
         ntfs   BIOS_RVY
                       FA6E01FB6E01B185                                      
nvme0n1                                                                      
├─nvme0n1p1
│        vfat          832C-400F                               435.5M    15% /mnt/temp
└─nvme0n1p2
         LVM2_m        7u1hmP-o6CX-ZHey-QRlP-Owkk-v2vF-soIAy0                
  ├─lvm-tmp
  │                                                                          
  │ └─tmp
  │      ext2          98ab199a-3298-4c71-bc6f-87d7e576f41d     15.6G     0% /tmp
  └─lvm-lvroot
         crypto        92300c06-5009-421c-a7bd-d9de7cc3bc92                  
    └─root
         ext4          87f52360-9f10-4189-9d2a-13608955a59b    400.1G     7% /

So my actual boot partition should be one the nvme0n1 drive, not on the nvme1n1 So it messed up the windows system partition :S I mounted on /mnt/temp => it actually contains the right structure and built images.
Any tips how to fix this, other than editing fstab and using the blkid for the mountpoint for the boot?

And I'm using grub.

Last edited by lman (2019-12-11 12:26:37)

Lone_Wolf · 2019-12-12 09:51:56

It may be a bit more complicated then that since you're using lvm & LUKS.

Read https://wiki.archlinux.org/index.php/EF … _partition and follow the links, especially the talk section.

Since you're using grub, I'm inclined to suggest mounting the esp at /efi and have /boot on the / partition .
run mkinitcpio -p linux to get the files to /boot, then reconfigure grub and see if booting works.

Arch Linux

#1 2019-12-11 08:54:35

[probably solved: just bad partition mapping] kernel 5.4.2 breaks boot

#2 2019-12-11 09:03:12

Re: [probably solved: just bad partition mapping] kernel 5.4.2 breaks boot

#3 2019-12-11 10:28:53

Re: [probably solved: just bad partition mapping] kernel 5.4.2 breaks boot

#4 2019-12-11 12:08:47

Re: [probably solved: just bad partition mapping] kernel 5.4.2 breaks boot

#5 2019-12-11 12:25:01

Re: [probably solved: just bad partition mapping] kernel 5.4.2 breaks boot

#6 2019-12-12 09:51:56

Re: [probably solved: just bad partition mapping] kernel 5.4.2 breaks boot

Board footer