Online install failure, initial update problem

I was trying to install EOS using the 9/2024 ISO online. The disk was partitioned as
500MB FAT32, boot flag, /boot/efi
8MB unformatted, grub_bios
300 GB ext4, /
630 GB ext4, /home
Selected vanilla XFCE
I had recently (3 weeks ago) did an online install on a 500GB with the same partitioning but Cinnamon that worked fine.

This time, it aborted with “failed to run command ‘systemd-machine-id-setup’: No such file or directory.”

Full Log for the online install : https://termbin.com/z3lr

So I installed offline with XFCE and it installed OK. But when I used Update System on the Welcome page after booting into the new install, the update started OK then gave me a boatload of prompts for importing PGP keys, to which I said “Yes”, Then the update started, and barfed all over everything with PGP signature errors. I then ran keyring updates manually. The Arch keyring udpated OK, but the EOS keyriing update barfed, to wit:
---- Begin terminal output —
[~]$ update_keyring
[sudo] password :
:: Synchronizing package databases…
core is up to date
extra is up to date
community is up to date
multilib is up to date
endeavouros is up to date
resolving dependencies…
looking for conflicting packages…

Package (1) Old Version New Version Net Change

core/archlinux-keyring 20211028-1 20241203-1 0.32 MiB

Total Installed Size: 1.67 MiB
Net Upgrade Size: 0.32 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring [--------------------------------] 100%
(1/1) checking package integrity [--------------------------------] 100%
(1/1) loading package files [--------------------------------] 100%
(1/1) checking for file conflicts [--------------------------------] 100%
:: Processing package changes…
(1/1) upgrading archlinux-keyring [--------------------------------] 100%
==> Appending keys from archlinux.gpg…
==> Locally signing trusted keys in keyring…
→ Locally signed 2 keys.
==> Importing owner trust values…
gpg: inserting ownertrust of 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring…
→ Disabled 24 keys.
==> Updating trust database…
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 6 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 6 signed: 101 trust: 1-, 0q, 0n, 5m, 0f, 0u
gpg: depth: 2 valid: 77 signed: 28 trust: 77-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2025-01-01
:: Running post-transaction hooks…
(1/3) Reloading system manager configuration…
(2/3) Arming ConditionNeedsUpdate…
(3/3) Checking which packages need to be rebuilt
[~]$ update_eos_keyring
:: Synchronizing package databases…
core is up to date
extra is up to date
community is up to date
multilib is up to date
endeavouros is up to date
resolving dependencies…
looking for conflicting packages…

Package (1) Old Version New Version Net Change

endeavouros/endeavouros-keyring 1-5 20231222-1 0.01 MiB

Total Installed Size: 0.01 MiB
Net Upgrade Size: 0.01 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring [--------------------------------] 100%
(1/1) checking package integrity [--------------------------------] 100%
error: endeavouros-keyring: signature from “manuel manuel@endeavouros.com” is unknown trust
:: File /var/cache/pacman/pkg/endeavouros-keyring-20231222-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] Y
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

You appear to be using a very old ISO. Not the one from 9/24.

Please double check that you are really using the most recent ISO.

1 Like

@#(&%^#&(^@&*)&#()QW&^(T^@#!!@#&^Q#()74908237891!!!

I beg permission to commit seppuku.

6 Likes

=== START CALAMARES 3.2.49.1 thats old…
Seppuku has been banned since 1868.
How you do download the ISO anyway?
May simply using ventoy and taking the wrong one to boot?

i see also some unclear info:


first thing ( 500 MB fat32, boot-flag on /boot/efi) is good in case using Grub and on a modern efi enabled system…
second does not make sense on such system in addition thats for old Bios systems or modern efi systems running in Bios/legacy/CSM mode with a gpt parttition scheme used. But even if ,not together on the same install.

Nowhere near that complicated. Used an old ISO instead of the latest which I already had.