I upgraded some packages form my manjaro linux and when I restarted the computer, I couldn’t even get to the boot maneger. I have a dual boot windows-manjaro and when I power up the computer it shows a black screen. I can only get to windows pressing F11 and I can’t boot to manjaro.
So, what I did was to boot from a usb and then follow the posts on the forum. Here is some stuff I tried (not in a particular order):
[manjaro manjaro]# manjaro-chroot -a
==> Detected systems:
→ 0) ManjaroLinux
==> Select system to mount [0-0] :
0
==> ERROR: You can’t mount 0!
[manjaro manjaro]# mount /dev/nvme0n1p1 /mnt/boot/efi
mount: /mnt/boot/efi: mount point does not exist.
I have three partitions: home(nvme0n1p5), root(nvme0n1p6), boot(nvme0n1p1).
[manjaro manjaro]# mount -t proc proc /mnt/proc
mount: /mnt/proc: mount point does not exist.
[manjaro manjaro]# mount -t sysfs sys /mnt/sys
mount: /mnt/sys: mount point does not exist.
Right after booting, whithout trying to mount anything the partitions look like this:
retry with 1 anyway … instead of 0
it’s a wierd bug
first system is listed as 0
but can only be selected by putting 1 …
I don’t know if it’s old and now fixed - but incrementing the choice by 1 … should work
… worst case: it still doesn’t work - just as now …
so: try it
With the “manual” method, you first have to mount the partition with your / filesystem on it
to /mnt
then there will be the /mnt/proc directory
to mount the proc filesystem to
… and the others …
which isn’t/aren’t there if you didn’t mount the partition with the / filesystem first …
it seems you missed a step …
I heard/read it is fixed - it came from different behaviours between UEFI and MBR booted systems - AFAIK
… it’s probably an older ISO that he is using, with the bug still present
I once found Manjaro appealing - I now am back to Arch (via ArchLabs installer)
… although pure Arch is actually really simple to install - just the basic config takes too much time for my taste
… Manjaro is still cool
I might give Arch a go. Someday. But not now. I’m extremely happy with Manjaro. It makes it so easy to learn and still have a blazingly fast system! And it’s easy to stsy up to date. In fact, it actually takes effort not to!
Manjaro is the perfect balance between easy and powerful!
… that’s not what I found …
…
what I found - for me - is:
due to the delayed updates
and the sometimes self made changes
(separate repositories …)
problems will arise
and be unfixable
until some … later time
or fixable by … switching branches … or something …
of course there is a way, always -
but not easy or even accessible to a casual user
… Arch has never given me much of any problem
… while Manjaro … relatively constantly does
unfortunately …
I’ll be converting my fathers laptop from Manjaro - which has worked quite well for the last at least two or three years - to …
Mint
… it’s just much less hassle to keep it working …
…
I know what to do - and how
but my father doesn’t …
I love Manjaro, personally. It’s the first Linux I’ve felt comfortable enough with to wipe Windows.
But, honestly? As long as you’re somewhere in the Linux world, you"re OK in my books!
Sorry for answering late, I’ve been very busy. So, I tried with the “manjaro-chroot -a” then selecting one. It worked!! I did this exactly this after booting into the usb:
[manjaro@manjaro ~]$ su [manjaro manjaro]# manjaro-chroot -a
==> Detected systems:
→ 0) ManjaroLinux
==> Select system to mount [0-0] :
1
==> Mounting (ManjaroLinux) [/dev/nvme0n1p5]
→ mount: [/mnt]
→ mount: [/mnt/boot/efi]
→ mount: [/mnt/home] [manjaro /]# pacman -Syyuu
warning: config file /etc/pacman.conf, line 100: directive ‘“n[sublime-text]nServer’ in section ‘multilib’ not recognized.
:: Synchronizing package databases…
core 165.7 KiB 1467 KiB/s 00:00 [######################] 100%
extra 2000.9 KiB 12.5 MiB/s 00:00 [######################] 100%
community 6.6 MiB 41.0 MiB/s 00:00 [######################] 100%
multilib 181.1 KiB 0.00 B/s 00:00 [######################] 100%
sublime-text 1827.0 B 0.00 B/s 00:00 [######################] 100%
sublime-text.sig 542.0 B 0.00 B/s 00:00 [######################] 100%
:: Starting full system upgrade…
there is nothing to do [manjaro /]# update-grub
Generating grub configuration file …
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.9-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.9-x86_64.img
Found initrd fallback image: /boot/initramfs-5.9-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.8-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.8-x86_64.img
Found initrd fallback image: /boot/initramfs-5.8-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.7-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.7-x86_64.img
Found initrd fallback image: /boot/initramfs-5.7-x86_64-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings …
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done [manjaro /]# exit
exit
→ umount: [/mnt/home]
→ umount: [/mnt/boot/efi]
→ umount: [/mnt] [manjaro manjaro]# exit
exit [manjaro@manjaro ~]$
After this I restart the PC and nothing happened. I couldn’t boot manjaro. Any ideas on what should I do or why did this happen?
I did what you said and I could do everything except for
mkinitcpio -P
When I executed this command I got this errors:
==> ERROR: ‘/lib/modules/5.7.19-2-MANJARO’ is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux57.preset: ‘fallback’
→ -k /boot/vmlinuz-5.7-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.7-x86_64-fallback.img -S autodetect
==> ERROR: ‘/lib/modules/5.7.19-2-MANJARO’ is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: ‘default’
→ -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64.img
==> ERROR: ‘/lib/modules/5.8.18-1-MANJARO’ is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux58.preset: ‘fallback’
→ -k /boot/vmlinuz-5.8-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.8-x86_64-fallback.img -S autodetect
==> ERROR: ‘/lib/modules/5.8.18-1-MANJARO’ is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: ‘default’
→ -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64.img
==> ERROR: ‘/lib/modules/5.9.16-1-MANJARO’ is not a valid kernel module directory
==> Building image from preset: /etc/mkinitcpio.d/linux59.preset: ‘fallback’
→ -k /boot/vmlinuz-5.9-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.9-x86_64-fallback.img -S autodetect
==> ERROR: ‘/lib/modules/5.9.16-1-MANJARO’ is not a valid kernel module directory
Before all this, when I turned on the computer I got to the boot manegment where I could chose between windows and manjaro. Now if I want to enter windows I have to press f11 and chose windows and if I want to boot manjaro, I have to press escape and then chose the correct kernel.
How can I make it so I can boot like before? Like having the option of windows and manjaro at the manjaro boot options.
Thanks so much again, I thought I would have to delete the entire OS and install it again.
