I think the reason why it’s failing is because I had interrupted manjaro when it was updating. I have looked up similar problems but they had very specific fixes for their machines.
Thanks.
you boot on USB manjro live
open a terminal
sudo manjaro-chroot -a
pacman-mirrors -c all
pacman -Syyu
exitthen reboot
2 Likes
Sorry for not giving the output of lsblk as it was getting late and I quickly made this post.
Output:
loop0 7:0 0 85.1M 1 loop /run/miso/sfs/livefs
loop1 7:1 0 619.2M 1 loop /run/miso/sfs/mhwdfs
loop2 7:2 0 1.3G 1 loop /run/miso/sfs/desktopfs
loop3 7:3 0 663.5M 1 loop /run/miso/sfs/rootfs
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 16M 0 part
└─sda2 8:2 0 465.7G 0 part
sdb 8:16 0 698.6G 0 disk
├─sdb1 8:17 0 450M 0 part
├─sdb2 8:18 0 260M 0 part
├─sdb3 8:19 0 128M 0 part
├─sdb4 8:20 0 534.4G 0 part
├─sdb5 8:21 0 904M 0 part
├─sdb6 8:22 0 450M 0 part
├─sdb7 8:23 0 6.9G 0 part
├─sdb8 8:24 0 127G 0 part
├─sdb9 8:25 0 2.8G 0 part
└─sdb10 8:26 0 8M 0 part
sdc 8:32 1 7.5G 0 disk /run/miso/bootmnt
├─sdc1 8:33 1 2.7G 0 part
└─sdc2 8:34 1 4M 0 part
sr0 11:0 1 1024M 0 rom
nvme0n1 259:0 0 119.2G 0 disk
├─nvme0n1p1 259:1 0 100M 0 part
├─nvme0n1p2 259:2 0 118.1G 0 part
├─nvme0n1p3 259:3 0 100M 0 part
└─nvme0n1p4 259:4 0 990M 0 part
Also, here’s there output of sudo manjaro-chroot -a:
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
==> Detected systems:
--> 0) ManjaroLinux
==> Select system to mount [0-0] :
Not sure what to do from here
Quickly stepping in here to make sure you better understand the post above yours.
- “Chroot” is a command that will give you read-write access to your installed system from a live iso booted from e. g. an usb-stick, which gives you the ability to ‘repair’ your installed system.
- If you issue the command
sudo manjaro-chroot -ayou’re prompted with a list of installed operating systems, in your case Manjaro. You would have to select it by typing0and then Enter. - Now you’re ‘inside’ your installed Manjaro and can E.G. update your repository mirrors, databases and system, as will be done by
pacman-mirrors -c allandpacman -Syyu
Hope this helps 
1 Like
==> ERROR: You can't mount 0!
Any ideas?
What steps did you take?
sudo manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
==> Detected systems:
--> 0) ManjaroLinux
==> Select system to mount [0-0] :
0
==> ERROR: You can't mount 0!
To be honest personally I’ve never ‘liked’ using manjaro-chroot since it’s buggy imho, but have been using the built-in live-rescue tool of MX-Linux, which never failed me. If you wanna get hold of a MX iso and try that. But maybe someone else will step in that has a clue what might be wrong…
I did sudo manjaro-chroot -a again and this time I went with this:
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdc1. Check your device.map.
==> Detected systems:
--> 0) ManjaroLinux
==> Select system to mount [0-0] :
0-1
==> Mounting (ManjaroLinux) [/dev/sdb8]
--> mount: [/mnt]
I then went with pacman-mirrors -c all and that went fine
But when I did pacman -Syyu, it came up with this:
[manjaro /]# pacman -Syyu
:: Synchronizing package databases...
error: failed to update core (unable to lock database)
error: failed to update extra (unable to lock database)
error: failed to update community (unable to lock database)
error: failed to update multilib (unable to lock database)
error: failed to update sublime-text (unable to lock database)
error: failed to synchronize all databases
Do a rm /var/lib/pacman/db.lck and try again…
Is there any real downside to getting rid of this lock?
Just make sure to not delete it while pacman is running
What do you mean by “pacman”?
Pacman is Manjaro’s cli package manager, as in pacman -Syyu
You can check for running pacman processes with:
ps -e | grep pacman
1 Like
After restarting, it sent me into TTY. It says something about modules 5.9.16-1 modules not found.
It says i’m in an emergency shell
Did you successfully update your system?
grub-update? No 
Can I do it in the emergency shell?
Please chroot again and do the following:
pacman -Syyu
mhwd-kernel -i linux510
and to be on the safe side
update-grub
This will install linux kernel 5.10, for linux59 has reached EOL (End Of Life)
1 Like
Whenever I turn on the pc, it sends me to the emergency shell, how do I leave? Also, there is no input in the emergency shell
Wait, i’m just being dumb, during the reboot I pressed escape and sent me to the Grub boot menu. I went into 5.4 instead
1 Like