Started an update on the latest kde plasma. It was a lengthy update so I left to let it do it’s thing. The computer was off when I returned, and attempts to boot were unsuccessful. on booting, the message
error: file ‘/boot/vmlinuz-5.18-x86_64’ was not found
error: you need to load the kernal first.
Attempts to boot in other kernels or fallback mode cause the system to hang during the boot process.
Sorry for the limited info. Slow typing this into an iPad.
The fact that your computer was shut down was probably due to a power outage, and what you describe here-above is indeed what happens when the machine is shut down during an update.
The package manager first downloads the packages, and then it removes the kernel images and initcpios at the beginning of the actual update process, and only when all packages have been upgraded does it put the new kernel images in /boot, recreates the initcpios, and then updates the bootloader configuration.
What you need to do to remedy this situation is boot up in the live mode of the USB stick or CD/DVD that you used for installing — or any other recent Manjaro installer medium — and open up a terminal window. Then, type the following commands…
sudo su -
[ -f /var/lib/pacman/db.lck ] && rm -f /var/lib/pacman/db.lck
pacman-mirrors -f5 && pacman -Syyu
Let the process finish, no matter how long it takes. Then, when the command prompt returns, leave the chroot environment by either pressing Ctrl+D or by typing the command…
Repeat that in order to close the terminal window, and then cleanly reboot your computer, making sure that you remove the removable drive in time.
Only if you’re running a software RAID configuration, but even then still it would be weird, because I don’t think dmraid is used all that much anymore.
That message is normal — it’s just the regular boot-time filesystem check — and probably hasn’t got anything to do with why the machine hangs. But the hanging itself isn’t normal, and I have no idea why it does that.
Thank-you for your help. This group has been phenomenal in supporting its users. This is very much appreciated.
There could be any number of ‘holes’ in the software if the update process was interrupted. It was a sizeable update of several GBs. Would there be any hope of recovering this installation? Or would it be necessary to do a new install?
Well, someone other than me might come up with certain things to check for, and there are plenty of threads here at the forum about freezes at boot time, so perhaps best to look around and wait for better advice.
if you were trying to boot with the 5.17 you would be stuck … this kernel is end of life so remove it: mhwd-kernel -r linux517
reinstall the other two: pacman -S linux515 linux518
then post output from: mhwd -l && mhwd -li
just to be sure lets reinstall also the video drivers:
uninstall them: mhwd -r pci video-nvidia mhwd -r pci video-linux
install them again: mhwd -i pci video-linux mhwd -i pci video-nvidia
any error post here, if there are none, reboot
It did throw an error, not sure if this is critical:
[manjaro /]# pacman -R cuda
:: blender optionally requires cuda: cycles renderer cuda support
:: openmpi optionally requires cuda: cuda support
Packages (1) cuda-11.7.1-1
Total Removed Size: 3915.24 MiB
:: Do you want to remove these packages? [Y/n] Y
:: Processing package changes...
(1/1) removing cuda [##########################################################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Refreshing PackageKit...
Error connecting: Could not connect: No such file or directory
error: command failed to execute correctly
[manjaro /]# pacman -Qs cuda
International Components for Unicode library
International Components for Unicode library (32 bit)
High performance message passing library (MPI)