Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

['/usr/bin/arch-chroot', '/mnt/archinstall', 'bootctl', '--no-variables', 'install'] exited with abnormal exit code [1]: #2157

Open
emes81 opened this issue Oct 12, 2023 · 5 comments · May be fixed by #2283
Open

['/usr/bin/arch-chroot', '/mnt/archinstall', 'bootctl', '--no-variables', 'install'] exited with abnormal exit code [1]: #2157

emes81 opened this issue Oct 12, 2023 · 5 comments · May be fixed by #2283

Comments

@emes81
Copy link

emes81 commented Oct 12, 2023 •
edited

Attempting to dual boot with Windows 11 using the latest (sept 2023) Arch iso. Ran pacman -Sy archinstall before archinstall.

Manually created the following partitions:

300MB, mount point /boot, format ext4
remainder of the space (ca. 225GB), compressed, with the following subfolder structure:
@, /
@home, /home
@log, /var/log
@pkg, /var/cache/pacman/pkg
@.snapshots, /@.snapshots
install.log
@codefiles
Copy link
Contributor

Installation of systemd-boot fails because the EFI system partition (/boot) file system format is not FAT based, instead it is Ext4. The ArchWiki states to format the EFI system partition to FAT32:
https://wiki.archlinux.org/title/Installation_guide#Format_the_partitions
https://wiki.archlinux.org/title/EFI_system_partition#Format_the_partition

Validation for this condition could be added to Manual Partitioning rather than allowing the installation to run and crash at the boot loader install.

@libjared
Copy link

I hit this. It would have been nice if archinstall was smart enough to catch it. Or give a friendlier error message at any stage of the process.

@Torxed
Copy link
Member

Torxed commented Oct 18, 2023

We should be able to add this to the prerequisites validation in the menu as well as the sanity check when reading the conf before starting a installation :)

@svartkanin
Copy link
Collaborator

We can tackle that in the menu/config, I didn't find a way to actually capture the error message returned by bootctl when running it with arch-chroot as it will only return the exit code :/

@Torxed
Copy link
Member

Torxed commented Nov 23, 2023

Hmm, it should be in process._trace_log I believe.

@codefiles codefiles linked a pull request Dec 3, 2023 that will close this issue
Draft
@drewboardman drewboardman mentioned this issue Mar 30, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check for ESP if UEFI boot codefiles/archinstall
5 participants
@Torxed @libjared @codefiles @svartkanin @emes81