Multi boot system loading wrong kernel

Support
1

I hope this is the right place to ask this, this is my first post to the forum. I believe the root of the problem is that my grub and/or rEFInd are not updating their boot entries properly.

Problem: pamac and pacman both install kernel 5.13, but after reboot the system loads kernel 5.10 and does not show 5.13 as a choice.

Hereā€™s the steps that lead to this problem:

  1. Started with Windows 10 on a 1 TB nvme0 drive.
  2. Installed Manjaro on 400 GB ext4 partition on that nvme0.
  3. Installed rEFInd to manage dual boot.
  4. Added second 1 TB nvme1 as btrfs, Manjaro added /boot/efi to nvme1.

The system boots to any of the 3 OSā€™s. On startup, rEFInd comes up with 4 entries, Win10, EFI\Manjaro\grubx64.efi, Boot fallback loader from EFI and Manjaro from ext4 volume. Option 1 loads Windows, Option 4 loads my old Manjaro install and option 3 loads a Grub Rescue prompt, but option 2 loads a Grub menu with 5 more options:

  • Manjaro Linux
  • Advanced options for Manjaro Linux
  • Windows Boot Manager
  • Manjaro Linux on nvme1
  • Advanced options for Manjaro on nvme1

Option 1 and 2 boot my old install with kernel 5.11
Option 4 and 5 boot the new install with kernel 5.10

/boot from nvme1 shows kernel 5.10 and 5.13
/boot from nvme0 shows kernel 5.11

Iā€™ve been using the second rEFInd entry and 4th grub entry and everything runs fine, but Iā€™ve been getting notices to update my kernel.

So the question is, how do I get my new Manjaro to boot with 5.13 and untangle rEFInd and grub? I donā€™t need to keep the old Manjaro install, but I would like to keep Windows around just in case. I like how rEFInd recovers after Windows removes dual boot, so I would like to keep rEFInd around.

The output to inxi --admin --verbosity=7 --filter --no-host --width is:

System:
  Kernel: 5.3.18-59.19-default x86_64 bits: 64 compiler: gcc v: 7.5.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.3.18-59.19-default 
  root=UUID=8bef70f0-1ae6-4423-9936-4d9ce8bd75f4 splash=silent 
  resume=/dev/disk/by-uuid/a343a3de-0210-4fae-9e8e-68f35e824558 
  mitigations=auto quiet 
  Console: tty 1 dm: SDDM Distro: openSUSE Leap 15.3 
Machine:
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X470-F GAMING v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 5861 date: 08/10/2021 
Memory:
  RAM: total: 31.26 GiB used: 1.99 GiB (6.4%) 
  Array-1: capacity: 128 GiB slots: 4 EC: None max module size: 32 GiB 
  note: est. 
  Device-1: DIMM_A1 size: 8 GiB speed: 3000 MT/s type: DDR4 
  detail: synchronous unbuffered (unregistered) bus width: 64 bits 
  total: 64 bits manufacturer: Corsair part-no: CMK16GX4M2B3000C15 serial: N/A 
  Device-2: DIMM_A2 size: 8 GiB speed: 3000 MT/s type: DDR4 
  detail: synchronous unbuffered (unregistered) bus width: 64 bits 
  total: 64 bits manufacturer: Corsair part-no: CMK16GX4M2B3000C15 serial: N/A 
  Device-3: DIMM_B1 size: 8 GiB speed: 3000 MT/s type: DDR4 
  detail: synchronous unbuffered (unregistered) bus width: 64 bits 
  total: 64 bits manufacturer: Corsair part-no: CMK16GX4M2B3000C15 serial: N/A 
  Device-4: DIMM_B2 size: 8 GiB speed: 3000 MT/s type: DDR4 
  detail: synchronous unbuffered (unregistered) bus width: 64 bits 
  total: 64 bits manufacturer: Corsair part-no: CMK16GX4M2B3000C15 serial: N/A 
CPU:
  Topology: 8-Core model: AMD Ryzen 7 2700X bits: 64 type: MT MCP arch: Zen+ 
  family: 17 (23) model-id: 8 stepping: 2 microcode: 800820D L1 cache: 768 KiB 
  L2 cache: 4096 KiB L3 cache: 16.0 MiB bogomips: 118403 
  Speed: 2120 MHz min/max: 2200/3700 MHz boost: enabled Core speeds (MHz): 
  1: 2196 2: 2219 3: 2196 4: 2199 5: 2111 6: 2108 7: 4136 8: 2109 9: 2200 
  10: 2198 11: 2101 12: 2108 13: 4199 14: 2109 15: 2197 16: 2258 
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1 
  bmi2 bpext clflush clflushopt clzero cmov cmp_legacy constant_tsc cpb cpuid 
  cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasid 
  fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb irperf lahf_lm lbrv lm mca 
  mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl 
  npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb 
  perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse pse36 
  rdrand rdseed rdtscp rep_good sep sev sev_es sha_ni skinit smap smca sme 
  smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 succor svm svm_lock syscall tce 
  topoext tsc tsc_scale v_vmsave_vmload vgif vmcb_clean vme vmmcall wdt 
  xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: 
  disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1080] vendor: ASUSTeK driver: nouveau 
  v: kernel bus ID: 09:00.0 chip ID: 10de:1b80 
  Display: server: X.org 1.20.3 compositor: kwin_x11 driver: nouveau 
  unloaded: fbdev,modesetting,vesa alternate: nv,nvidia tty: 88x29 
  Message: Advanced graphics data unavailable in console for root. 
Audio:
  Device-1: NVIDIA GP104 High Definition Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 09:00.1 chip ID: 10de:10f0 
  Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 0b:00.3 chip ID: 1022:1457 
  Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo 
  bus ID: 5-1:2 chip ID: 046d:0825 serial: <filter> 
  Device-4: Creative Sound BlasterX G6 type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus ID: 5-2:6 chip ID: 041e:3256 
  serial: <filter> 
  Device-5: Kingston HyperX QuadCast type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-3:2 chip ID: 0951:16df 
  serial: <filter> 
  Sound Server: ALSA v: k5.3.18-59.19-default 
Network:
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: 5.6.0-k 
  port: e000 bus ID: 07:00.0 chip ID: 8086:1539 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IP v4: <filter> type: dynamic noprefixroute scope: global 
  broadcast: <filter> 
  IP v6: <filter> type: noprefixroute scope: link 
  WAN IP: <filter> 
Drives:
  Local Storage: total: 3.01 TiB used: 827.07 GiB (26.9%) 
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB 
  block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
  serial: <filter> rev: 2B2QEXE7 temp: 35 C scheme: GPT 
  SMART: yes health: PASSED on: 107d 8h cycles: 214 
  read-units: 18,159,700 [9.29 TB] written-units: 22,010,771 [11.2 TB] 
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB 
  block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 
  serial: <filter> rev: 2B2QEXE7 temp: 32 C scheme: GPT 
  SMART: yes health: PASSED on: 30d 20h cycles: 214 
  read-units: 19,380,318 [9.92 TB] written-units: 28,220,289 [14.4 TB] 
  ID-3: /dev/sda vendor: Western Digital model: WD20PURZ-85GU6Y0 
  size: 1.82 TiB block size: physical: 4096 B logical: 512 B sata: 3.0 
  speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: 0A80 temp: 26 C 
  scheme: MBR 
  SMART: yes state: enabled health: PASSED on: 1y 54d 6h cycles: 762 
  ID-4: /dev/sdb type: USB vendor: Samsung model: Flash Drive FIT 
  size: 59.75 GiB block size: physical: 512 B logical: 512 B serial: <filter> 
  rev: 1100 scheme: MBR 
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
  ID-5: /dev/sdc vendor: Kingston model: SV300S37A240G family: Driven SSDs 
  size: 223.57 GiB block size: physical: 512 B logical: 512 B sata: 3.0 
  speed: 6.0 Gb/s serial: <filter> rev: BBF0 temp: 26 C scheme: MBR 
  SMART: yes state: enabled health: PASSED on: 5y 333d 7h cycles: 624 
  read: 12916 GiB written: 13116 GiB 
  Message: No Optical or Floppy data was found. 
RAID:
  Message: No RAID data was found. 
Partition:
  ID-1: / raw size: 419.04 GiB size: 419.04 GiB (100.00%) 
  used: 5.53 GiB (1.3%) fs: btrfs block size: 4096 B dev: /dev/nvme0n1p6 
  label: N/A uuid: 8bef70f0-1ae6-4423-9936-4d9ce8bd75f4 
  ID-2: /.snapshots raw size: 419.04 GiB size: 419.04 GiB (100.00%) 
  used: 5.53 GiB (1.3%) fs: btrfs block size: 4096 B dev: /dev/nvme0n1p6 
  label: N/A uuid: 8bef70f0-1ae6-4423-9936-4d9ce8bd75f4 
  ID-3: /boot/efi raw size: 100.0 MiB size: 96.0 MiB (96.00%) 
  used: 41.6 MiB (43.3%) fs: vfat block size: 512 B dev: /dev/nvme0n1p2 
  label: N/A uuid: BAA4-DBF7 
  ID-4: /boot/grub2/i386-pc raw size: 419.04 GiB size: 419.04 GiB (100.00%) 
  used: 5.53 GiB (1.3%) fs: btrfs block size: 4096 B dev: /dev/nvme0n1p6 
  label: N/A uuid: 8bef70f0-1ae6-4423-9936-4d9ce8bd75f4 
  ID-5: /boot/grub2/x86_64-efi raw size: 419.04 GiB size: 419.04 GiB (100.00%) 
  used: 5.53 GiB (1.3%) fs: btrfs block size: 4096 B dev: /dev/nvme0n1p6 
  label: N/A uuid: 8bef70f0-1ae6-4423-9936-4d9ce8bd75f4 
  ID-6: /home raw size: 419.04 GiB size: 419.04 GiB (100.00%) 
  used: 5.53 GiB (1.3%) fs: btrfs block size: 4096 B dev: /dev/nvme0n1p6 
  label: N/A uuid: 8bef70f0-1ae6-4423-9936-4d9ce8bd75f4 
  ID-7: /opt raw size: 419.04 GiB size: 419.04 GiB (100.00%) 
  used: 5.53 GiB (1.3%) fs: btrfs block size: 4096 B dev: /dev/nvme0n1p6 
  label: N/A uuid: 8bef70f0-1ae6-4423-9936-4d9ce8bd75f4 
  ID-8: /root raw size: 419.04 GiB size: 419.04 GiB (100.00%) 
  used: 5.53 GiB (1.3%) fs: btrfs block size: 4096 B dev: /dev/nvme0n1p6 
  label: N/A uuid: 8bef70f0-1ae6-4423-9936-4d9ce8bd75f4 
  ID-9: /run/media/rtr/0a3ac3d6-bfa8-42c5-ae7e-205a1a8c1849 
  raw size: 891.96 GiB size: 891.96 GiB (100.00%) used: 325.36 GiB (36.5%) 
  fs: btrfs block size: 4096 B dev: /dev/nvme1n1p3 label: N/A 
  uuid: 0a3ac3d6-bfa8-42c5-ae7e-205a1a8c1849 
  ID-10: /run/media/rtr/C_Win raw size: 511.45 GiB size: 511.45 GiB (100.00%) 
  used: 268.60 GiB (52.5%) fs: ntfs block size: 4096 B dev: /dev/nvme0n1p4 
  label: C_Win uuid: 2CA4A7DDA4A7A7B2 
  ID-11: /run/media/rtr/NO_LABEL raw size: 400.0 MiB size: 399.2 MiB (99.80%) 
  used: 568 KiB (0.1%) fs: vfat block size: 512 B dev: /dev/nvme0n1p5 
  label: NO_LABEL uuid: 0D89-C112 
  ID-12: /run/media/rtr/b57cfbd6-8385-480f-9800-c164cac69c9b 
  raw size: 781.25 GiB size: 767.92 GiB (98.29%) used: 127.93 GiB (16.7%) 
  fs: ext4 block size: 4096 B dev: /dev/sda2 label: N/A 
  uuid: b57cfbd6-8385-480f-9800-c164cac69c9b 
  ID-13: /run/media/rtr/ea787231-6c71-48b2-a0c5-0106614a479c 
  raw size: 223.57 GiB size: 223.57 GiB (100.00%) used: 99.61 GiB (44.6%) 
  fs: btrfs block size: 4096 B dev: /dev/sdc1 label: N/A 
  uuid: ea787231-6c71-48b2-a0c5-0106614a479c 
  ID-14: /srv raw size: 419.04 GiB size: 419.04 GiB (100.00%) 
  used: 5.53 GiB (1.3%) fs: btrfs block size: 4096 B dev: /dev/nvme0n1p6 
  label: N/A uuid: 8bef70f0-1ae6-4423-9936-4d9ce8bd75f4 
  ID-15: /tmp raw size: 419.04 GiB size: 419.04 GiB (100.00%) 
  used: 5.53 GiB (1.3%) fs: btrfs block size: 4096 B dev: /dev/nvme0n1p6 
  label: N/A uuid: 8bef70f0-1ae6-4423-9936-4d9ce8bd75f4 
  ID-16: /usr/local raw size: 419.04 GiB size: 419.04 GiB (100.00%) 
  used: 5.53 GiB (1.3%) fs: btrfs block size: 4096 B dev: /dev/nvme0n1p6 
  label: N/A uuid: 8bef70f0-1ae6-4423-9936-4d9ce8bd75f4 
  ID-17: /var raw size: 419.04 GiB size: 419.04 GiB (100.00%) 
  used: 5.53 GiB (1.3%) fs: btrfs block size: 4096 B dev: /dev/nvme0n1p6 
  label: N/A uuid: 8bef70f0-1ae6-4423-9936-4d9ce8bd75f4 
Swap:
  Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 39.06 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/nvme1n1p1 label: N/A uuid: a343a3de-0210-4fae-9e8e-68f35e824558 
Unmounted:
  ID-1: /dev/nvme0n1p1 size: 529.0 MiB fs: ntfs label: Recovery 
  uuid: 0CD2A280D2A26DA0 
  ID-2: /dev/nvme0n1p3 size: 16.0 MiB fs: N/A label: N/A uuid: N/A 
  ID-3: /dev/nvme1n1p2 size: 500.0 MiB fs: vfat label: M2_2 uuid: 42F8-D26E 
  ID-4: /dev/sda1 size: 1.06 TiB fs: exfat label: N/A uuid: 9973-5D63 
  ID-5: /dev/sdb1 size: 59.72 GiB fs: exfat label: Ventoy uuid: FDA7-58AA 
  ID-6: /dev/sdb2 size: 32.0 MiB fs: vfat label: VTOYEFI uuid: 89CA-465B 
USB:
  Hub: 1-0:1 info: Full speed (or root) Hub ports: 14 rev: 2.0 speed: 480 Mb/s 
  chip ID: 1d6b:0002 
  Device-1: 1-3:2 info: Kingston HyperX QuadCast type: Audio,HID 
  driver: hid-generic,snd-usb-audio,usbhid interfaces: 4 rev: 1.1 
  speed: 12 Mb/s chip ID: 0951:16df serial: <filter> 
  Device-2: 1-5:3 info: Corsair CORSAIR SCIMITAR RGB ELITE Gaming Mouse 
  type: Mouse,HID driver: hid-generic,usbhid interfaces: 2 rev: 2.0 
  speed: 12 Mb/s chip ID: 1b1c:1b8b serial: <filter> 
  Device-3: 1-9:4 info: ASUSTek AURA LED Controller type: HID 
  driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s 
  chip ID: 0b05:1872 serial: <filter> 
  Hub: 2-0:1 info: Full speed (or root) Hub ports: 8 rev: 3.1 speed: 10 Gb/s 
  chip ID: 1d6b:0003 
  Device-4: 2-4:2 info: Silicon Motion - Taiwan (formerly Feiya ) Flash Drive 
  type: Mass Storage driver: usb-storage interfaces: 1 rev: 3.1 speed: 5 Gb/s 
  chip ID: 090c:1000 serial: <filter> 
  Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 speed: 480 Mb/s 
  chip ID: 1d6b:0002 
  Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.1 speed: 10 Gb/s 
  chip ID: 1d6b:0003 
  Hub: 5-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 speed: 480 Mb/s 
  chip ID: 1d6b:0002 
  Device-5: 5-1:2 info: Logitech Webcam C270 type: Video,Audio 
  driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s 
  chip ID: 046d:0825 serial: <filter> 
  Device-6: 5-2:6 info: Creative Sound BlasterX G6 type: Audio,HID 
  driver: hid-generic,snd-usb-audio,usbhid interfaces: 5 rev: 1.1 
  speed: 12 Mb/s chip ID: 041e:3256 serial: <filter> 
  Device-7: 5-3:4 
  info: Corsair CORSAIR K95 RGB PLATINUM XT Mechanical Gaming Keyboard 
  type: Keyboard,HID,Mouse driver: hid-generic,usbhid interfaces: 4 rev: 2.0 
  speed: 12 Mb/s chip ID: 1b1c:1b89 serial: <filter> 
  Device-8: 5-4:5 info: Broadcom BCM20702A0 Bluetooth 4.0 
  type: <vendor specific> driver: btusb interfaces: 4 rev: 2.0 speed: 12 Mb/s 
  chip ID: 0a5c:21e8 serial: <filter> 
  Hub: 6-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 speed: 5 Gb/s 
  chip ID: 1d6b:0003 
