Hello there,
As the latest update was being installed, plasma just died on me, and I stupidly shutdown nowed the laptop while the update was still running.
After I did that I got an error like the following one:
Loading Linux linux
error: file '/boot/vmlinuz-linux' not found.
Loading inital ramdisk ...
error: you need to load the kernel first.
Press any key to continue...
So after doing some research I booted from a live USB and manjaro-chroot -aed into the filesystem and completed the update.
After doing that and rebooting I started to get the following error:
mount: /new_root: unknown filesystem type 'ext4'.
dmesg(1) may have more information after failed mount system call.
ERROR: Failed to mount 'UUID=the-uuid-which-i-can't-be-bothered-to-type-out' on real root
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ~]#
This is the first time I face such an issue, and I literally have no idea about how to go about debugging this issue, I’d really appreciate any help on how to fix this issue, thanks in advance.
Edit: I have two disks in my laptop, one for my home directory and one for my system root, both are in ext4 format.
Edit 2: This is the output of update-grub:
...
ERROR: mkdir /var/lock/dmraid
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you don't think an error has occurred, please file a bug report...
Thanks for your swift response @Mirdarthos l, but for some reason everytime I run the command:
I get the following error:
error: no targets specified (use -h for options)
However after checking the command’s help the command seems fine…
Edit: I don’t think that this is the issue, because as I mentioned in the post I completed the installation and the error that you quoted stopped showing up, and the error that shows up on boot is the following error:
Furthermore, when running mhwd-kernel -li it shows linux515 and linux66.
So there is probably a non-chroot way to do this, I’d be surprised if there wasn’t, but boot into the chroot environment as before, and please provide the output of:
It turns out that the issue was corrupted Kendall installations even though package excited successfully, so I removed all newly installed kernels and rebooted and all was good.