I will do it!
Though I wonder how come it can be corrupted after installation, put in box, taking it 3 weeks later to install again!
OK. I will download, format the flash disk, install the ISO.
also compare the sum of the ISO, if they are not the same, the ISO is not OK.
All what I can say… I am just an unlucky guy!
Again, but let me say this time I am lucky that I am all the time learning something new and gaining more experiences!
Though it is a challenge for me to understand how the live session is working… how the flash disk got corrupted while kept in a drawer!
As I always say it is EndeavourOS University!
I keep learning all the time.
Will reboot to installed system as I could not install a torrent client
error: failed retrieving file 'python-pillow-9.1.1-1-x86_64.pkg.tar.zst' from mirror.f4st.host : The requested URL returned error: 404
error: failed retrieving file 'deluge-1:2.0.5-1-any.pkg.tar.zst' from mirror.f4st.host : The requested URL returned error: 404
error: failed retrieving file 'python-cryptography-37.0.2-1-x86_64.pkg.tar.zst' from mirror.f4st.host : The requested URL returned error: 404
warning: too many errors from mirror.f4st.host, skipping for the remainder of this transaction
error: failed retrieving file 'libtorrent-rasterbar-1:2.0.6-2-x86_64.pkg.tar.zst' from mirror.f4st.host : The requested URL returned error: 404
I wonder how do I get 404?
Rebooting!
The same reason as above. You can’t just launch the ISO and start installing software
The database on the ISO is too old at this point.
If you want to install software on the ISO use pacman -Sy packagename
Mirror
mirror.f4st.host
has a (temporary?) problem.
You can edit file /etc/pacman.d/mirrorlist and comment out that mirror (by adding a # character as the first character on that particular line).
There is also zero reason to update anything while running the lives session. The ISO is a snapshot of tested to work as it is. Where online install will I stall latest versions of everything fresh from the net. And offline will use the image from iso to create the system.
Updating iso Live-Session will only do one thing: creating more issues.
As usual… as I am having a question in my mind… I keep thinking and reading trying to find an answer!
The only thing that came to my mind that as @dalto said it may be corrupted while being stored or read during booting the live session is that it is initially a very low quality “promotional” flash disk distributed for free with a company logo. Actually it has a company logo… a company that I can’t even remember… it does not even show anywhere even the size of the flash disk… allover outside is absolutely blank!
2 Likes
Downloaded ISO through Ktorrent.
Just in case, trying to follow the instructions
I get:
[limo@limo ~]$ sha512sum -c EndeavourOS_Artemis-22_6.iso.sha512sum
sha512sum: EndeavourOS_Artemis-22_6.iso.sha512sum: No such file or directory
and
[limo@limo ~]$ gpg --verify EndeavourOS_Artemis-22_6.iso
gpg: WARNING: unsafe permissions on homedir '/home/limo/.gnupg'
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified.
Please remember that the signature file (.sig or .asc)
should be the first file given on the command line.
How is that?
BUT from the forum here I found “sha1sum”
[limo@limo ~]$ sha1sum EndeavourOS_Artemis-22_6.iso
374400741f9cf7c5d8486b3789b1395c795c0162 EndeavourOS_Artemis-22_6.iso
[limo@limo ~]$
It looks like you didn’t download the sha512 sum file. You need to do that separately.
Likewise, did you download the gpg sig file?
I just did!
What next?
[limo@limo ~]$ gpg --verify EndeavourOS_Artemis-22_6.iso.sig
gpg: WARNING: unsafe permissions on homedir '/home/limo/.gnupg'
gpg: assuming signed data in 'EndeavourOS_Artemis-22_6.iso'
gpg: Signature made Thu Jun 23 20:31:01 2022 EET
gpg: using RSA key 8F43FC374CD4CEEA19CEE323E3D8752ACDF595A1
gpg: issuer "joekamprad@endeavouros.com"
gpg: Can't check signature: No public key
[limo@limo ~]$
Re-run those commands that failed from the directory that contains the files and the iso.
[limo@limo ~]$ sha512sum -c EndeavourOS_Artemis-22_6.iso.sha512sum
EndeavourOS_Artemis-22_6.iso: OK
Trying to do the rest of instruction… Will update you
[limo@limo ~]$ gpg --recv-keys CDF595A1
gpg: WARNING: unsafe permissions on homedir '/home/limo/.gnupg'
gpg: key E3D8752ACDF595A1: "Johannes Kamprad (joekamprad development key) <joekamprad@endeavouros.com>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
[limo@limo ~]$
[limo@limo ~]$ gpg --edit-key CDF595A1
gpg: WARNING: unsafe permissions on homedir '/home/limo/.gnupg'
gpg (GnuPG) 2.2.36; Copyright (C) 2022 g10 Code GmbH
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
pub rsa2048/E3D8752ACDF595A1
created: 2021-02-03 expires: never usage: SC
trust: unknown validity: unknown
sub rsa2048/9980FA8E52E66CA8
created: 2021-02-03 expires: never usage: E
[ unknown] (1). Johannes Kamprad (joekamprad development key) <joekamprad@endeavouros.com>
[ unknown] (2) [jpeg image of size 3520]
gpg>
pub rsa2048/E3D8752ACDF595A1
created: 2021-02-03 expires: never usage: SC
trust: unknown validity: unknown
sub rsa2048/9980FA8E52E66CA8
created: 2021-02-03 expires: never usage: E
[ unknown] (1). Johannes Kamprad (joekamprad development key) <joekamprad@endeavouros.com>
[ unknown] (2) [jpeg image of size 3520]
gpg>
pub rsa2048/E3D8752ACDF595A1
created: 2021-02-03 expires: never usage: SC
trust: unknown validity: unknown
sub rsa2048/9980FA8E52E66CA8
created: 2021-02-03 expires: never usage: E
[ unknown] (1). Johannes Kamprad (joekamprad development key) <joekamprad@endeavouros.com>
[ unknown] (2) [jpeg image of size 3520]
gpg>
pub rsa2048/E3D8752ACDF595A1
created: 2021-02-03 expires: never usage: SC
trust: unknown validity: unknown
sub rsa2048/9980FA8E52E66CA8
created: 2021-02-03 expires: never usage: E
[ unknown] (1). Johannes Kamprad (joekamprad development key) <joekamprad@endeavouros.com>
[ unknown] (2) [jpeg image of size 3520]
gpg>
pub rsa2048/E3D8752ACDF595A1
created: 2021-02-03 expires: never usage: SC
trust: unknown validity: unknown
sub rsa2048/9980FA8E52E66CA8
created: 2021-02-03 expires: never usage: E
[ unknown] (1). Johannes Kamprad (joekamprad development key) <joekamprad@endeavouros.com>
[ unknown] (2) [jpeg image of size 3520]
gpg>
pub rsa2048/E3D8752ACDF595A1
created: 2021-02-03 expires: never usage: SC
trust: unknown validity: unknown
sub rsa2048/9980FA8E52E66CA8
created: 2021-02-03 expires: never usage: E
[ unknown] (1). Johannes Kamprad (joekamprad development key) <joekamprad@endeavouros.com>
[ unknown] (2) [jpeg image of size 3520]
gpg>
pub rsa2048/E3D8752ACDF595A1
created: 2021-02-03 expires: never usage: SC
trust: unknown validity: unknown
sub rsa2048/9980FA8E52E66CA8
created: 2021-02-03 expires: never usage: E
[ unknown] (1). Johannes Kamprad (joekamprad development key) <joekamprad@endeavouros.com>
[ unknown] (2) [jpeg image of size 3520]
gpg>
What should I enter at the gpg> prompt?
Or perhaps this is enough to trust the ISO is OK? (downloaded by torrent anyway and passed a test above)
Hopefully I can proceed and “dd” the image to the flash disk?
To fix the " gpg: WARNING:
chown -R limo ~/.gnupg/
Also correct the permissions and access rights on the directory:
chmod 600 ~/.gnupg/*
chmod 700 ~/.gnupg
You should be ready to go (after fixing the above error).
Yes. You are ready to move forward.
1 Like
Just to be sure and avoid any stupid thing I can do (as usual)
I have now
[limo@limo ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 300M 0 part /boot/efi
└─sda2 8:2 0 232.6G 0 part /
sdb 8:16 1 0B 0 disk
sdc 8:32 1 29.3G 0 disk
sr0 11:0 1 1024M 0 rom
Is this OK? I got it from Arch Linux Wiki
Should I press enter for
sudo dd bs=4M if=/home/limo/EndeavourOS_Artemis-22_6.iso of=/dev/sdc1 conv=fsync oflag=direct status=progress
It should probably be /dev/sdc, not /dev/sdc1 assuming that is the correct device.
Hopefully! You see I always encounter a few things I can’t understand (like a corrupted flash disc, or inaccessible BIOS… etc.)
Yes… my bad! Sorry.
That’s why I prefer to double check!
Greatings from my Brand New EndeavourOS, BTRFS, KDE Plasma
The first thing I do (after updating mirors and updating system through "welcome) is to say thank you, thank you, thank you, thank you,
And special thanks to everybody who contributed to the thread about best search engine that has no problems with BTRFS.
Simply, you all made my dream of BTRFS come true!
All of you guys are wonderful. Thank you forever.
3 Likes