Yesterday when I pressed shutdown, my laptop was frozen in the logo of manjaro when you shutdown the system. After 10 minutes I holded the reset button and I try to see if everything was ok but I didn’t have luck
In the first moment I received this message:
error: file `/boot/vmlinuz-6.6-x86_64’ not found.
error: you need to load the kernel first.
I came to the forum and google to try to see old post but I couldn’t.
I tried with a LiveUSB but I couldn’t.
In this moment, the error message that I wrote before is not appearing. Now when I’m init my laptop is not finding the grub and open my BIOS SETTINGS automatically. If I quit there and I try again, the same. The grub and the message are not appearing right now.
Could you help me, please?
Now I’m not in my laptop but when I have access again to my home, I will reply and If you tell me here what information / commands I need to write to give information, I appreaciate and I will post everything.
You can also chroot and try to reinstall the kernel, or install 6.1
pacman -Syu linux61
In the future, disable the preference in Add/Remove programs to update on shutdown. It is one of the worst ideas ever, i have no explanation how the developer came with that idea at all…your case is an illustration why.
It’s because most of today’s developers in the GNU/Linux ecosystem grew up on — and had their conception of computer science poisoned by — Microsoft Windows, which insists on conducting its update process on shutdown.
Thanks for trying to help @Teo. I’m trying to do a lot of things but I’m a little bit lost.
This is my information:
manjaro /]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 140.2M 1 loop
loop1 7:1 0 971.5M 1 loop
loop2 7:2 0 1.3G 1 loop
loop3 7:3 0 791.9M 1 loop
sda 8:0 1 28.6G 0 disk
|-sda1 8:1 1 3.3G 0 part
`-sda2 8:2 1 4M 0 part
nvme0n1 259:0 0 1.9T 0 disk
|-nvme0n1p1 259:1 0 301M 0 part /boot/efi
|-nvme0n1p2 259:2 0 120G 0 part /
|-nvme0n1p3 259:3 0 8G 0 part
`-nvme0n1p4 259:4 0 1.3T 0 part /home
I tried to do pacman-mirrors -f 5 && pacman -Syyu and then update-grub but I had more errors:
[manjaro /]# pacman-mirrors -f 5 && pacman -Syyu
::INFO Downloading mirrors from Manjaro
::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json
::INFO => Mirror status: https://repo.manjaro.org/status.json
::INFO Using default mirror file
::INFO Querying mirrors - This may take some time
0.518 Bulgaria : https://mirror.telepoint.bg/manjaro/
0.324 Germany : http://ftp.uni-kl.de/pub/linux/manjaro/
0.557 Belarus : http://mirror.datacenter.by/pub/mirrors/manjaro/
0.429 Germany : https://mirror.netcologne.de/manjaro/
1.746 Kenya : https://manjaro.mirror.liquidtelecom.com/
::INFO Writing mirror list
::Germany : http://ftp.uni-kl.de/pub/linux/manjaro/stable
::Germany : https://mirror.netcologne.de/manjaro/stable
::Bulgaria : https://mirror.telepoint.bg/manjaro/stable
::Belarus : http://mirror.datacenter.by/pub/mirrors/manjaro/stable
::Kenya : https://manjaro.mirror.liquidtelecom.com/stable
::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
:: Synchronizing package databases...
core 140.0 KiB 392 KiB/s 00:00 [######################] 100%
extra 8.3 MiB 8.62 MiB/s 00:01 [######################] 100%
community 29.0 B 414 B/s 00:00 [######################] 100%
multilib 144.7 KiB 2.52 MiB/s 00:00 [######################] 100%
:: Starting full system upgrade...
there is nothing to do
[manjaro /]# update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
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.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
I was trying to follow the tutorial that you wrote but I cannot understand so good and I’m afraid to destroy the system haha
I will elaborate on why it is a bad idea a bit:
It does not show the log, what is really happening, it only shows a logo it seems; secondly, you are already out of the session so if something goes wrong you cannot start fixing right away, you have to hard-reboot, and you know you will not be able to properly boot, so you need live usb to chroot. Not fatal, but unnecessary extra step.
@ZeR0ByTe Ok maybe only the kernel is broken. It is normal that grub does not see the os, if there is no kernel
so try
pacman -S linux66
or if there is a problem (it might be)
pacman -S linux61
and update grub and you should have at least 1 kernel and a booting system
[manjaro /]# pacman -Syu linux61
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
warning: linux61-6.1.92-1 is up to date -- reinstalling
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (1) linux61-6.1.92-1
Total Installed Size: 143.67 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/2) Creating Timeshift snapshot before upgrade...
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
(2/2) Remove upgraded DKMS modules
==> dkms remove --no-depmod vmware-workstation/17.5.1_23298084 -k 6.1.92-1-MANJARO
:: Processing package changes...
(1/1) reinstalling linux61 [##################################] 100%
:: Running post-transaction hooks...
(1/7) Arming ConditionNeedsUpdate...
(2/7) Updating module dependencies...
(3/7) Install DKMS modules
==> dkms install --no-depmod vmware-workstation/17.5.1_23298084 -k 6.1.92-1-MANJARO
==> depmod 6.1.92-1-MANJARO
(4/7) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.1-x86_64 -g /boot/initramfs-6.1-x86_64.img
==> Starting build: '6.1.92-1-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [kms]
-> 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: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.1-x86_64.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.1-x86_64 -g /boot/initramfs-6.1-x86_64-fallback.img -S autodetect
==> Starting build: '6.1.92-1-MANJARO'
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> 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: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.1-x86_64-fallback.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
(5/7) Updating Kernel initcpios for Nvidia-DRM...
(6/7) Refreshing PackageKit...
Error connecting: Could not connect: No such file or directory
error: command failed to execute correctly
(7/7) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
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
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.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
And also:
[manjaro /]# mhwd-kernel -li
Currently running: 6.9.0-1-MANJARO (linux69)
The following kernels are installed in your system:
* linux515
* linux54
* linux61
* linux66
You should be now able to boot the 6.1 kernel. Note that you still have remnants of 3 other broken kernels, and untended pacnews, but is can be fixed at a later time.
But even Windows actually tells you that it’s doing that, and not to power off. If pamac does it without any indication then I agree with @Teo, that’s an unbelievably stupid idea.
