You are not logged in.
Hello,
I just set up a new install and wanted to install all the stuff I usually have on my system.
However, during install (libreoffice in this case), I got an error message:
error: Partition / too full: 184198 blocks neede, 82100 blocks free
error: not enough free disk space
error: failed to commit transaction (not enough free disk space)
Errors occured, no packages were upgraded.
lsblk shows this:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
zram0 253:0 0 3.8G 0 disk [SWAP]
nvme0n1 259:0 0 238.5G 0 disk
├─nvme0n1p1 259:1 0 484M 0 part /boot
├─nvme0n1p2 259:2 0 18.1G 0 part
│ └─luksdev 254:0 0 18.1G 0 crypt /
└─nvme0n1p3 259:3 0 219.4G 0 part
└─ainsthomeloop 254:1 0 219.4G 0 crypt /home
(Sorry for the weird formatting)
Some packages install just fine (blender, gimp and inkscape were fine), while others give me the error message.
I used the guided installer and let it figure out partitioning. I use Systemd directly, no Grub
I'm not totally opposed to doing a fresh install, but then I'd probably have to figure out partitioning myself and that's one of my main problems with the non-guided install…
TIA
Last edited by Dying_Watchdogs (2021-12-18 14:46:47)
Offline
luksdev 254:0 0 18.1G 0 crypt /
A root of 18 G seems a bit small, but there are things you can do to free some space.
I'd start with https://wiki.archlinux.org/title/Pacman … kage_cache .
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
luksdev 254:0 0 18.1G 0 crypt /
A root of 18 G seems a bit small, but there are things you can do to free some space.
I'd start with https://wiki.archlinux.org/title/Pacman … kage_cache .
Hm, you're right, that is small. Thing is, I just let the guided installer do its thing, saying yes to all the defaults; so I'm not sure why it would do that. Maybe because the disk itself is quite small and it takes a percentage or something? Your signature indicates you're not the person to ask here, though.
Anyway, deleting everything in the package cache got rid of the issue, but obviously isn't ideal. I don't care that much for now, since I don't plan to install much more on it – I'll see how it fares with updates and the cache getting full again.
Thanks, I'll mark it solved.
Last edited by Dying_Watchdogs (2021-12-18 14:48:17)
Offline