smth failed

[oldwizard1010]

logs files:
archiso.log
archiso2.log

[1995parham]

I am getting this issue since this morning on every system I tried. I think there is a package upgrade or something else happened. Furthermore, I think the main issue is here:

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

I tried with #2032 and #2031 with no success. Bootloader is configured on systemd-boot.

[1995parham]

@oldwizard1010 I didn't see the second issue (about user creation) can you express how did you see that? I mean, it happened after the bootloader issue, or you did another setting for installation?

The user creation issue maybe related to #2040.

[oldwizard1010]

@1995parham
second issue was added a little bit later after second attempt to install, using grub instead of systemd-boot

[1995parham]

You can see #2040 for this I think.

[einCyberSimon]

I've had this problem yesterday aswell. Seems like there is something broken in systemd.
See #2040 (I used grub and did not create an useraccount via the script, but only the root account. You then have to add your useraccount later aswell)
Apart from that you can fall back to a manual arch installation.

[1995parham]

@VelogicMusic thanks, I think we need to wait for new systemd release 😢

[oldwizard1010]

yep, this helped
#2040

[alfaroale]

The problem seems to be actually with arch-chroot. Check comment section in: https://bugs.archlinux.org/task/79619
Using systemd-nspawn instead of arch-chroot solved it. https://wiki.archlinux.org/title/systemd-nspawn
Maybe archinstall should use systemd-nspawn instead of arch-chroot.

[1995parham]

Yeah, but I think the fix will be available sooner that archinstall migration to systemd-nspawn. For now, I am waiting for 254.3 version of systemd to have my systems back 🕐

[ret2src]

I can confirm that systemd 254.3 does indeed fix the recently reported issues. If you're in a hurry and can't wait for a few days to install Arch, you can turn on the testing repos. Since this is a very dirty hack, you should definitely turn them off after the installation has succeeded, otherwise you're more likely to get broken updates in the future.

To turn on the testing repos, edit your /etc/pacman.conf (see https://joshtronic.com/2019/08/19/how-to-install-packages-from-testing-on-arch-linux/)

[Zer0Qx]

while installing archlinux freshly, enabling testing repo, did not resolve the issue. still getting it

[1995parham]

I enable testing repository on ISO and also in the installation environment, everything works as expected.

[tanjilbhuiyan]

Everything works as expected.means you successfully installed arch linux on your machine?

[ret2src]

Everything works as expected.means you successfully installed arch linux on your machine?

Yes, fresh install on a wiped disk.

[1995parham]

Yeah, for me, wipes out everything and fresh installation works.

[tanjilbhuiyan]

So i tried and it did not work for me. What i did:

1. Enable wifi
2. Pacman -Syy
3. Enable testing repo for core and extra.
4. Deleted partition using fdisk
5. Pacman -Syy
6. Archinstall

And boom failed..

Can you please tell me what exact steps you followed? Thanks in advance.

[ret2src]

@tanjilbs23

• Boot into Arch ISO from Ventoy USB (GPT, UEFI, Secure Boot)
• Connect to WiFi using iwctl
• Wipe disk with cfdisk
• Enable testing repos in /etc/pacman.conf
• $ archinstall
• Single ext4 Partition with recommended layout, no swap, LUKS encryption, single sudo user, KDE Desktop, pipewire, German mirrors, Berlin timezone

[tanjilbhuiyan]

Tried again. Almost similar to the process you mentioned. I did not disable swap. Used btrfs. Let me try your way

[tanjilbhuiyan]

@tanjilbs23

• Boot into Arch ISO from Ventoy USB (GPT, UEFI, Secure Boot)
• Connect to WiFi using iwctl
• Wipe disk with cfdisk
• Enable testing repos in /etc/pacman.conf
• $ archinstall
• Single ext4 Partition with recommended layout, no swap, LUKS encryption, single sudo user, KDE Desktop, pipewire, German mirrors, Berlin timezone

Still installing , but i am sure it worked. But i dont know why. The main difference i see.

1. I did not ran pacman -Syy
2. I disabled zram.
   3..i used ext4.
3. I used cfdisk instead fdisk.

The last time systemd version was 254.2 now it showed and installed 254.3. Why?? And how??

[tanjilbhuiyan]

Figured out. My mistake was to run : pacman -Syy command.

Other than that all we have to do is enable testing repo in iso ( before install) and additional repository ( while installing).

The most important part i think is to clear the old partition i guess.

But for now this is working.
@ret2src @1995parham

[insidesources]

I just installed successfully with all of my normal options, btrfs, encryption, adding an user, using systemd boot

I did what was said in this thread above, enabled core testing in /etc/pacman.conf and selected testing repo during the script installation. Thanks all.

[insidesources]

tested without enabling testing repos and installs successfully

[Fuhrerbaumanki]

tested without enabling testing repos and installs successfully

It turns out you just turned it on /etc/pacman.conf repository core testing and was this enough for a successful installation?

[ret2src]

tested without enabling testing repos and installs successfully

It turns out you just turned it on /etc/pacman.conf repository core testing and was this enough for a successful installation?

You probably no longer need testing as the new systemd version is in the normal repos since yesterday: https://archlinux.org/packages/core/x86_64/systemd/

[svartkanin]

This is not related to archinstall #2040 (comment)