F5F Stay Refreshed Software Operating Systems Incorrect storage capacity detected on your device.

Incorrect storage capacity detected on your device.

Incorrect storage capacity detected on your device.

F
finnster20
Member
161
05-24-2018, 12:13 PM
#1
Hi, I'm using Kali Linux 2018.1. It was working well until xfce stopped functioning, and I've fixed it so I can access the desktop. However, I notice something odd with disk space: when I run df, it shows 0% free space, but the available and used sections still display around 200MB. I've tried removing unnecessary packages, but it doesn't seem to free any space. It seems the issue persists even after booting normally. The problem might be related to how the virtual box is linked to the actual disk.
F
finnster20
05-24-2018, 12:13 PM #1

Hi, I'm using Kali Linux 2018.1. It was working well until xfce stopped functioning, and I've fixed it so I can access the desktop. However, I notice something odd with disk space: when I run df, it shows 0% free space, but the available and used sections still display around 200MB. I've tried removing unnecessary packages, but it doesn't seem to free any space. It seems the issue persists even after booting normally. The problem might be related to how the virtual box is linked to the actual disk.

I
Imorrivel
Member
60
05-30-2018, 11:49 PM
#2
Using du -h --max-depth=1 helps locate where the data resides. k4dirstat works well in a GUI environment. Exercise caution when running du from the root; it may traverse /proc and generate numerous errors that disrupt output. Try extracting around a few hundred MB and check if df reflects any changes. This assumes you're not storing all data in a single, large trash bin.
I
Imorrivel
05-30-2018, 11:49 PM #2

Using du -h --max-depth=1 helps locate where the data resides. k4dirstat works well in a GUI environment. Exercise caution when running du from the root; it may traverse /proc and generate numerous errors that disrupt output. Try extracting around a few hundred MB and check if df reflects any changes. This assumes you're not storing all data in a single, large trash bin.

C
COLIN20052012
Posting Freak
857
06-01-2018, 01:28 AM
#3
The problem likely stems from insufficient free space on the system. Many applications require temporary storage, and 127MB is insufficient for most tasks.
C
COLIN20052012
06-01-2018, 01:28 AM #3

The problem likely stems from insufficient free space on the system. Many applications require temporary storage, and 127MB is insufficient for most tasks.

D
Dephunkpunk_2
Senior Member
484
06-01-2018, 08:34 PM
#4
Building on QXC's comments, executing du -sh * in the root directory (since you're root) will display a summary of each folder and file's size. This is the standard method I use to check storage usage.
D
Dephunkpunk_2
06-01-2018, 08:34 PM #4

Building on QXC's comments, executing du -sh * in the root directory (since you're root) will display a summary of each folder and file's size. This is the standard method I use to check storage usage.

C
CreeperKaeKae
Junior Member
14
06-01-2018, 08:48 PM
#5
Thanks for letting me know about the issue. I didn’t realize I was transferring my friend’s SD card to the disk. It’s now 6.5GB and everything is working again. Appreciate the help!
C
CreeperKaeKae
06-01-2018, 08:48 PM #5

Thanks for letting me know about the issue. I didn’t realize I was transferring my friend’s SD card to the disk. It’s now 6.5GB and everything is working again. Appreciate the help!

T
tdowlingiii
Member
127
06-01-2018, 09:28 PM
#6
Using df -h provides a clearer view of disk space usage.
T
tdowlingiii
06-01-2018, 09:28 PM #6

Using df -h provides a clearer view of disk space usage.

P
PerfectPonySam
Junior Member
13
06-03-2018, 04:01 PM
#7
df displays human-friendly results while df -m uses megabytes. They work differently yet remain practical. When comparing df and du, the latter focuses on disk space, whereas du highlights actual file sizes. Using du is better for identifying storage consumption.
P
PerfectPonySam
06-03-2018, 04:01 PM #7

df displays human-friendly results while df -m uses megabytes. They work differently yet remain practical. When comparing df and du, the latter focuses on disk space, whereas du highlights actual file sizes. Using du is better for identifying storage consumption.

D
Damien1019
Member
185
06-05-2018, 02:20 PM
#8
You're looking for a way to see free disk space without getting the wrong title. The person was interested in file and folder sizes, not just overall space.
D
Damien1019
06-05-2018, 02:20 PM #8

You're looking for a way to see free disk space without getting the wrong title. The person was interested in file and folder sizes, not just overall space.