[joe-Manjaro ~]# manjaro-chroot -a
==> Mounting (Ubuntu) [/dev/sdb1]
--> mount: [/mnt]
--> mount: [/mnt/home]
mount: /mnt/etc/resolv.conf: mount point is a symbolic link to nowhere.
Need to select some option to that command?
root@joe-Manjaro:/# pacman-mirrors -f 5 && pacman -Syyu
pacman-mirrors: command not found
[joe-Manjaro ~]# manjaro-chroot /manjaro
mount: /manjaro/proc: mount point does not exist.
==> ERROR: failed to setup API filesystems in chroot /manjaro
A question just out of curiosity:
The Ubuntu grub is showing kernel version 2.6.32? This kernel is from 2010 or so. Which installation image did you use?
First of all I would like to mention that my long contact with ubuntu left me with remnants and a way to solve problems.
Let me explain.
I used applications eg (grub customizer) and I did not have much contact with the terminal and the essence of linux which I believe is the deep knowledge of the structure and interdependence of the components that make up the operating system in general.
On the other hand, I am old enough to deal with it now, but I will also try the fact that I do not know English well.
I would like you to tell me some link to learn what you think I should learn.
Now on to the topic I uploaded I solved it using the grub customizer but I would like to try to analyze the steps needed to solve a problem of this size sometime in the future.
Don’t use grub-customizer in Manjaro. It’s not compatible with the already customized GRUB that Manjaro uses. It is however still offered in the repositories because Manjaro also offers grub-vanilla as an alternative boot loader, and grub-customizer does work with that one.
/dev/sda1 then. /dev/sda is your drive itself, and you cannot mount a drive. Well, you can, but only if there is no partition table and the drive has a single, large filesystem on it, and drives like that are not bootable.
It properly chroots into the on-disk installation, including the mounting of /dev, /proc and /sys within the chroot environment.
It fast-tracks five mirrors, synchronizes the databases and commences a full system update.
It installs GRUB to the default location for your platform (i.e. the master boot record of the drive in an MSDOS partition table, or the EFI system partition in a UEFI system), without the Reed-Solomon error-correcting codes (which are often problematic in UEFI setups), and with the modules to support both GPT and MSDOS partition tables preloaded.
I just install Ubuntu MATE alongside Manjaro MATE yesterday. To let Manjaro handle grub you have to reinstall grub from your Manjaro installation after booting with fallback initramfs:
First check where grub is installed:
[kunruh@thinkfreax ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0 0 476,9G 0 disk
├─nvme0n1p1 259:1 0 1G 0 part /boot/efi
├─nvme0n1p2 259:2 0 32G 0 part
├─nvme0n1p3 259:3 0 64G 0 part /
└─nvme0n1p4 259:4 0 379,9G 0 part
└─luks-b682afc6-8cfb-4311-970a-3b7e35fc05ab
254:0 0 379,9G 0 crypt /home
In may case it is nvme0n1p1 (mountpoint is /boot/efi)