Please forgive my lack of understanding I used windows for most of my life.
I was updating using AUR in the background and trying to use adb to get into a broken phone I noticed that my start menu had no icons like it was empty. I thought I messed something up running the adb commands on my laptop and not connecting to the phone to run the commands. I noticed there was an error with the update but didn’t read it before restarting.
I then get this error when booting.
Error: end of file /boot/vmlinuz-6.1-x86_64
I tried going into advanced options but unfortunately the fallback is the exact same kernel version as the default and doesn’t work either.
I have looked at other threads that have similar issues and made a live Manjaro usb so I can boot into that and repair the one on my system however my disk has full encryption so I am at a loss as to how to do this.
When I try to run
manjaro-chroot -a
I get
grub-probe: error: cannot find a GRUB drive for dev/sdb1. Check your device.map
ERROR: No Linux partitions detected!
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found lunux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/intel-ucode.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 GRIB drive for /dev/sdb1. Check your device.map.
Adding boot menu entry for UEFI Firmware Settings …
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
I restart and pull out the flash drive. I am prompted for my password but after I get the same error.
Error: end of file /boot/vmlinuz-6.1-x86_64
Error: you need to load the kernal first
While in chroot I used that command. It doesnt give me any output and just went down to the next line. It is not installing any new kernels when I check with
mhwd-kernel -li
When I use the command
sudo mhwd-kernel -i linux66
It just goes to the next line and doesn’t give me any feedback to share with you. I tried various different kernels with the same result.
I used
mhwd-kernel -li
To see if the any new kernels were installed.
It shows
Currently running: 6.5.5-1-MANJARO (linux65)
The following kernels are installed in your system:
*linux61
When I run
mhwd-kernel -l
I get
Available kernels:
*linux419
*linux510
*linux515
*linux54
*linux61
*linux65
*linux66
*linux61-rt
*linux65-rt
*linux66-rt
For some reason using
sudo mhwd-kernel -i linux66
Does nothing
but if I try
mhwd-kernel -i linux66
I get
Synchronizing package databases…
Core 100%
Extra 100%
Community is up to date
Multilib is up to date
Error: no targets specified (use -h for help)
If you are in chroot that makes perfect sense, since you ARE root and sudo should not be used.
I haven’t actually read the whoe thread you pulled me in here from another remember.
I installed and tried every kernel I the furthest I got was a login screen which would just ask me to relog in once I already had logged in.
I think my issue is the same as this thread.
At this point I want to copy the contents of my whole drive to an external and do a fresh install.
Would I use rsync to do this? I just dont understand what the path is out of my unencrypted drive once I have done the mounting and chrooting into my encrypted drive.
I found that dolphin file manager could do what I needed. I used AUR on the USB run manjaro to install it and then didnt restart my machine. I right clicked the external drive and set it to modify files so I could copy everything over there.
I hadnt realized that using AUR could do this to my system. Thanks for all your help!
Please do not do this again
The problem is not AUR itself
Some things that others can learn from it
It cannot be said often enough:
Do update in a terminal
Do read the update-thread ahead of it
Do read error-messages
Do update AUR only if you already updated the base-system without errors
P.S.:
In principle, saving an encrypted system is much more difficult than saving an unencrypted one. (> 1 day)
Backups help you not to have to put in too much effort in the event of a crash, but rather to be able to simply reinstall and restore your data. (1 hour)
Timeshift / snapper and btrfs help you get out of a crash with a simple rollback (5 minutes)
I had the similar issue but after an update with pacman -Syu in the background funnily enough i had been using adb with a device prior although i don’t believe it was related to my issue.
Whilst it was updating it moved on to upgrading packages, unfortunately it seemed to hang while updating Virtualbox, it was stuck upgrading this packages for about 15 mins, i assumed there must have been a problem, not acknowledging that it had also yet to update the kernel i used ctrl+c interrupt signal and then rebooted.
At this point it would not boot past the boot loader as it would say the same error message that the kernel was not present or unable to find kernel image. I checked the grub boot script using e but it was showing a boot script, so i chrooted using a bootable USB archlinux installation and continued with pacman -Syu to finish upgrade rest of packages then used grub-mkconfig -o /boot/grub/grub.cfg then i found out that manjaro has update-grub command which i could have used lol. All jokes aside now my grub script did not show any instructions to boot . Long story short i noticed the kernel image in /boot had a .kver extension and /etc/mkinitcpio.d/ did not show my kernel version although 2 others that i was running before i was running the current one. My suspicions that it was a kernel issue anyway as was expecting to see vmlinuz on its own in /boot not with that extension that i haven’t seen before plus at least an initramfs.img image but neither was present only the one with .kver extension, as i was originally trying to boot from grub command line but couldn’t find the files.
I ran mhwd-kernel -i linux515 whilst i was chrooted in the filesystem all outputed the same error message so tried all the different versions until linux66 which did seem to work and asked me to confirm installation, and rebooted.
I could now see a populated boot script using grub E command from Manjaro grub splash screen with the kernel version linux66 option showing to boot from. Failing this would have tried installing a new kernel via pacman.
following this link also helped
I Hope my experience with this situation could be of use to someone.
. Long story short i noticed the kernel image in /boot had a .kver extension and /etc/mkinitcpio.d/ did not show my kernel version although 2 others that i was running before i was running the current one. My suspicions that it was a kernel issue anyway as was expecting to see vmlinuz on its own in /boot not with that extension that i haven’t seen before plus at least an initramfs.img image but neither was present only the one with .kver extension, as i was originally trying to boot from grub command line but couldn’t find the files.