oz wrote:
The installer image got broken some time ago because of this. It started when the ISO image was switched to loading itself in to RAM before running. In the installation guide step «1.8 Update the system clock» it is CRITICALLY important, which is not mentioned. I mean if that’s not working then you MUST stop and get it working before continuing.
If it fails to activate NTP then pacman-init will never run. There is no message or hint that something is wrong but any attempt to use pacman will get weird signature, keyring, etc errors. Those aren’t the real problem. The real problem is that NTP hasn’t initialized (and in turn pacman-init). There really should be messages that describe the problem.
This can also be a problem on machines that have network access but not Internet access. The system gets confused.
Also, it’s really difficult to work while in the install image because there is no space to install more packages in the installer environment.
All of this used to work. The old system was better.
Thanks!
I just had pacstrap to fail during the installation of Arch Linux through a recently downloaded, fresh ISO and ended up in this thread.
After reading the reply above, I ran
and got «System clock synchronized: no». This raised a red flag. Then I ran
$ systemctl status pacman-init.serviceand it was dead. This raised another red flag.
I started looking up for services related to time synchronization, and found «systemd-timesyncd.service». I ran
$ systemctl status systemd-timesyncd.serviceand the output showed that it was timing out while trying to connect to some kind of public NTP server. It turns out that there is a file «/etc/systemd/timesyncd.conf» where this can be configured. I edited it and saved it like this:
[Time]
NTP=0.arch.pool.ntp.org 1.arch.pool.ntp.org 2.arch.pool.ntp.org 3.arch.pool.ntp.org
FallbackNTP=0.arch.pool.ntp.org 1.arch.pool.ntp.org 2.arch.pool.ntp.org 3.arch.pool.ntp.orgBasically, I just copied what was into FallbackNTP= to NTP= and uncommented those lines (other lines left commented).
After that, I restarted the service:
$ systemctl restart systemd-timesyncd.serviceFinally, running
gave me «System clock synchronized: yes»; and running
$ systemctl status pacman-init.servicetold me the service was active.
And now pacstrap worked.
@mfgbhatti Thanks for the help. It did not resolve it but it helpful to get more insight into more errors.
For me:
pacman -Syu
keyring not writeable
pacman-key --init
ERROR: Trust database could be be updated
pacman-key --populate
Could not be locally signed
I consider arch broken at the moment (March ISO).
I think that the install terminal for arch runs in a very restricted read-only mode.
I’ll try again in three months and see how it’s changed.
Loading
Перейти к контенту
oz wrote:
The installer image got broken some time ago because of this. It started when the ISO image was switched to loading itself in to RAM before running. In the installation guide step «1.8 Update the system clock» it is CRITICALLY important, which is not mentioned. I mean if that’s not working then you MUST stop and get it working before continuing.
If it fails to activate NTP then pacman-init will never run. There is no message or hint that something is wrong but any attempt to use pacman will get weird signature, keyring, etc errors. Those aren’t the real problem. The real problem is that NTP hasn’t initialized (and in turn pacman-init). There really should be messages that describe the problem.
This can also be a problem on machines that have network access but not Internet access. The system gets confused.
Also, it’s really difficult to work while in the install image because there is no space to install more packages in the installer environment.
All of this used to work. The old system was better.
Thanks!
I just had pacstrap to fail during the installation of Arch Linux through a recently downloaded, fresh ISO and ended up in this thread.
After reading the reply above, I ran
and got «System clock synchronized: no». This raised a red flag. Then I ran
$ systemctl status pacman-init.serviceand it was dead. This raised another red flag.
I started looking up for services related to time synchronization, and found «systemd-timesyncd.service». I ran
$ systemctl status systemd-timesyncd.serviceand the output showed that it was timing out while trying to connect to some kind of public NTP server. It turns out that there is a file «/etc/systemd/timesyncd.conf» where this can be configured. I edited it and saved it like this:
[Time]
NTP=0.arch.pool.ntp.org 1.arch.pool.ntp.org 2.arch.pool.ntp.org 3.arch.pool.ntp.org
FallbackNTP=0.arch.pool.ntp.org 1.arch.pool.ntp.org 2.arch.pool.ntp.org 3.arch.pool.ntp.orgBasically, I just copied what was into FallbackNTP= to NTP= and uncommented those lines (other lines left commented).
After that, I restarted the service:
$ systemctl restart systemd-timesyncd.serviceFinally, running
gave me «System clock synchronized: yes»; and running
$ systemctl status pacman-init.servicetold me the service was active.
And now pacstrap worked.
@mfgbhatti Thanks for the help. It did not resolve it but it helpful to get more insight into more errors.
For me:
pacman -Syu
keyring not writeable
pacman-key --init
ERROR: Trust database could be be updated
pacman-key --populate
Could not be locally signed
I consider arch broken at the moment (March ISO).
I think that the install terminal for arch runs in a very restricted read-only mode.
I’ll try again in three months and see how it’s changed.
0
0
Я установил manjaro, зашёл в add/remove software или же мененджер установок, он скачал пакеты, а установить или собрать не смог.
Захожу в консоль, чтобы обновить с неё, пишу sudo pacman -Syyu,
он тоже что-то качает, а потом предлагает что-то удалить:
:: File /var/cache/pacman/pkg/manjaro-keyring-20220514-2-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
После чего, независимо от выбора он качает все остальные программы, которые должны обновиться, затем он каждый пакет, закаченый до этого предлагает удалить.
И так можно по кругу, скачивать и удалять. Я так удалял и скачивал, пока не осознал, что интернет не бесконечный и что что-то не так.
Я уже пробовал:
sudo pacman -S pacman-mirrors (так в каком-то другом форуме пытались решить проблему, но мне не помогло).
sudo pacman-mirrors -di (там можно протыкать зеркала, которые наравятся и подтвердить выбор) после чего писал судо пакман суй, но он не сувал.
sudo pacman-mirrors -f0 показывает что с вязь с некоторыми зеркалами есть.
в менеджере пакетов я также включил поддержку всего: аура, флатпака, снапа. Перезагружал разумеется.
До этого я устанавливал с этой же флешки manjaro на тот же компютер и всё работало (в этот раз я не создавал home, а воспользовался стереть диск и установить на него, так как отдельный раздел под home я посчитал ненужным).
Get the Reddit app
Scan this QR code to download the app now
Or check it out in the app stores
Hi all, I’m looking for a modern distro for my Vortex86EX board, which lacks CMOV* instructions (i.e. i586).
Much to my surprise, there is still a well-maintained i486 fork after Arch Linux dropped i686 support for years.
Thanks to everyone who has supported this great project!
I downloaded the latest i486 snapshot archlinux32-2021.07.16-i486.iso to test it in QEMU, and the live CD booted smoothly on an emulated 486DX.
However, the pacstrap process was not straightforward:
# pacstrap /mnt base linux
=> Creating install root at /mnt
=> Installing packages to /mnt
...
(113/113) checking keys in keyring
downloading required keys...
error: keyring is not writable
error: keyring is not writable
error: required key is missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
=> ERROR: Failed to install packages to new rootAfter some trail and error, I managed to workaround the readonly iso9660 filesystem with an overlayfs:
# mkdir /tmp/upperdir /tmp/workdir
# mount -t overlay overlay -o lowerdir=/etc/pacman.d/gnupg,upperdir=/tmp/upperdir,workdir=/tmp/workdir /etc/pacman.d/gnupg
# pacstrap /mnt base linuxI once installed the (upstream amd64) Arch Linux on my PC with the live CD, and did not meet similar problems.
I’m still feeling puzzled. Could this be an archlinux32-specific issue?
Last edited by Arnie97 (2021-11-25 20:10:32)