Troubleshooting

Helping us help you

Log files are available in ./archinstoo/logs/* relative to where you ran.

These contain 4 files: cmd_history.txt, cmd_output.txt and install.log (+ your user_configuration.json) Depending on the issue all 4 can be useful.

If you do not want to open a public issue feel free to contact directly: hadean-eon-dev@proton.me

Known issues

Issues with dependencies

Arch's ISO is built 1st of each month.

Using the latest version is often safer bet.

Check:

. ./PKGBUILD && pacman -Qu "${depends[@]}"
# or the same with "${optdepends[@]}"

Update:

. ./PKGBUILD && pacman -Sy --needed "${depends[@]}"
# or the same with "${optdepends[@]}"

For the lazy ones: ./DEV -h2t or with optionals ./DEV -h2t -o

Important

Do also note that the ISO has limited cow_space, running any form of -Syu or updating packages can trigger space errors/or read-only hook issues/or partial updates,

and needs to be rebuilt with more space for certain breaking updates.

Usually build a 1GB ISO to test dev builds (vs the original 256M). And can be released more frequently.

You can also do this by running mount -o remount,size=1G /run/archiso/cowspace on the ISO directly.

See ISOs to create custom ones directly.

Issues with signatures/keyring

Check system BIOS clock / timezone

killall gpg-agent
rm -rf /etc/pacman.d/gnupg
pacman-key --init
pacman-key --populate
pacman -Sy archlinux-keyring

Then run archinstoo Back to Step 1

https://github.com/archlinux/archinstall/issues/4018 https://github.com/archlinux/archinstall/issues/2213

---