I accidentially turned off my pc while updating and now it says it cant find the /boot/vmlinuz54 file

my direct problem is the fact that i dont really know anything about what to do with chroot
i found out i probably need to get into my system (drive is sda2) and then reinstall the kernel (?) i just dont know how to do this and all the other guides i found didnt work
im running only linux on kernel54 i am booted into a live cd and have acess to internet (if that helps)
im running the standard desktop layout of manjaro which should be kde if im not mistaking (if that helps)

  1. Boot up your live usb.

  2. Connect to internet.

  3. Open a terminal and run sudo manjaro-chroot -a (if only one linux system present, type 1 instead of 0)

  4. Once in chroot update the system: pacman -Syu

  5. Rebuild the initramfs: mkinitcpio -P

  6. Update the grub: update-grub

  7. Quit chroot: exit

  8. Reboot your system.

Hope this helps!

:crossed_fingers:t3:

2 Likes

step 3 output is this:
==> Mounting (ManjaroLinux) [/dev/sda2]
--> mount: [/mnt]
mount: /mnt: /dev/sda2 already mounted on /mnt.
--> mount: [/mnt/boot/efi]
mount: /mnt/boot/efi: /dev/sda1 already mounted on /mnt/boot/efi.

step 4 gives me this issue
:: 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 synchronize all databases

error: failed to update core (unable to lock database)

Remove the lock:

rm /var/lib/pacman/db.lck

and again:

pacman -Syu

should i be worried if it says /proc lacks process entries? (not mounted?)
edit i guess yes
mkinitcpio -P
==> ERROR: /proc must be mounted!

Looks like you are not properly chrooted:

You can either unmount /dev/sda1 and /dev/sda2 and use sudo manjaro-chroot -a

or, run the following commands before proceeding with step 4 and the rest:

mount -t proc proc /mnt/proc
mount -t sysfs sys /mnt/sys
mount -o bind /dev /mnt/dev
mount -t devpts pts /mnt/dev/pts/
chroot /mnt

i think i have a problem

mount -t proc proc /mnt/proc
mount: /mnt/proc: mount point does not exist.

Please try unmounting the partitions and use the automatic chroot to see if it fares better.

ok i will

1 Like

how do i do that? because i thought it was unmount /dev/sda2 but it told me
umount: /dev/sda2: umount failed: No such file or directory.

ok i figured out how to unmount sda1 sda2 is "busy"
umount /dev/sda2
umount: /mnt: target is busy.

ok nvm my other answers got past that now i have a problem with updating the grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
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.
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

Looks good.

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.

This is your live usb I suppose. Reboot now and see if you can boot up normally from Grub menu.

ok i will see

Thank you so much my System works again :smiley:

1 Like

You are welcome! That's great to hear!

:wave:t3:

2 Likes

do you have an idea why my firefox doesnt work now?

No. It would be better to start a new thread to get specific help with troubleshooting that.

ok thank you

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by