Every atp command returns an avalanche of errors, I freed up some space but the package management stuff seems gone and I can’t seem to fix it. Should I fresh install?
SOLUTION: Okay first of all thanks to all the people who replied to me and pointed me to the right direction, the issue was I was having full disk space and missing a few apt libraries which prevented the commands to run succesfully. I solved by freeing up some space, chrooting inside my corrupted environment from a live USB (there’s plenty of guides online on how to do this correctly), I downloaded (from debian package search) and installed manually with dpkg a few packages: apt-transport-https, curl, and libnettle8t64 which apt-transport-https required and which was the one actually solving the problem. After that apt --fix-broken install could run succesfully and every further apt command worked without issues, upgraded the system and now it is booting fine! Again, thank you so much @mumblerfish@lemmy.world, @utopiah@lemmy.ml @hendrik@palaver.p3x.de, @ThanksForAllTheFish@sh.itjust.works, @BassTurd@lemmy.world, @IsoKiero@sopuli.xyz !
Try cleaning up space through a live usb of any distro.
Removed by mod
In case anyone is tempted, don’t run this
Yeah, you need a sudo in front of it otherwise it won’t work.
Also
--no-preserve-rootAnd to clarify to those that don’t know what it does, it will recursively and forcibly remove everything in the / directory, which is the root directory. Run the command and it all dies.
And all of your data on that machine is gone as well.
Well Linux will stop you I think if you run it without
--no-preserve-rootThe Debian installer rescue mode can make it a lot easier by dropping you on a terminal chrooted to your root filesystem with all other mounts already in place.
It will be CLI only but anyone who’s comfortable with a shell should have a much better time there than on a live distro.
This is such an important thing to learn when using linux. If you want to be able to rescue your setup and not just reinstall: live usb!
To do a rescue on a system that does not boot, then you may also have to enter your environment and fix things, you do that by chroot. I always forget what steps are necessary, so I always look it up in the gentoo handbook: https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Chrooting It is the same principle with any live media.