You are not logged in.
Pages: 1
hey,
i broke my archlinux (64bit) installation so i'm trying to repair it via livecd but i have a couple of problems:
first, i tried a ~2 year old ArchBoot CD. whenever i tried to install a package with pacman -r it would say execv failed (no such file or directory). i couldn't fix it despite there being several related topics on these forums.
then i tried the current archlinux-2013.11.01-dual iso (thumb drive) and it would time out after 30 seconds looking for the livecd-root by UUID.
since i had already installed the newest archboot version to the same thumb drive i just rebooted into ArchBoot and it would boot perfectly fine but now there's another problem.
Whenever i try to install a package with pacman via pacman -r /mnt (original hard drive installation i'm trying to fix) it would say:
partition / is full. not enough free blocks. ~300 blocks, 0 free <- something along these lines
i'll update the thread in ~half an hour, gotta catch my bus!
no place like /home
github
Offline
Just how big is the partition you are trying to install to? Also, do you know how much space is being used in it?
Claire is fine.
Problems? I have dysgraphia, so clear and concise please.
My public GPG key for package signing
My x86_64 package repository
Offline
sorry, that took me a little longer than 30 minutes.
it is definately not a space problem. the update in question was less than 1 mb and i have checked with other packages, too. besides, df -h shows 39% free space on / which is a couple of gigabytes.
the partition is also definately mounted with write-permissions (it's ext4, btw) and df -ih shows free inodes, too.
just seems very peculiar to me.
anyway, after 2-3 years without updates it's probably best if i just do a clean install. i'm going to copy some files and get to it. still, it would be interesting to see if anyone has an clue as to what's going on.
regards
Last edited by demian (2013-11-04 18:50:26)
no place like /home
github
Offline
still, it would be interesting to see if anyone has an clue as to what's going on.
Well, if I had to guess...
...after 2-3 years without updates...
That's probably it, not to mention...
the update in question was less than 1 mb
If you updated a single package after several years without updates (the only thing I can infer here), that absolutely was the cause of the breakage. What the package was doesn't matter, as pacman dislikes partial updates and a number of fundamental things that have changed in that span of time. If you don't intend to update your system regularly---like, at least once a week---you may want to look into another distribution.
Offline
Pages: 1