Filesystem root has 0 bytes disk space?

I have Zorin OS pro 16.3 and I only have Zorin.

I was wondering about partitioning the drives when I installed it, which is something I haven't done, and now I think I need to. At least I think that's the problem.

The error message says my "filesystem root has 0 bytes disk space."

What do I do to fix this problem?

When I started up my computer it said "filesystem root has only 765.6 MB disk space left.

You need to clear out some space. I would recommend running the following commands if already booted.
If you need to boot first, boot into Advanced Options for Zorin then select the (recovery) option and then arrow key to Drop to root prompt (This avoids adding any new files to root when you boot).

sudo apt clean && sudo apt autoremove

Clear out old logs:

sudo journalctl --vacuum-size=200M

You may need to remove old kernels.
What is your terminal output for

dpkg --list 'linux-image*'

I will work on the first thing to do-boot into advanced options but meanwhile how do I get the terminal readout into this box?


Well, I guess I did it.
Be back after I do the first thing.

I booted into the Bios Utility and at the bottom it gives an option of advanced along with default, save, boot menu. If I go into this advanced option it gives me a page that says Main, Advanced, Boot, Security options. If I choose this I still cant find anywhere I can get to recovery.

No, the Zorin OS Advanced options from the Grub Menu, not the BIOS Settings.

That is a lot of old kernels taking up a LOT of space. We should clear most of those out (Leave one, though, as a fallback in case you need it.)

sudo apt remove --purge linux-image-5.15.0-100-generic linux-image-5.15.0-101-generic linux-image-5.15.0-105-generic linux-image-5.15.0-107-generic linux-image-5.15.0-113-generic linux-image-5.15.0-117-generic linux-image-5.15.0-119-generic linux-image-5.15.0-121-generic linux-image-5.15.0-122-generic linux-image-5.15.0-124-generic linux-image-5.15.0-126-generic linux-image-5.15.0-130-generic linux-image-5.15.0-131-generic linux-image-5.15.0-134-generic linux-image-5.15.0-136-generic linux-image-5.15.0-138-generic linux-image-5.15.0-78-generic linux-image-5.15.0-84-generic linux-image-5.15.0-86-generic linux-image-5.15.0-87-generic linux-image-5.15.0-88-generic linux-image-5.15.0-89-generic linux-image-5.15.0-91-generic linux-image-5.15.0-92-generic linux-image-5.15.0-94-generic linux-image-5.15.0-97-generic

sudo update-grub

2 Likes

I typed this code in and at the end it showed it said "unable to locate package"....and it lists two commands I put in wrong such as linux-image-5.15 without the added 0.
So I need to do over just a couple of these . The others were fine.
How do I put a command in for that? Should it be purge linux-image-5.15.0 and whatever number it is or do I put purge linux-image-5.15.0 and whatever number it is?
I hope you can understand this.

I... actually cannot understand it because you listed the same option twice... :wink:

The removal command will be (replacing X with the proper number):

sudo apt remove --purge linux-image-5.15.0-XXX

I did worry about the length of that given that you needed to key all of that in manually due to using the recovery menu - no copy paste allowed.

That you only had a couple of typos is impressive.

2 Likes

I appreciate the compliment!
So, I typed in the number I thought it was, 126, but it said it was unable to locate package linux-image-5.15.0-126. That was one of the ones I messed up on. I don't remember the other one right now. Is it important I get all the numbers you included purged or included? I will retype the whole thing again if I need to.

1 Like

That was a lot of kernels. I think if you got the majority of them, that is sufficient space cleared to boot normally.

Once booted, you can use

dpkg --list 'linux-image*'

To see what is left over, then can employ copy / paste to catch the stragglers.

1 Like

Well i ran that code. I can't remember what the outcome was because I couldn't get the zorin os to start ip when i start the computer. I'm on my phone now. The signin screen shows the zorin logo flashing but then it goes away and leaves just the computer logo behind.
The last time I tried to boot into bios not using the grub bios I chose boot menu and a box came up asking which boot and there were 2 options. One was the name of my system and tge other said something like enter setup.
So I'm going to be back on the morning to see your helpful solution to my mess I created.
I did notice at the time we were talking about whether i needed to make sure i got all the numbers included i got a pop up message again about low disk soace. That's why i restarted my co.piter.

My cat interfered before i could fix the spellings. Sorry. The last sentence was supposed to be that i restarted my computer when i saw the low disk space pop up again after running the last code you gave me.

1 Like

And it currently will not boot normally?

I got to the grub bios and chose recovery and it gave me a terminal prompt at the bottom of my screen. I pressed escape and it's telling me what will happen when i exit the recovery mode.
No it won't boot into zorin.

Ok, what happens when you run

dpkg --list 'linux-image*'

to show what kernels are still installed?

Do you use Snap packages?
A lot of Flatpaks?

A few more cleaning commands to try to clear out some space:

sudo rm -rf /var/crash/*

sudo rm -rf ~/.cache/*

sudo rm -rf /var/tmp/*

sudo rm -rf /tmp/*

1 Like

I can't get my computer to boot into zorin. It flashes the logo a few times but then nothing.
I'm on my old computer.
So I know how to get into the grub bios and I saw several options for recovery. I tried the newest recovery option and nothing. I then tried the generic, not recovery, to see if I could get it to do anything and nothing, or rather maybe that was a problem.

I figured out how to get a command prompt and this was the outcome of the dpkg --list 'linux-image*'

Your earlier attempt to remove all those spacehog kernels did not remove any of them due to a typo.

You can remove them again in this terminal, all at once and carefully checking for typos, or one at a time.

1 Like

When I get to the cursor prompt it asks whether it's maintenance and if not to cntl D.
I tried maintenance and the line I was typing was just staying at the bottom on the screen and it was blending into the prompt words before the prompt that identify my computer and then seemed to be replacing them with my code.
Is that fine or should I choose "to continue-cntrl D" instead?
While I'm waiting for your reply I think I'll try putting them in one at a time.