You are not logged in.
Pages: 1
Ok, I am trying to reinstall Arch on my HP Mini 1000 and I can get through every part of the installation fine up to the Configure System part. I go to edit the config files but they are all blank. I noticed it is opening the files from /mnt/etc, which for some reason is not being created. I am using the 2009.02 FTP USB image, which I have used a few times before with no problem. I have tried redownloading the image from a different mirror, and I checked the MD5SUM and it passes, but the same problem still persists. I have tried multiple mirrors during the install, and they all seem to download the packages fine. Everything looks great until I try to edit the configs. I have tried everything I can think of and nothing is working.
Thanks in advance.
Last edited by dotCapone (2009-07-16 01:45:05)
Offline
hi,
also happened to me a couple of times. did you run arch setup as root?
Offline
Sounds like there was an error during the package instalation step. Check vc/7. Also check that all the partions were mounted correctly.
Last edited by Mr.Elendig (2009-07-15 13:59:59)
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
I am running setup as root. Mount shows that the partition is mounted and it doesn't show any errors in vc/7. The last thing it says in vc/7 is downloading core.db.tar.gz.
Offline
Well I just figured out you could scroll down at the screen where the packages are installed, and it says all the packages are corrupted. I tried multiple mirrors, and I even tried using the core installer image and even that says some of the packages are corrupted. I have tried multiple mirrors, multiple images, and multiple flash drives, and the same problem keeps occuring.
Offline
I tried one last time and just one package was corrupted, so I went back to pick the packages again, and it redownloaded the corrupt package and then everything installed fine from there.
Last edited by dotCapone (2009-07-16 01:52:52)
Offline
Hi,
This happened to me too over the weekend, I solved it by burning the core distribution rather than livecd. (x86_64)
TOAD
Offline
Pages: 1