The output of the filesystem in post #1 shows that the root filesystem "/dev/nvme... /" is a 250.4GB partition that has used 236.3GB, and only has 1.3GB available. That means that about 99.5% of the root filesystem is used.I found something this afternoon which might be causing the problem.
Seems that when I create anything, file, video etc then it automatically saves it to the media/David/data directory. It could be that this has become full due to me making a video the other day and saving it. Only today did I discover this and move the 'save to' directory onto the external hard drive. But I still cannot remove stuff on the media/david/data file.
A linux system works optimally when the root filesystem is used up to about 80%. As the percentage usage rises from that point, the chances of deteriorated performance rises. By the time the percentage figure reaches into the mid 90s, some seriously poor performance starts to occur until high 90s percentages just sees the system falter altogether until it eventually just stops. The experiences you describe are consistent with symptoms of the filling and near full root filesystem.
The resolution to the problem is to remove files from the root partition. After that, one can deal with the rest of the filesystem.
The image of the system monitor output in post #1 has truncated the full name of the root partition. It's the second item in the listing of the second image.
Clearer better information would come from the following two commands in a terminal:
Code:
lsblk
df -h
If unsure of how to use code tags, please see here: https://linux.org/threads/the-code-tag-and-why-it-matters.57746/#post-276419
To find out the directories and/or files that are using the most space on the root partition, you can run the following command as root in a terminal to find the top 30 directories or files that are using space:
Code:
du -hxa / |sort -hr | head -n 30
That command may take a little time, some seconds, to run, so the user needs to wait till it finishes. If you provide those details, (in code tags), readers will be in a better position to see what can be done to resolve the issue. There's certainly no need to re-install at this point without having the relevant information.
Once one has dealt with the root filesystem, the other disks and partitions can be managed.
I note that similar commands have been requested in earlier posts by @CaffeineAddict and @Mike-BTU but since the outputs haven't been forthcoming, I've repeated similar requests. I think readers really need that information to provide the best help.
Last edited:

