Error in update, many kernels missing

Hi all. I just had an error in my Manjaro update… I’m sorry I did not catch the error message, but I’m guessing the update didn’t complete properly because many of my kernels are missing.

Grub.cfg has:

- 5.4
- 5.15
- 6.1-rt
- 6.1
- 6.6-rt
- 6.6
- 6.7-rt
- 6.9-rt
- 6.10-rt
- 6.11-rt
- 6.11

But the latest that I can boot with is 6.6 now.

Output of mhwd-kernel -l:

Available kernels:
   * linux419
   * linux510
   * linux515
   * linux54
   * linux61
   * linux611
   * linux612
   * linux613
   * linux66
   * linux61-rt
   * linux611-rt
   * linux66-rt

Output of mhwd-kernel -li:

The following kernels are installed in your system:
   * linux515
   * linux54
   * linux61
   * linux611
   * linux66
   * linux61-rt
   * linux610-rt
   * linux611-rt
   * linux66-rt
   * linux67-rt
   * linux69-rt

When I try pacman -R linux611-rt I get the following:

checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing linux611-rt breaks dependency 'linux611-rt' required by linux611-rt-virtualbox-host-modules

Any idea how I can get out of this? Thanks.

remove the blocking dependency as well - it is specific to that kernel and you don’t want it anyway
remove the virtualbox host modules in that case

you could try:
sudo pacman -Rns linux611-rt
but do carefully review the list of packages that is proposed as going to be removed
before you answer “yes” to proceed

Why not use the tool that you used to install the kernels?:
mhwd-kernel
it does have a remove option …

Thank you. Is this error a problem?


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 Manjaro Linux (24.0.3) on /dev/sda5
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
done

it’s not a complete output
seems to be a partial from
update-grub

I could be wrong though.

and:
there is no error anywhere :man_shrugging:
but also no kernel that I can see …

OK I’ll ignore the “if you think this is an error” then.

Now I have installed linux611-rt but it is not added to grub. Do I need to do it manually?

Are you sure you need eleven (11) kernels?
You can only use one at a time … :slightly_smiling_face:

Are you sure you need any -rt kernel at all?
If you are unsure then you don’t.

There is no indication in what you posted that you did what you say you did. :man_shrugging:
Or it wasn’t successful - I see no mention of a kernel in the last output you posted.

I didn’t ask for any specific kernel, I just let Manjaro install what it wanted to install. Am I supposed to manually clean up old kernels? I did think the -rt was kind of strange but I don’t remember specifying.

I will install plain linux611 and post the entire output.

[cutie ~]# pacman -Rns linux611-rt
checking dependencies...
:: base optionally requires linux: bare metal support

Packages (1) linux611-rt-6.11_rt7-3

Total Removed Size:  144.38 MiB

