System unresponsive after removing some kernels

newbietolinux · 29 June 2025 17:48

Hi all

Today my system was unusually slow/hanging. I noticed there were 5 kernels installed and thought that may be causing lag, so in the GUI I removed 3 kernels and installed a newer one after that.

When I rebooted the PC, my whole system was unresponsive, meaning after the monitor logo there is nothing on the screen and it just remains like that indefinitely.

I don’t know what kind of mess I’ve made. How can I fix this? I was wondering maybe a chroot -a Timeshift to restore my system. I am hoping I don’t need to do a full reinstall of Manjaro.

I am writing to this forum on a LiveUSB.

Updated: System can’t find GRUB drive:

manjaro@manjaro ~]$ manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
==> Mounting (ManjaroLinux) [/dev/nvme0n1p2]
 --> mount: [/mnt]
 --> mount: [/mnt/boot/efi]
[manjaro /]#

Can someone please advise?

beermad · 29 June 2025 18:08

Perhaps a silly question, but you did run update-grub afterwards, didn’t you?

Nachlese · 29 June 2025 18:08

When you did install a kernel, how did you do that?

Not so important now - in chroot, install one again:

see what is available:

mhwd-kernel -l

choose one and install it:

pacman -Syu linuxXYZ

mkinitcpio -P
to create the initrd

then:

grub-mkconfig -o /boot/grub/grub.cfg

or:
update-grub

That should be it if there is no NVIDIA graphics involved - in that case I’m clueless as to what to do.

andreas85 · 29 June 2025 18:09

No

Only one of the installed kernels is in use at a time. You can see which one with:
uname -a

Then i would suggest using kernel 6.12 (LTS)

After installing a kernel you need to restart to actually use it.

newbietolinux · 29 June 2025 18:11

Hi beermad

I did it through the GUI. I thought I could just restart my PC without update-grub.

newbietolinux · 29 June 2025 18:12

Hi Nachlese

Great, going to follow your instructions now.

newbietolinux · 29 June 2025 18:17

Thank you andreas85. I will select 6.12 LTS.

Thank you Nachlese, following these instructions.

newbietolinux · 29 June 2025 18:35

Hi Nachlese

There might have been an error in installing Linux612 but maybe it was resolved:

[manjaro /]# pacman -Syu linux612
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
warning: linux612-6.12.34-1 is up to date -- reinstalling
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (1) linux612-6.12.34-1

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

:: Proceed with installation? [Y/n] y
(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 linux612                        [######################] 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/linux612.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.12-x86_64 -g /boot/initramfs-6.12-x86_64.img
==> Starting build: '6.12.34-1-MANJARO'
  -> Running build hook: [systemd]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [sd-vconsole]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.12-x86_64.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux612.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-6.12-x86_64 -g /boot/initramfs-6.12-x86_64-fallback.img -S autodetect
==> Starting build: '6.12.34-1-MANJARO'
  -> Running build hook: [systemd]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci_renesas'
  -> Running build hook: [sd-vconsole]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> WARNING: Possibly missing '/bin/sh' for script: /usr/bin/fsck.btrfs
==> WARNING: Possibly missing '/bin/sh' for script: /usr/bin/fsck.xfs
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.12-x86_64-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
(4/5) Updating Kernel initcpios for Nvidia-DRM...
(5/5) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.13-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.13-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.13-rt-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.12-x86_64.img
Found initrd fallback image: /boot/initramfs-6.12-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.12-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.12-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.12-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.
ERROR: mkdir /var/lock/dmraid
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
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
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
[manjaro /]#

newbietolinux · 29 June 2025 18:55

Hi Nachlese

I have run all the commands in order.

Running update-grubalso gave the error of not finding GRUB drive at the end. Could you please tell me if this output is all good before i leave the liveUSB environment? Thank you so much.

update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.13-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.13-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.13-rt-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.12-x86_64.img
Found initrd fallback image: /boot/initramfs-6.12-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.12-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.12-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.12-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.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
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
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
[manjaro /]#

megavolt · 29 June 2025 18:57

newbietolinux:

Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.13-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.13-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.13-rt-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.12-x86_64.img
Found initrd fallback image: /boot/initramfs-6.12-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.12-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.12-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-6.12-rt-x86_64-fallback.img

That is important. Ignore the probe error.

This kernel is EOL. Remove it.

newbietolinux · 29 June 2025 18:58

Thank you megavolt.

newbietolinux · 29 June 2025 19:01

Would I say pacman -R linux613?

megavolt · 29 June 2025 19:03

I would do:

mhwd-kernel -r linux613-rt

In general, it uses also pacman, but does additional stuff. It is a helper script.

newbietolinux · 29 June 2025 19:04

Thank you.

newbietolinux · 29 June 2025 19:06


[manjaro /]# mhwd-kernel -r linux613
Error: Kernel not installed.
Currently running: 6.1.30-1-MANJARO (linux61)
The following kernels are installed in your system:
   * linux612
   * linux612-rt
   * linux613-rt
[manjaro /]#

megavolt · 29 June 2025 19:08

You see what to do?

newbietolinux · 29 June 2025 19:09

ah okay

newbietolinux · 29 June 2025 19:29

Thank you so much Nachlese, beermad, andreas85 and megavolt.

system · 2 July 2025 19:29

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