Is there any way to modify the grub-install command in ArcoLinux calamares installer?
Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is there any way to modify the grub-install command in ArcoLinux calamares installer?
I need to append --removable to the grub-install command to actually install Grub. Is there any way to do that in a graphical installer such as ArcoLinux calamares? I tried editing the bootloader.conf and change grub-install line there to include --removable, but that just says that no such file or directory exists. Install log: https://termbin.com/xwz1 without editing the grub-install command. https://termbin.com/p5cf with --removable
In bootloader.conf, grubInstall section:
grubInstall: "grub-install --removable"
is the reason your getting grub install errors. You need an efi partition at least 200MB formatted fat32 flagged as esp.
"Some motherboard manufacturers seem to only support the /efi/boot/ directory location for the .EFI file in the EFI System Partition (ESP). The GRUB installer can perform this operation automatically with the --removable option. "
- Gentoo wiki
The installer does create an ESP, but my motherboard doesn't like the way it's configured.
Can you just ignore it ?. Most installers do the boot-loader last and if it fails who cares - just chroot into it and fix the loader however you wish.
Haven't touched gentoo in years, and haven't bothered to attempt to munge calamares, so take all this for what it's worth.
Ok, if I understood this correctly:
1. Install the system
2. Close the installer when GRUB fails to install
3. Chroot into the installed system and execute the grub-install and grub config commands
That would be my take on it - if it doesn't work, nothing lost. I have had to do this on Fedora and apt-based systems, and no noticeable adverse effects. But they had solid bug reporting systems that are acted on. No knowledge of Void's capabilities in this respect.
That would be my take on it - if it doesn't work, nothing lost. I have had to do this on Fedora and apt-based systems, and no noticeable adverse effects. But they had solid bug reporting systems that are acted on. No knowledge of Void's capabilities in this respect.
It is now saying this:
grub-install: error: failed to get canonical path of /boot/efi
And that's when not chrooted
When chrooted it says:
cannot find a device for /boot/efi (is /dev mounted?)
Last edited by LeonScoretzka; 09-12-2021 at 04:26 AM.
Reason: correction
did you post the /etc/fstab of the live system or the /etc/fstab located on partition nvme0n1p2?
This is the one from the chrooted system:
Code:
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=7681-3B10 /boot/efi vfat umask=0077 0 2
UUID=34d929a0-f084-40ad-bfac-4f4e0c10f8fb / ext4 defaults,noatime 0 1
/swapfile swap swap defaults,noatime 0 0
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.