:: Do you want to remove these packages? [Y/n] 
:: Running pre-transaction hooks...
(1/1) Removing linux initcpios...
:: Processing package changes...
(1/1) removing linux611-rt                                                          [################################################] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Refreshing PackageKit...
(4/4) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.11-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.11-x86_64.img
Found initrd fallback image: /boot/initramfs-6.11-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.9-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.9-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.9-rt-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.7-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.7-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.7-rt-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.6-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.6-x86_64.img
Found initrd fallback image: /boot/initramfs-6.6-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.6-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.6-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.6-rt-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.1-x86_64.img
Found initrd fallback image: /boot/initramfs-6.1-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.1-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.1-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.1-rt-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-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 Manjaro Linux (24.0.3) on /dev/sda5
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
done
[cutie ~]# pacman -Syu linux611
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
 sublime-text is up to date
warning: linux611-6.11.10-2 is up to date -- reinstalling
:: Starting full system upgrade...
warning: plymouth: local (24.004.60-7) is newer than extra (22.02.122-18)
resolving dependencies...
looking for conflicting packages...

Packages (1) linux611-6.11.10-2

Total Installed Size:  143.92 MiB
Net Upgrade Size:        0.00 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) Creating Timeshift snapshot before upgrade...
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
:: Processing package changes...
(1/1) reinstalling linux611                                                         [################################################] 100%
:: Running post-transaction hooks...
(1/5) Arming ConditionNeedsUpdate...
(2/5) Updating module dependencies...
(3/5) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux611.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.11-x86_64 -g /boot/initramfs-6.11-x86_64.img
==> Starting build: '6.11.10-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [kms]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [resume]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.11-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux611.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.11-x86_64 -g /boot/initramfs-6.11-x86_64-fallback.img -S autodetect
==> Starting build: '6.11.10-2-MANJARO'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [plymouth]
  -> Running build hook: [filesystems]
  -> Running build hook: [resume]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.11-x86_64-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
(4/5) Refreshing PackageKit...
(5/5) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.11-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.11-x86_64.img
Found initrd fallback image: /boot/initramfs-6.11-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.9-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.9-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.9-rt-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.7-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.7-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.7-rt-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.6-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.6-x86_64.img
Found initrd fallback image: /boot/initramfs-6.6-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.6-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.6-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.6-rt-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.1-x86_64.img
Found initrd fallback image: /boot/initramfs-6.1-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.1-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.1-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.1-rt-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-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 Manjaro Linux (24.0.3) on /dev/sda5
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
done

I will reboot and see how it goes and report back. Thanks.

It all worked.

For your own sanity’s sake:
remove all the -rt kernels
keep only two or three of the latest normal kernels with at least one being LTS
use
mhwd-kernel -li
to show you what you have left, what you can get rid of

no one needs 5 or 11 kernels

2 Likes

So when you say to remove kernels, do you mean to remove the image files and change grub.cfg manually?

Also, I still don’t have kernel 6.11 in grub. The latest one that is showing in the menu is 6.10-rc-4.

No. Not manually.
Use either mhwd-kernel or pacman to do that.

That is not what that looks like to me:

it should be there.

update-grub puts it there

not urgent:
you should get rid of packagekit as well

1 Like

Ok I figured out what is causing that. I have a Manjaro partition on sda5 and on sdb1. I am running the Manjaro on sdb1 and thus it updates grub on sdb1, but I am booting with the grub on sda5 which has a selection for ‘Manjaro on /dev/sdb1’.

When I boot directly to sdb I get a ‘Filesystem does not exist’ error.

For now I don’t mind just booting to sdb. Do you know how to fix the filesystem error?

1 Like

Me and very likely no one else has any idea about your hardware or, more importantly, your disk layout
and where you put what.

inxi -zv8
could help

1 Like

Yes I know that’s my bad. I messed up my config.


System:
  Kernel: 6.6.63-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=1b7d6df2-a557-49b2-91dd-36e22d771306 rw quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A info: frameworks v: 6.8.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: Dell product: OptiPlex 3020 v: 00
    serial: <superuser required> Chassis: type: 6 serial: <superuser required>
  Mobo: Dell model: 040DDP v: A01 serial: <superuser required> part-nu: 0612
    uuid: <superuser required> BIOS: Dell v: A20 date: 05/27/2019
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter>
    charge: 55% (should be ignored) rechargeable: yes status: discharging
Memory:
  System RAM: total: 16 GiB available: 15.57 GiB used: 5.15 GiB (33.0%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 16 GiB slots: 2 modules: 2 EC: None
    max-module-size: 8 GiB note: est.
  Device-1: DIMM1 type: DDR3 detail: synchronous size: 8 GiB
    speed: 1600 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: 0000 part-no: 1600DDAD3 serial: <filter>
  Device-2: DIMM2 type: DDR3 detail: synchronous size: 8 GiB
    speed: 1600 MT/s volts: N/A width (bits): data: 64 total: 64
    manufacturer: 0000 part-no: 1600DDAD3 serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i7-4770 bits: 64 type: MT MCP arch: Haswell
    gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
    family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
    smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
    desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 3822 min/max: 800/3900 scaling: driver: intel_cpufreq
    governor: schedutil cores: 1: 3822 2: 3822 3: 3822 4: 3822 5: 3822 6: 3822
    7: 3822 8: 3822 bogomips: 54296
  Flags: abm acpi aes aperfmperf apic arat arch_perfmon avx avx2 bmi1 bmi2
    bts clflush cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht ibpb ibrs ida invpcid lahf_lm lm mca mce md_clear mmx
    monitor movbe msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq
    pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdtscp
    rep_good sdbg sep smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp
    syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi
    vpid x2apic xsave xsaveopt xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Lexa PRO [Radeon
    540/540X/550/550X / RX 540X/550/550X] driver: amdgpu v: kernel arch: GCN-4
    code: Arctic Islands process: GF 14nm built: 2016-20 pcie: gen: 2
    speed: 5 GT/s lanes: 8 link-max: gen: 3 speed: 8 GT/s ports:
    active: DVI-D-1 empty: HDMI-A-1 bus-ID: 01:00.0 chip-ID: 1002:699f
    class-ID: 0300 temp: 51.0 C
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93") monitors: <missing: xrandr>
  Monitor-1: DVI-D-1 model: Samsung LS24C33xG serial: <filter> built: 2024
    res: 1920x1080 dpi: 93 gamma: 1.2 chroma: red: x: 0.655 y: 0.322 green:
    x: 0.298 y: 0.635 blue: x: 0.153 y: 0.039 white: x: 0.314 y: 0.329
    size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9
    modes: 1920x1080, 1680x1050, 1600x900, 1280x1024, 1440x900, 1280x800,
    1280x720, 1024x768, 800x600, 720x576, 720x480, 640x480, 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.7-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 550 / 550 Series
    (radeonsi polaris12 LLVM 18.1.8 DRM 3.54 6.6.63-1-MANJARO)
    device-ID: 1002:699f memory: 3.91 GiB unified: no
  API: Vulkan v: 1.3.295 layers: N/A device: 0 type: discrete-gpu name: AMD
    Radeon RX 550 / 550 Series (RADV POLARIS12) driver: mesa radv
    v: 24.2.7-arch1.1 device-ID: 1002:699f surfaces: xcb,xlib
Audio:
  Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: Dell
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8c20
    class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] Baffin HDMI/DP Audio [Radeon
    RX 550 640SP / 560/560X] driver: snd_hda_intel v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 8 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1
    chip-ID: 1002:aae0 class-ID: 0403
  API: ALSA v: k6.6.63-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Dell driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 04:00.0
    chip-ID: 8086:2725 class-ID: 0280
  IF: wlp4s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: br-0bda3f76b157 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-3: virbr0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  Info: services: NetworkManager, sshd, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 1.4 TiB used: 388.49 GiB (27.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Kingfast model: N/A size: 953.87 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
    serial: <filter> fw-rev: 1B0 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Silicon Power
    model: SPCC Solid State Disk size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 3.0 Gb/s tech: SSD serial: <filter> fw-rev: 9105
    scheme: MBR
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 476.93 GiB size: 468.38 GiB (98.21%)
    used: 388.49 GiB (82.9%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 label: N/A
    uuid: 1b7d6df2-a557-49b2-91dd-36e22d771306
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 8 GiB used: 0 KiB (0.0%) priority: -3
    file: /swapfile
  ID-2: swap-2 type: file size: 8 GiB used: 889.5 MiB (10.9%) priority: -2
    file: /swapfile2
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 100 MiB fs: vfat label: SYSTEM
    uuid: 9443-38B8
  ID-2: /dev/sda2 maj-min: 8:2 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-3: /dev/sda3 maj-min: 8:3 size: 923.58 GiB fs: ntfs label: Windows
    uuid: DEF24449F24427DB
  ID-4: /dev/sda4 maj-min: 8:4 size: 900 MiB fs: ntfs label: Recovery
    uuid: C0A24470A2446CCA
  ID-5: /dev/sda5 maj-min: 8:5 size: 29.3 GiB fs: ext4 label: N/A
    uuid: cd6400db-a31f-4956-971d-1192db54a409
USB:
  Hub-1: 1-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:8008
    class-ID: 0900
  Hub-3: 2-0:1 info: full speed or root hub ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:8000
    class-ID: 0900
  Hub-5: 3-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-6: 3-6:2 info: Hitachi ports: 4 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 chip-ID: 045b:0209 class-ID: 0900
  Device-1: 3-6.1:3 info: Logitech Unifying Receiver
    type: keyboard,mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c52b class-ID: 0300
  Device-2: 3-6.2:4 info: Logitech Nano Receiver type: keyboard,mouse
    driver: logitech-djreceiver,usbhid interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 98mA
    chip-ID: 046d:c534 class-ID: 0301
  Hub-7: 4-0:1 info: super-speed hub ports: 2 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 39.0 C mobo: N/A gpu: amdgpu temp: 53.0 C
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1877 libs: 428 tools: pamac,trizen pm: flatpak
    pkgs: 0
  Active pacman repo servers in: /etc/pacman.conf
    1: https://download.sublimetext.com/arch/stable/x86_64
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    2: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    3: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
    4: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    5: https://mirror.nyist.edu.cn/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 292
  1: cpu: 21.9% command: thunderbird pid: 1562 mem: 565.8 MiB (3.5%)
  2: cpu: 16.6% command: java pid: 1567 mem: 1683.1 MiB (10.5%)
  3: cpu: 6.8% command: baloo_file_extractor pid: 3311 mem: 43.1 MiB (0.2%)
  4: cpu: 6.2% command: firefox pid: 1618 mem: 417.9 MiB (2.6%)
  5: cpu: 4.8% command: firefox pid: 2629 mem: 252.4 MiB (1.5%)
  Memory top: 5 of 292
  1: mem: 1683.1 MiB (10.5%) command: java pid: 1567 cpu: 16.6%
  2: mem: 565.8 MiB (3.5%) command: thunderbird pid: 1562 cpu: 21.9%
  3: mem: 417.9 MiB (2.6%) command: firefox pid: 1618 cpu: 6.2%
  4: mem: 396.2 MiB (2.4%) command: plasmashell pid: 1179 cpu: 1.4%
  5: mem: 313.8 MiB (1.9%) command: vivaldi-bin pid: 1572 cpu: 0.8%
Info:
  Processes: 292 Power: uptime: 8m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.21 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
    tool: systemctl
  Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Bash v: 5.2.37
    running-in: konsole inxi: 3.3.36

I think I just need to restore the MBR on sdb.

This might help:

[cutie ~]$ lsblk -o PATH,PTTYPE,PARTTYPE,FSTYPE,PARTTYPENAME 
PATH      PTTYPE PARTTYPE                             FSTYPE PARTTYPENAME
/dev/sda  gpt                                                
/dev/sda1 gpt    c12a7328-f81f-11d2-ba4b-00a0c93ec93b vfat   EFI System
/dev/sda2 gpt    e3c9e316-0b5c-4db8-817d-f92df00215ae        Microsoft reserved
/dev/sda3 gpt    ebd0a0a2-b9e5-4433-87c0-68b6b72699c7 ntfs   Microsoft basic data
/dev/sda4 gpt    de94bba4-06d1-4d40-a16a-bfd50179d6ac ntfs   Windows recovery environment
/dev/sda5 gpt    c12a7328-f81f-11d2-ba4b-00a0c93ec93b ext4   EFI System
/dev/sdb  dos                                                
/dev/sdb1 dos    0x83                                 ext4   Linux

Apparently sda is EFI and sdb is not.

So would something like this work?

grub-install --force --target=i386-pc --recheck --boot-directory=/boot /dev/sdb

Be careful.

a) I see in your inxi output /dev/sdb1 as your / partition.

b) /dev/sda5 also contains a Manjaro partition, most likely.

First you need to determine how you installed your system: BIOS or UEFI mode. /dev/sda (gpt parted disk) contains your Windoof already. So you could use the ESP of Windoof on /dev/sda to carry thr grub instance to boot /dev/sda5. Or, you install grub on /dev/sdb (MBR parted disk) to boot into /dev/sdb1 but then you won’t be able to dual boot from grub menu.

Ok thanks for this, really.

The story is that I bought a system with a windows 10 disk (sda). I installed a separate sdb and installed Manjaro on that natively. Later I wanted to do some troubleshooting, so I shrunk the windows 10 partition on sda and installed manjaro on the free space (sda5). In the course of doing all that, apparently the boot block on sdb got messed up so right now I must boot with the grub in sda5.

I don’t really care about retaining dual boot for now. As long as I can directly boot Manjaro on sdb it will be fine. I just don’t want to mess up sda if I need to go back to it by changing bios options.

Although now I notice sda is kind of messed up because there is no option for windows any more. I’m guessing this happened because I wasn’t in secure boot mode when I installed manjaro on sda5. I may need to secure boot and reinstall manjaro or do the windows boot block fix to boot to windows again. But again, right now I don’t want to bother you guys with that and I just want a working sdb.

I don’t think so. You most likely just switched from legacy boot (into /dev/sdb1) to UEFI boot to boot /dev/sda5 via the existing ESP of Windoof.