#Failed arch install with archinstall

1 messages · Page 1 of 1 (latest)

sharp rock
#

I have no idea what this means
can anyone help?

midnight falcon
#

i got the same issue too

frigid dew
#

Same. Seems to be a recent issue

sharp rock
#

I'm trying to use grub

frigid dew
#

Boot into archiso.
Update archinstall using pacman -Sy and pacman -S archinstall.
Then run these commands to find the path to the installer.py:
cd /find . | grep archinstall | grep installer.py
For me, as for MythSniper, the path was
/usr/lib/python3.13/site-packages/archinstall/lib/installer.py
4. Find the installer.py and open it using any text editor
5. Go to the section where the error message was being raised (you can search by "Unable to start service")
6. Change the following section:

try:
self.arch_chroot(f'systemctl enable {service}')
except SysCallError as err:
raise SeviceException(f'Unable to start service {service}: {err}')
to the following:

try:
SysCommand(f'systemctl --root={self.target} enable {service}')
except SysCallError as err:
raise SeviceException(f'Unable to start service {service}: {err}')
Initiate the installation as usual.
At least for me, it worked fine after this. (note that it's just a quick fix

frigid dew
#

I did this command before running the archinstall:

sed -i 's/self.arch_chroot(f.systemctl enable {service}.)/SysCommand(f"systemctl --root={self.target} enable {service}")/' /usr/lib/python3.13/site-packages/archinstall/lib/installer.py

and it worked for me

tranquil shoal
# frigid dew Same. Seems to be a recent issue

It actually isn't
I am a contributor and watcher of archinstall
And archinstall was updated on september 2nd
But all the problems with sd happened yesterday
And some people were saying that it is a pacstrap issue