You are not logged in.
Hello Guys,
This is my first topic. I have done all the research in this forum and in Google for the issue, with no luck in finding a solution. I have done several Arch linux installs before on Virtual Machines and PC's all of them working properly, except for this one that I can not get to pass the install phase.
Description of Hardware:
HP Laptop Pavilion Entertainment PC dv2-1030us
Athlon AMD Processor
4 GB RAM
300GB HD
ATI Video Card
Broadcom wireless Card (Default drivers Not Working)
Wired Network Card (Working)
I'm trying to install Arch from USB drive created from another arch machine via:
sudo dd if=/name_of_file.iso of=/dev/sdX
Using Arch Version:
Current Release: 2014.08.01
Included Kernel: 3.15.7
ISO Size: 559.0 MB
The above bootleable USB drive have been used to install Arch in another machine currently running it.
After creating the partitions on the drive, namely:
BOOT
SWAP
ROOT
HOME
And formatting them accordingly to the install guide, and having the system ready to download all the base and base-devel packages via:
pacstrap -i /mnt base base-devel
Right after it finishes downloading I get the following error:
downloading required keys in keyring...
:: Import PGP key 4096R/753E0F1F, "Anatol Pomozov <anatol.pomozov@gmail.com>", created: 2014-02-04? [Y/n] y
error: key "Anatol Pomozov <anatol.pomozov@gmail.com>" could not be imported
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were installed.
==> ERROR: Failed to install packages to new root
I first ignored the error and then tried to proceed with the installation process and executed the following sequences of commands:
genfstab -U -p /mnt >> /mnt/etc/fstab
and then tried to chroot with:
arch-chroot /mnt
Then i got the following error:
mount: mount point /mnt/etc/resolv.conf does not exist
chroot: failed to run command "/bin/sh": No such file or directory
Here is list of the Topics i Found in this forum that throw some light into the issue, some of the solutions I have tried with no luck at all:
I hope you can help find a direction where to start fixing this issue, since i feel pretty lost right now. By the way I'm a Newbie in the Arch Linux world, so there are a lot of thing that are not that obvious to me...
Thank you in advance.
Last edited by alejandroccs (2014-08-20 21:12:13)
Offline
Offline
Slithery,
I'm sorry, I forgot to point that out in the first place; I'm currently using the following version of Arch Linux:
Current Release: 2014.08.01
Included Kernel: 3.15.7
ISO Size: 559.0 MB
Offline
Is partions mounted (root,swap,root,home)
Offline
Pekka,
All partitions are formated and mounted using the following commands:
SWAP
# mkswap /dev/sda2
# swapon /dev/sda2
ROOT
# mkfs.ext4 /dev/sda3
HOME
# mkfs.ext4 /dev/sda4
MOUNTING ROOT
# mount /dev/sda3 /mnt
CREATING HOME
# mkdir /mnt/home
MOUNTING HOME
# mount /dev/sda4 /mnt/home
Offline
I've had the same issue with an (outdated) Arch Linux iso. As far as I am aware, it is caused by pacman's keys becoming out of date.
I've managed to get around this before, but the exact method eludes me.
You could try just updating the archlinux-keyring package, by refreshing pacman (pacman -Sy), then reinstalling only that package (try pacman -S archlinux-keyring).
Then you should be able to continue as normal.
Note that this only affects the CD filesystem in RAM - it will not persists across reboots using the CD.
The reason why this might work is that the package archlinux-keyring might not be signed by the key you were having issues with. If it still fails, you could temporarily set the SigLevel for the core repo to 'Never', however this does disable package signing, at least until you reset the SigLevel.
Unfortunately, I could not replicate the problem in a Qemu VM, so I'm not sure how good my method is. Hopefully, it fixes the problem.
Here are some links that might help shed some light:
http://calvinx.com/category/unix-linux/archlinux/
https://wiki.archlinux.org/index.php/Pacman-key
Hopefully this is helpful!
pypi
Offline
Pypi,
Thank you for your response, what you said I did it before since is on one of the solutions I previously found in the forum; however your phrase ending in:
..."becoming out of date."
Is what got into my head and finally help me find the solution to this issue. What happened is actually really simple, this is an old laptop I had around in my house, but I never got into the BIOS of the machine, when a I did early today I found out that the BIOS time was way back, actually January 01, 1970 which was causing the PGP Key "becoming out of date" because it was comparing the time from the file itself and my machine, and since my hardware was back in time it could not install the Key at all because the PGP Key date signature appears to be ahead of time.
So if by chance you find getting the same errors stated above in a fresh install we have to check our hardware Date and Time to verify everything is ok.
This issue is Solved.
Thank for all of you who tried to help me, I really appreciate it.
Offline
Glad to be of service, if not quite in the way I intended!
That it was caused by date and time surprises me, since I had the problem while installing to a disk attached to my (Arch Linux) PC, for another computer.
Oh well; I will remember this (hopefully) when I run into the problem next time!
I looked at the first two linked topics... but not the third. <smack head>
Offline