[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 14/11/2019 19:41, Simon Waters wrote:
On Thursday, 14 November 2019 12:03:47 GMT Julian Hall wrote:Hi, Thanks for the advice thus far, unfortunately the situation has marched smartly down the loo since I last posted. I found a website called Easy Linux Tips Project with advice on cleaning up a Linux system, but in attempting to follow that advice I discovered that / actually had /zero/ bytes, not the 8Gb which initially seemed available. At that point nothing would work so I decided to recover from my rsync backupIn the unhelpful school of what you could have done then....
aka 'Lessons for next time':)
I think you could have booted from a recovery disk, mount the file system, and clear out the dross (or if using lvm type system extend the disk if there is a bit of space somewhere, I knew the swap partition was good for something, reducing it a bit for some free space).
If I knew what to clean out, and how to safely, that would be useful.
When you get to zero bytes on the root file system you are using it is hard to do much locally,
Pretty much impossible which is why I eventually formatted the partition and rsynced the backup into it.
I solved the permissions issue by realising I was being an idiot, and although the website instructions didn't say so I should be using sudo to run the rsync. That worked, but then GRUB decided to throw in the towel. Cue GRUB Recovery disk. That stuffed up and would only see the old Mint 17.3 installation. Then I did a clean reinstall from my Mint 19 DVD only to find I was back to square one, Mint 19 X server refusing to load, this time with about 100Gb free onb the partition.
I now have the original Mint 19.2 rsync backup on the partition, and it still won't load. Rapidly running out of ideas as a fresh install /should/ have at least loaded properly.
Julian -- The Mailing List for the Devon & Cornwall LUG https://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq