my life ain’t easy , nothing happens straight ahha
[parasetu@pasec ~]$ sudo pacman -S arch-install-scripts
[sudo] password for parasetu:
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
if you're sure a package manager is not already
running, you can remove /var/lib/pacman/db.lck
Thank you @dmt@Nachlese , for all the time and patience , its already above 2 am here, idk what more to do , i’ll probably go to sleep , because this issue seems to be another big thing but appreciate your help and i’ll try to boot from a live usb , hope it will help :))
yeah , don’t wanna give you more trouble , you guys already helped a lot , i’m just a bit worried turning off the pc as well , but hope things will be alright.
This does nothing for the current issue(s), however for future reference (when you eventually decide to reinstall everything) – you only need one ESP partition no matter how many OS you wish to install.
I’m guessing the only reason you don’t already have a single $ESP is perhaps a lack of confidence using the respective manual partitioning methods of each OS you installed.
All that really needs to be done when installing a second (or third) OS is to select the existing $ESP, assign it the mount point required by the new OS, and remember to not select the $ESP to be partitioned.
The UEFI boot files should be installed to the respective folder for each OS, on the same $ESP – /EFI/Arch or /EFI/Manjaro, for example.
When trying to manage so many (more than two) OS on a machine, I suggest that the rEFInd UEFI Bootloader may be beneficial – choosing rEFInd as the default loader would allow it to effectively manage all OS present.
okay guys , I’m back and when i tried to boot into the system it did boot straightaway , but it was a bit slow , could be because of the new address allotment , besides that , I have updated the grub and the outcome doesn’t show manjaro , so do i need to chroot or is it fixed after grub update
sudo update-grub
[sudo] password for parasetu:
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.11-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.11-x86_64.img
Found initrd fallback image: /boot/initramfs-5.11-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.14-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Found Ubuntu 20.04.1 LTS (20.04) on /dev/nvme0n1p5
Found EndeavourOS Linux (rolling) on /dev/sdb13
Found Garuda Linux (Soaring) on /dev/sdb4
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
yes sir , i booted into manjaro and then updated the grub , but on reboot still the bios is not of manjaro and its of garuda and i have done virtualisation on my cpu aswell divided my two graphics card so when i connect DP cable with graphic card , it will go blank as it can not be accessed by Garuda and will be only accesses by the VM(Virtual machine) inside of garuda.
Every single one in that list is o.k. to install - except for the -rt kernels.
You should have a very specific reason to try to use those.
… just don’t.
After you installed one or two supported kernels - boot into one of them and remove the ones that are no longer up to date.
You seem to have fundamental lack of understanding of computers, and in particular, the boot processes involved. I see now why this thread is fast approaching 80 posts with no clear resolution.
At least you seem to be booting Manjaro;
Is each installed OS also booting as expected now?
but appreciate your help and i’ll try to boot from a live usb , hope it will help :))
