Command or tool for terminal to report disk space but as a kind of TUI (Terminal User Interface)?

[Rosika (Rosika Schreck)]

Hi Manuel,

you´re welcome.

@Manuel_Jordan

because the Figures shared by my side are Live CD/DVD and thus the OS itself is not running.

Hmm, it makes me wonder .

You provided this screenshot (cropped):

So “Status” says it´s “Active”. I guess that´s the reason for the key symbol being displayed.
Although…

@Manuel_Jordan

the OS itself is not running

… might it be the case that /dev/sda3 is still mounted

Just a thought.

Cheers from Rosika

[Manuel_Jordan]

Very very interesting … if the OS is not running how is mounted that partition?

LOL … tools and Linux always have something to show!

[Rosika (Rosika Schreck)]

@Manuel_Jordan :

Hi Manuel,

@Manuel_Jordan

if the OS is not running how is mounted that partition?

O.K., I guess your reasoning is: why is the respective partition mounted even if the OS running as virtual machine isn´t running at the moment?

Seems intriguing…

Well, now I actually had to to consult perplexity for some explanation

The key icon on /dev/sda3 appears because the GParted Live environment itself has mounted the partition, even though your Linux Server OS is not running.
Here’s why this happens and how to resolve it:

Why /dev/sda3 is Mounted in GParted Live:

Live Environment Behavior:

When booting from the GParted Live CD/DVD, the VM runs the GParted operating system (not your installed Server OS).
This Live environment may automatically mount partitions like /dev/sda3 for read-only inspection or to facilitate repairs.
The key icon indicates the partition is mounted, preventing modifications until unmounted.

Could this be it

Cheers from Rosika

P.S.:

Another possibility:

VirtualBox Boot Configuration:

If the VM’s boot order prioritizes the Live CD/DVD over the virtual hard disk, the VM will repeatedly boot into GParted instead of your Server OS. This keeps the partitions “in use” by the Live session, even though the Server OS is inactive

[pdecker]

@Manuel_Jordan

Because the Linux server is installed through VirtualBox it is stored in a .vdi file. It was created with a size of 50GB. Therefore the “fake” HDD/SSD has only 50GB. When the du command is executed it shows the same structure data. But in none place appears the 50GB.

I’m not clear on what you are saying, but I think maybe you are wondering why you don’t see a 50GB .vdi file.

By default, VirtualBox will allocate only the currently needed space and grow the file as needed until it reaches the 50GB (or whatever size) limit you configured.

[Manuel_Jordan]

@pdecker

By default, VirtualBox will allocate only the currently needed space and grow the file as needed until it reaches the 50GB (or whatever size) limit you configured.

Correct … it because from the beginning the .vdi file was created with 50GB … thus if I reach the limit is mandatory two things:

• With VB increase the vdi file to give extra space
• Use GParted as Live CD/DVD to increase the storage according with the new addition added in the previous step

I think exists at least 2 more ways to create the .vdi capacity from the beginning

[Manuel_Jordan]

Hello @Rosika

O.K., I guess your reasoning is: why is the respective partition mounted even if the OS running as virtual machine isn´t running at the moment?

Correct.

Seems intriguing…
Well, now I actually had to to consult perplexity for some explanation

LOL

The key icon on /dev/sda3 appears …
Could this be it

Has sense in someway

If the VM’s boot order prioritizes the Live CD/DVD over the virtual hard disk, the VM will repeatedly boot into GParted instead of your Server OS. This keeps the partitions “in use” by the Live session, even though the Server OS is inactive

But it is the correct approach, first read the “Optical Disk” and later the “Hard Disk” … otherwise the Live CD/DVD never runs …

Interesting this behavior

[Rosika (Rosika Schreck)]

Thanks @Manuel_Jordan for the feedback

Cheers from Rosika