Sensors:
  System Temperatures: cpu: 48.2 C mobo: N/A gpu: nouveau temp: 40 C 
  Fan Speeds (RPM): cpu: 0 gpu: nouveau fan: 904 
Info:
  Processes: 367 Uptime: N/A Init: systemd v: 246 runlevel: 5 
  target: graphical.target Compilers: gcc: N/A Shell: bash (sudo) v: 4.4.23 
  running in: tty 1 inxi: 3.1.00

the output to parted --list is:

Model: ATA WDC WD20PURZ-85G (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  1162GB  1162GB  primary               type=07
 2      1162GB  2000GB  839GB   primary  ext4         type=83


Model: Samsung Flash Drive FIT (scsi)
Disk /dev/sdb: 64.2GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  64.1GB  64.1GB  primary               boot, type=07
 2      64.1GB  64.2GB  33.6MB  primary  fat16        esp, type=ef


Model: ATA KINGSTON SV300S3 (scsi)
Disk /dev/sdc: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type     File system  Flags
 1      1049kB  240GB  240GB  primary  btrfs        type=83


Model: NVMe Device (nvme)
Disk /dev/nvme0n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                          Flags
 1      1049kB  556MB   555MB   ntfs         Basic data partition          hidden, diag
 2      556MB   661MB   105MB   fat32        EFI system partition          boot, esp
 3      661MB   677MB   16.8MB               Microsoft reserved partition  msftres
 4      677MB   550GB   549GB   ntfs         Basic data partition          msftdata
 5      550GB   550GB   419MB   fat32                                      legacy_boot, msftdata
 6      550GB   1000GB  450GB   btrfs


Model: NVMe Device (nvme)
Disk /dev/nvme1n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name  Flags
 1      17.4kB  41.9GB  41.9GB  linux-swap(v1)        swap
 2      41.9GB  42.5GB  524MB   fat32                 boot, legacy_boot, esp
 3      42.5GB  1000GB  958GB   btrfs

The output to lsblk is:

AME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    0   1.8T  0 disk 
ā”œā”€sda1        8:1    0   1.1T  0 part 
ā””ā”€sda2        8:2    0 781.3G  0 part /run/media/rtr/b57cfbd6-8385-480f-9800-c164cac69c9
sdb           8:16   1  59.8G  0 disk 
ā”œā”€sdb1        8:17   1  59.7G  0 part 
ā””ā”€sdb2        8:18   1    32M  0 part 
sdc           8:32   0 223.6G  0 disk 
ā””ā”€sdc1        8:33   0 223.6G  0 part /run/media/rtr/ea787231-6c71-48b2-a0c5-0106614a479
nvme0n1     259:0    0 931.5G  0 disk 
ā”œā”€nvme0n1p1 259:2    0   529M  0 part 
ā”œā”€nvme0n1p2 259:3    0   100M  0 part /boot/efi
ā”œā”€nvme0n1p3 259:4    0    16M  0 part 
ā”œā”€nvme0n1p4 259:5    0 511.5G  0 part /run/media/rtr/C_Win
ā”œā”€nvme0n1p5 259:6    0   400M  0 part /run/media/rtr/NO_LABEL
ā””ā”€nvme0n1p6 259:7    0   419G  0 part /
nvme1n1     259:1    0 931.5G  0 disk 
ā”œā”€nvme1n1p1 259:8    0  39.1G  0 part [SWAP]
ā”œā”€nvme1n1p2 259:9    0   500M  0 part 
ā””ā”€nvme1n1p3 259:10   0   892G  0 part /run/media/rtr/0a3ac3d6-bfa8-42c5-ae7e-205a1a8c184
2

When you are on the Refind boot screen, press Insert, F2 or Tab while your Manjaro entry is highlighted and you can choose which kernel you would like to boot. I hid everything (press delete key only hides these items) except Win10 and Manjaro on mine and uninstalled Grub so Refind is the only boot manager present.

3

I just rebooted and tried that F2 on each of the 4 options for refind. The first 3 entries (Windows, EFI/Manjaro and Boot Fallback) all have the same two options, ā€œBoot using default optionsā€ and ā€œReturn to main menuā€. The last entry in refind has ā€œBoot with normal optionsā€ and ā€œBoot into single user modeā€. Iā€™m not sure why the last entry, the one with my old Manjaro install, has different wording.

I think maybe installing the second copy of Manjaro confused refind and now I have grub running as a second boot loader inside of refind. So when I update my system, pamac installs the kernel into /boot, doesnā€™t know which boot loader to update and decides not to update either one.

Iā€™m not sure if this is a further clue, but while the /boot/efi directory on the new Manjaro install has directories in it, the /boot/efi on the old Manjaro install is empty.

I was considering uninstalling grub and using refind-install to have it rebuild entries, but I donā€™t want to break things so that I canā€™t boot at all.

4

If it helps, hereā€™s the output from mhwd-kernel -i linux513:

[onyx ~]# mhwd-kernel -i linux513
:: Synchronizing package databases...
 core                                      169.6 KiB   796 KiB/s 00:00 [#######################################] 100%
 extra                                    1892.8 KiB  13.2 MiB/s 00:00 [#######################################] 100%
 community                                   6.6 MiB  38.1 MiB/s 00:00 [#######################################] 100%
 multilib                                  174.6 KiB  4.61 MiB/s 00:00 [#######################################] 100%
warning: linux513-5.13.13-1 is up to date -- reinstalling
warning: linux513-nvidia-470.63.01-5 is up to date -- reinstalling
warning: linux513-virtualbox-host-modules-6.1.26-8 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (3) linux513-5.13.13-1  linux513-nvidia-470.63.01-5  linux513-virtualbox-host-modules-6.1.26-8

Total Installed Size:  140.92 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] y
(3/3) checking keys in keyring                                         [#######################################] 100%
(3/3) checking package integrity                                       [#######################################] 100%
(3/3) loading package files                                            [#######################################] 100%
(3/3) checking for file conflicts                                      [#######################################] 100%
(3/3) checking available disk space                                    [#######################################] 100%
:: Running pre-transaction hooks...
(1/2) Remove upgraded DKMS modules
==> Unable to remove module vboxhost/6.1.26_OSE for kernel 5.13.13-1-MANJARO: Not found in dkms status output.
==> Unable to remove module v4l2loopback/0.12.5 for kernel 5.13.13-1-MANJARO: Not found in dkms status output.
(2/2) Save Linux kernel modules
:: Processing package changes...
(1/3) reinstalling linux513                                            [#######################################] 100%
(2/3) reinstalling linux513-nvidia                                     [#######################################] 100%
(3/3) reinstalling linux513-virtualbox-host-modules                    [#######################################] 100%
In order to use the new version, reload all virtualbox modules manually.
:: Running post-transaction hooks...
(1/8) Arming ConditionNeedsUpdate...
(2/8) Updating module dependencies...
(3/8) Install DKMS modules
==> Unable to install module vboxhost/6.1.26_OSE for kernel 5.13.13-1-MANJARO: Missing kernel headers.
==> Unable to install module v4l2loopback/0.12.5 for kernel 5.13.13-1-MANJARO: Missing kernel headers.
(4/8) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux513.preset: 'default'
  -> -k /boot/vmlinuz-5.13-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.13-x86_64.img
==> Starting build: 5.13.13-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.13-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux513.preset: 'fallback'
  -> -k /boot/vmlinuz-5.13-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.13-x86_64-fallback.img -S autodetect
==> Starting build: 5.13.13-1-MANJARO
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.13-x86_64-fallback.img
==> Image generation successful
(5/8) Updating Kernel initcpios for Nvidia-DRM...
(6/8) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.13-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.13-x86_64.img
Found initrd fallback image: /boot/initramfs-5.13-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-rt-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.10-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-rt-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/nvme0n1p2@/efi/Microsoft/Boot/bootmgfw.efi
Found Manjaro Linux (21.1.0) on /dev/nvme0n1p5
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme1n1.
done
(7/8) Restore Linux kernel modules

==> Warning:
         -> Kernel has been updated. Modules of the current kernel
         -> have been backed up so you can continue to use your
         -> computer. However, the new kernel will only work 
         -> at next boot.


(8/8) Keep rEFInd default kernel
5

I notice two things from the kernel install scroll, first it looks like it calls on grub to update its configuration file instead of refind and then the above message. grub-probe is not able to see the btrfs partition to update?

6

:+1: Welcome to Manjaro! :+1:

  1. Please read this:
    How to provide good information
    and press the three dots ā€¦ below your post and press the :pencil2: to give us more information so we can see whatā€™s really going on.
    Now we know the symptom of the disease, but we need some more probing to know where the origin liesā€¦ :grin:

  2. An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information for us to be able to help you. (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
    Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.

  3. The output of:

    parted --list
lsblk

    executed as root would be helpful as well after booting from grub.

:+1:

P.S. If you want to notify me that you did provide this information, please :heart: this message and Iā€™ll come back and have another look.

1 Like
7

  1. In the future, when providing code/output, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text so that the output looks like this:

    Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

    instead of like this:

    Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.`

    (as that makes both our lives much easier)

  2. No need to do anything right now as Iā€™m a moderator here on this site and have fixed it for you already. However, in the future I might not see your post so review my RAW edits by pushing the orange pencil in the upper right corner of the post I just fixed. :wink:

  3. Did you boot with an OpenSuse Live USB stick? Why???

  4. Did you install something in CSM / BIOS mode?

  5. That looks like 2 ESPs on one disk, and that is not allowed by the UEFI specs

  6. OK, Iā€™ll stop here because thatā€™s one sick puppy and it looks like youā€™re in for a full backup of all your data and a reinstall

:+1:

8

Thank you, @Fabby! I included the inxi, parted and lsblk in the OP. I suppose I was trying to keep it simple with my original post and didnā€™t want to confuse things with too much information, but this audience probably is more able to parse the information better than the average forum contributor :slight_smile:

My circumstances have changedā€¦ In a forceful attempt to get the system to stop using the /boot from the first Manjaro install on nvme0, I deleted the partition. This didnā€™t help and resulted in all of the refind menu entries not working, except for the Windows 10 entry, which still works fine.

I fumbled around with some refind instructions on the Arch Wiki, booting with a USB stick, mounting the second Manjaro root and boot file systems on btrfs and using manjaro-chroot to get refind to update from within that chroot. It said it saw the boot partition and updated the refind menu entries, but it didnā€™t actualy change anything.

My next attempt was to re-install Manjaro to the partition that I deleted, with btrfs support and pointing to the /boot/efi partition on the second nvme1. I had hoped that the installer would see the Manjaro installation from that and create a boot entry on refind, but it didnā€™t. I tried the same thing with SuSE, hoping their installer would handle it differently, but it also failed to recognize the installation.

9
  1. Please read this:
  1. Take a data backup
  2. Wipe that thing and reinstall Windows first and Manjaro next with your new-found wisdom.

:sob:

P.S. Sorry: trying to untangle all that and recovering it one by one is going to take days through a forum and would probably take me 4 hours if I could sit behind your machineā€¦

10

I tried SuSE because it was the newest iso on my ventoy USB stick. The Manjaro iso I have on there from July 2021, and while thatā€™s not ā€œoldā€, it asks for 460 pkg updates on boot (I know, rolling distro).

You caught something I didnā€™t see, the legacy boot partition on nvme1. While Iā€™ve installed multiple OSā€™s and dual boot systems off and on for decades, when it was a simple fdisk/mbr design, but I do not have much experience with efi. Itā€™s one of those things I mess with for a couple hours every few years and then leave alone for long long periods at a time, and Iā€™m old so I forget what I knew 3 years ago :slight_smile: But 2 boot partitions on one drive definitely sounds out of spec.

I do have backups on my NAS and I wanted to reinstall Windows at some point anyway. The data is all there for the Manjaro install that I want to use and Iā€™m pretty sure Iā€™m less than a dozen steps away from getting it working, but the order and nature of those steps are quite important.

I was considering unplugging all the drives except for the one I want to keep, booting from manjaro on the ventoy stick, installing the refind package and doing a refind-install so the only drive it can update is the one with my Manjaro install.

What I donā€™t know is if I should delete one of the espā€™s, or both, or maybe do something in my bios to untangle efi? I have an ASUS Strix RoG x470 gaming-f motherboard.

11

I just updated the N00b guide with tons of BIOS / UEFI information and itā€™s being verified by our resident UEFI expert as we speak. R E A D Ā  I T ! :stuck_out_tongue_winking_eye:

I forgot what I was talking about 3 minutes agoā€¦ Look! :dog2: Huh? What were you saying? :grin:

yeahā€¦

Definitely

That, my friend, is BIOS thinking and will get you into trouble. Read the N00b guide! :stuck_out_tongue_winking_eye:

This is what you should be doing:

image

(With your new-found wisdom after youā€™ve read all of the N00b guide; take it from another old fart :older_adult: )

:grin:

12

Solved!

I learned that the second legacy boot partition on nvme1 was created by SuSE, so I removed that and the temp SuSE partition.

After a few hours of poking around, rebooting and a couple dozen web searches, I was about to try booting into Windows, hoping it would ā€œfixā€ my dual boot by making itself the only OS visible as they love do to me after almost every patch Tuesday update.

I went into my BIOS and made Windows on nvme0 the default boot drive, rebooted and saw many new entries in refind, including an entry for the btrfs Manjaro that I use every day, but it was pointing to the 5.13 kernel as well. I did not expect it to work when I selected it, but it booted right up! Iā€™m going to guess that this is the ESP pacman was updating all along, maybe?

Iā€™m pretty sure this will not be the end of my issues until I reformat and start from scratch, but at least I can mark this issue as resolved on the forum.

13

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.