You are not logged in.
hello,
The day before yesterday I tried to reinstall my arch by using my own installation script.
I've successfully used this script many times before, but now for some reason I got issues while downloading certain packages.
The problem appeared during the 'chroot process'.
Normally I use reflector to get the latest mirrors, here's a part of my script:
# 7 Retrieve latest mirrors and update mirrorlist
echo ":: Updating mirrorlist..."
yes | pacman -S reflector --noconfirm
reflector --verbose --latest 5 --sort rate --save /etc/pacman.d/mirrorlist
Although I used reflector, I still got errors like these:
error: failed retrieving file 'xxx' from xx : The requested URL returned error: 404
error: failed retrieving file 'xxx' from xx : Protocol "rsync" not supported or disabled in libcurl
In the end my grub installation was corrupted...
The strange thing is, the day afterwards I tried to reinstall arch and everything worked again! I did not change anything in the script.
So my questions are the following:
- why did reflector not see these issues for the respective mirrors
- is there a way in my script to catch any errors from pacman so I can deal with them accordingly
thx
Failure is success in progress.
A.E.
Offline
mirrors can be accessed over http, htpps or rysnc.
rsync isn't part of the installation iso (and is mainly used to synchornize mirrors) .
The --protocol option can be used to make sure reflector only uses a specific protocol, reflector wiki page has 2 examples using it.
added
Disclaimer : this could be a bug in reflector, without full command outputs that's almost imposible to determine.
Last edited by Lone_Wolf (2019-08-04 13:15:26)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
without full command outputs that's almost imposible to determine.
I know, my script performs a reboot at the end of the installation, so there was no way to retrieve the errors...
Is there a way to collect the errors in arch-chroot during installation?
Failure is success in progress.
A.E.
Offline
Is there a way to collect the errors in arch-chroot during installation?
Have a writable partition and then use e.g. script to log terminal output? Or redirect your script output to a file (with tee if you want visible output as well)
Or just remove the automatic reboot during testing?
Last edited by progandy (2019-08-04 19:09:38)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline