LinuxQuestions.org
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Linux - Distributions (https://www.linuxquestions.org/questions/linux-distributions-5/)
-   -   Is there any way to modify the grub-install command in ArcoLinux calamares installer? (https://www.linuxquestions.org/questions/linux-distributions-5/is-there-any-way-to-modify-the-grub-install-command-in-arcolinux-calamares-installer-4175700500/)

LeonScoretzka 09-11-2021 02:17 PM
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"

I don't know what to do. Can anyone help me?

colorpurple21859 09-11-2021 06:41 PM
This is your problem from your first link
Quote:
WARNING: system is EFI but no EFI system partitions found.
is the reason your getting grub install errors. You need an efi partition at least 200MB formatted fat32 flagged as esp.

LeonScoretzka 09-12-2021 01:02 AM
Quote:
Originally Posted by colorpurple21859 (Post 6283403)
This is your problem from your first link

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.

syg00 09-12-2021 02:44 AM
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.

LeonScoretzka 09-12-2021 02:54 AM
Quote:
Originally Posted by syg00 (Post 6283463)
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

syg00 09-12-2021 03:01 AM
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.

LeonScoretzka 09-12-2021 04:24 AM
Quote:
Originally Posted by syg00 (Post 6283465)
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?)

syg00 09-12-2021 04:46 AM
Did you mount /boot/efi ?.

colorpurple21859 09-12-2021 08:28 AM
The --removable option puts the grubx64.efi in /Boot/bootx64.efi on the efi partition and doesn't register it in the firmware/bios of the system.

Both of your links
Quote:
WARNING: system is EFI but no EFI system partitions found
If the efi partition can't be found there is something wrong with your setup.

post the output of
Code:
lsblk -f

LeonScoretzka 09-12-2021 08:52 AM
Quote:
Originally Posted by syg00 (Post 6283479)
Did you mount /boot/efi ?.
I did

LeonScoretzka 09-12-2021 09:20 AM
Quote:
Originally Posted by colorpurple21859 (Post 6283505)
The --removable option puts the grubx64.efi in /Boot/bootx64.efi on the efi partition and doesn't register it in the firmware/bios of the system.

Both of your links
If the efi partition can't be found there is something wrong with your setup.

post the output of
Code:
lsblk -f
lsblk -f:
Code:
NAME FSTYPE FSVER LABEL            UUID                                FSAVAIL FSUSE% MOUNTPOINTS
loop0
    squash 4.0                                                                0  100% /run/archiso/airootfs
sda                                                                                   
|-sda1
|    exfat  1.0  Ventoy            6EBD-7A57                                         
| `-ventoy
|    iso966 Jolie arcolinuxb-openbox-v21.09.8
|                                  2021-08-07-15-26-22-00                    0  100% /run/archiso/bootmnt
`-sda2
    vfat  FAT16 VTOYEFI          7502-2467                                         
sdb                                                                                   
nvme0n1
|                                                                                     
|-nvme0n1p1
|    vfat  FAT32 NO_LABEL          7681-3B10                                         
`-nvme0n1p2
    ext4  1.0                    34d929a0-f084-40ad-bfac-4f4e0c10f8fb

colorpurple21859 09-12-2021 09:29 AM
post /etc/fstab

LeonScoretzka 09-12-2021 09:40 AM
Quote:
Originally Posted by colorpurple21859 (Post 6283513)
post /etc/fstab

Code:
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
Looks like there's nothing there. I wonder why?

colorpurple21859 09-12-2021 09:51 AM
did you post the /etc/fstab of the live system or the /etc/fstab located on partition nvme0n1p2?

LeonScoretzka 09-12-2021 09:54 AM
Quote:
Originally Posted by colorpurple21859 (Post 6283523)
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


All times are GMT -5. The time now is 12:03 PM.
Page 1 of 2 1 2
Show 50 post(s) from this thread on one page