Error failed to install package to new root
Предупреждение не удалось получить некоторые файлы
Расскажи, как и куда ты пакеты ставишь. Может, места нет, например. И на каком пакете обрывается? Он всегда один, или рандомно?
post-factum
(11.09.16 12:43:40 MSK)
Что делать ?
Я где-то неделю назад смотрел на арчёвый лайв-исо и он был безнадёжно стар, по сравнению с репами. Поэтому я тебе порекомендую перед установкой выполнить pacman -Syu.
anonymous
(11.09.16 18:15:41 MSK)
radg
(11.09.16 23:34:11 MSK)
Последнее исправление: radg 11.09.16 23:34:53 MSK
(всего
исправлений: 1)
Спасибо всем. Просто начал установку заново и все пошло как надо.
Ваннгую что дело было в нестабильном инете.
temakonkin
(12.09.16 08:48:30 MSK)
- Похожие темы
- #4 2016-08-13 05
- #5 2019-05-03 03
- Arch Linux
- #4 2019-03-27 22
- #3 2016-07-29 19
- #2 2016-07-29 17
- #5 2016-08-14 19
- #3 2014-06-14 15
- #3 2019-03-27 22
- #2 2017-04-08 14
- #2 2019-03-27 22
- #5 2017-04-08 14
- #3 2017-04-08 14
- #2 2014-06-14 15
- #1 2017-04-08 13
- [SOLVED] failed to install packages to new root
- #1 2014-06-14 14
- #1 2019-03-27 22
- #1 2016-07-29 17
Похожие темы
I recently decided to try out Arch Linux, but I am having problems installing the base and base-devel packages. First, here are my partitions:
sda2 home 350GB (ext4)
sda4 root 30GB (ext4)
sda3 boot 7GB (fat32)
I figured I didn’t need a swap partition yet, cause I have 6GB of RAM, which I assume is enough to install Arch. The boot partition is larger than normal because I have ~35GB free space, and based on my research, some were saying that the boot partition was too small.
Then, after setting the server mirror and mounting the partitions, I synchronized the package databases just to be sure:
And here is where I encountered the first problem. When executing pacstrap -i /mnt base base-devel and selecting all packages, I got these warnings:
warning: skipping target: file
warning: skipping target: fileutils
warning: skipping target: gawk
warning: skipping target: gettext
warning: skipping target: grep
warning: skipping target: gzip
warning: skipping target: pacman
warning: skipping target: sed
warning: skipping target: texinfo
warning: skipping target: util-linux
warning: skipping target: which
None of the solutions I have found work, and I am not sure how to continue. I have done the process a few times, but the problem seems to happen each time. Any help would be greatly appreciated. If you have any questions, feel free to comment!
Edit: Yup, I do have internet connection.
Fri Jul 06, 2018 8:08 am
That is exactly what we need.
1. your work directory must be deleted.
sudo rm -rf ..
2. failed retrieving file
do a «mirror» and «sudo pacman -Syyu» in terminal
3. do not put applications from AUR in packages.both
error: target not found: curseradio-git
error: target not found: discord
error: target not found: slack-desktop
error: target not found: spotify
error: target not found: workflowy
error: target not found: xcursor-neutral++
error: target not found: anydesk
error: target not found: openvpn-nordvpn
error: target not found: backintime
error: target not found: bitwarden
error: target not found: megasync
Use a script to get those in later after installation.
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.
Fri Jul 06, 2018 3:07 pm
erikdubois wrote: ↑Fri Jul 06, 2018 8:08 am
That is exactly what we need.
Thank you for this—I think I’m almost there, but am now getting this error:
Fri Jul 06, 2018 4:14 pm
Fri Jul 06, 2018 5:01 pm
Sat Jul 07, 2018 7:27 am
have fun figuring out what you do need.
Make a new topic for your next issue
marking this as solved
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.
First of all, this is not your inability to install arch, if your iso is from a couple of months ago, you probably have a bad GPG database, and because of that you have that problem.
The fastest way is to download the most recent ISO since the problem is solved by now.
On the other hand, you can try this
sudo pacman -S archlinux-keyring
The output should be something like:
After that run one more time:
after that you can run again the
pacstrap /mnt base
Closing since the issue appears to be fixed in 1.0.9.
#4 2016-08-13 05
then, re pacstrap your system.
See if this works.
Last edited by Elizine (2016-08-13 05:33:55)
#5 2019-05-03 03
The referenced post seemed to solve the issue by formatting their partition as ext2 rather than FAT 32, however I am trying to install on a UEFI system and I was under the impression that FAT 32 was required for your EFI partition, so I am in a bit of a catch 22. I also tried updating my keyring with:
If the issue is as the referenced post hypothesized, and that something about the packages doesn’t cooperate with FAT 32, are there other file systems I could try ? If not, I am unsure of how to proceed.
Any help would be greatly appreciated. Thanks !
An image of my screen after pacstrap downloads everything and tries to install: (Apologies for less than ideal quality.)
Could you just walk us through each step you’ve taken so far in your install in regards to the important parts at least? Like formatting partitions, mounting, and so forth.
Arch Linux
You are not logged in.
#4 2019-03-27 22
corrupted pkgs and device errors prbly point to problems with USB device
#3 2016-07-29 19
Are you trying to dual boot with another linux distro that’s sharing the same /boot partition?
#2 2016-07-29 17
Why is it there?
#5 2016-08-14 19
I agree. If you’ve installed another distro prior to Arch, and you want overwrite its data footprint; make sure you remove the kernels files from that distros boot directory prior to installation.
#3 2014-06-14 15
Thank you vefy much, it solved the problem
You do not need to leave your room. Remain sitting at your table and listen.Do not even listen, simply wait, be quiet, still and solitary.The world will freely offer itself to you to be unmasked, it has no choice, it will roll in ecstasy at your feet. Franz Kafka
#3 2019-03-27 22
Right so I’ve got a FAT 32 formatted /dev/sda1 as the boot partition, swap space as /dev/sda2, and an ext4 formatted /dev/sda3 root partition. Is that correct ?
#2 2017-04-08 14
You should really use an up-to-date installation iso, but if that isn’t possible, you might be able to get by by updating the archlinux-keyring package in the live environment before running pacstrap.
‘ in this case is a special time thing, you should not use it in an installed system as it will lead to partial updates which are not supported.
Making lemonade from lemons since 2015.
#2 2019-03-27 22
Your /boot can be FAT32, not your / partition.
#5 2017-04-08 14
No, the «corrupt packages» were just due to using an old iso with an outdated keyring — they aren’t stored on the usb anyways, so a usb hardware issue would not lead to those symptoms. The second error is quite common, and usually a result of using something other than dd to create the live usb.
«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman
#3 2017-04-08 14
Thank you so much! It worked like a charm!However, I wonder why the newest ISO wouldn’t work on the device;As in, it would always output something like:
ERROR: ‘/dev/disk/by-label/ARCH_201704’ device did not show up after 30 seconds. Falling back to interactive prompt You can try to fix the problem manually, log out when you are finished sh: can’t access tty: job control turned off
#2 2014-06-14 15
Last edited by karol (2014-06-14 15:10:10)
#1 2017-04-08 13
I’m trying to install ArchWhenever I go through with installing the base packages (pacstrap -i /mnt base base-devel), I keep getting this:
Also, it should probably be noted that I’m doing this off of a Live USB running a version of Arch from last year (2016_03)I’ve tried using a newer ISO, thinking that the packages were outdated, but I wasn’t able to boot from it (archlinux-2017.04.01-x86_64)(I’m using YUMI to create Live USB’s)
What should I do?
[SOLVED] failed to install packages to new root
I have done a few successful ArcoLinuxD installs in the past, but wanted to give ArcoLinuxB a try this time. My goal is to build an iso with xfce and openbox (no i3). I have edited the packages.both file (adding what I want, and commenting out what I do not). When I try to run script 30 to build the iso, I keep getting this. ERROR: Failed to install packages to new root. Any idea what I’m doing wrong?
Give us more code lines — at least 30 lines before the actual error.
Here is how you can help us to help you
erikdubois wrote: ↑ Thu Jul 05, 2018 7:32 pm Give us more code lines — at least 30 lines before the actual error.
1. your work directory must be deleted. sudo rm -rf ..
2. failed retrieving file do a «mirror» and «sudo pacman -Syyu» in terminal
error: target not found: curseradio-git error: target not found: discord error: target not found: slack-desktop error: target not found: spotify error: target not found: workflowy error: target not found: xcursor-neutral++ error: target not found: anydesk error: target not found: openvpn-nordvpn error: target not found: backintime error: target not found: bitwarden error: target not found: megasync
erikdubois wrote: ↑ Fri Jul 06, 2018 8:08 am That is exactly what we need.
Thank you for this—I think I’m almost there, but am now getting this error:
#1 2014-06-14 14
HiI am reinstalling Arch. The image that I use from usb is coulple month old. I am trying to ceep my old /home partition, so I just mounted the old /home partition to the new file system. The root partition is new, after mkfs.ext4.After choosing a mirror and running
all the packages ware downloaded and it continued to the installation. Then the output was
but it didnt help. I check the time, and it seems to be O.K.
thanks for reading.
Last edited by Yashka (2014-06-14 17:41:28)
#1 2019-03-27 22
Linux made easy and beautiful
#1 2016-07-29 17
Hey,i have a problem.When i use pacstrap /mnt base apear error .»/mnt/boot/vmlinuz-linux exists in filesystem» How i can fix it?