root partition full

malvidx · 2016-12-30 04:12:18

i cant get a straight answer on what to do when my root partition is full. i used bleachbit and it only gave me like 4% more room.

ive done google searches, tried irc, and i either dont understand what people are saying to do or i get no response. im extremely frustrated.

if i could get help in simple terms id appreciate it

thanks

BLizgreat! · 2016-12-30 05:16:53

Which filesystem in particular? How big did you make the partition? In stuff like ext4 a % is reserved for root just for situations like that.

Speaking of root did you run bleachbit as root user? Terminal type "gksudo bleachbit &exit". OR Open a run dialogue and launch it with "gksudo bleachbit". Before deleting anything, click the button to preview what's going to be deleted.

When/if you run it also pay attention to what bleachbit tells you got deleted. If you made a reasonably sized partition and its suddenly oddly full, then yep clearly you'll need to trackdown and correct the cause.

Edit also pay attention to which options you select in the column to the left in bleachbit, it will even give you a brief explanation of what each does.

Overall though jmo but you should take this issue up with your search engine of choice. A problem older than dirt and no doubt has been covered 2 death and then some.

Not meaning to be a bhole here but consider finding the solution to routine problems like this yourself a part of your training.

Last edited by BLizgreat! (2016-12-30 05:29:33)

beaker · 2016-12-30 06:48:26

Use your bunsenlabs live usb. Open gparted and increase the size of your root partition.

BLizgreat! · 2016-12-30 11:43:11

Ah already said you'd tried searching. This is a job for super du! Well actually just the plain ole du command.

Make your user root with "sudo su" then run the following to help zero in on what's running amok on your OS.

 du -sh /*

Look for something that's huge that shouldn't be. Follow up investigating as follows.

cd /

Then

ls

Find out what in the offending huge directory is responsible for using up all that diskspace. In the following let's say the /var directory was/is the one showing up as way bigger than it should be. Substitute your problem child as needed. Instead of /var, could be /home or whatever.

du -h var

Look through the output for huge files-etc.

Last edited by BLizgreat! (2016-12-30 11:45:04)

BLizgreat! · 2016-12-30 15:02:40

This got me Googling around for useful commands related to this type of thing. Found a cool one, so why not post. As root run...

find / -size +10M -print0 | xargs -0 ls -lh

Will show all files bigger than 10 Mb's system-wide. You can obviously change the size, ie: +5M there would be 5mbs. Use k for kilobytes etc. Kinda cool eh.

Vll!

Also to flog a dead horse as is my usual wont. Doesn't have to be used to only target /(root) can use the cmd on plenty of other stuff too. Ie: find /usr would show stuff of x-size in usr only.

Definitely cool imo.

Last edited by BLizgreat! (2016-12-30 16:13:15)

Horizon_Brave · 2016-12-30 17:41:27

Also, in the future, to prevent something like this, you can opt to divy up your partitions corresponding to different directories. If you know that you're non-root user will be saving a lot of cat videos and images, consider making /home/<user> it's own partition... Likewise if you know you'll be keeping a ton of logs for different services, consider making /var/log/ it's own partition. I've seen before were some people are locked out of a system due to the fact that the / is completely filled.

malvidx · 2016-12-30 18:47:29

I have done everything suggested. Bleachbit only cleaned up 4%. It appears the problem is in /usr. Its 94% full. How do i fix that? And i dont have an ext4 i have a ext2

Head_on_a_Stick · 2016-12-30 18:56:11

I like to use ncdu:

sudo ncdu -x /usr

Be very careful though, it is easy to delete system-critical files -- be sure to back up fully first.

Do you have lots of themes and/or icons installed? They live under /usr/share

What is the full output of:

df -h

malvidx · 2016-12-30 21:14:08

here is the output

malvidx@tux:~$ df -h
Filesystem                Size  Used Avail Use% Mounted on
udev                       10M     0   10M   0% /dev
tmpfs                     761M  9.3M  752M   2% /run
/dev/dm-1                 8.2G  7.0G  799M  90% /
tmpfs                     1.9G  4.0K  1.9G   1% /dev/shm
tmpfs                     5.0M  4.0K  5.0M   1% /run/lock
tmpfs                     1.9G     0  1.9G   0% /sys/fs/cgroup
/dev/mapper/tux--vg-tmp   360M  2.1M  335M   1% /tmp
/dev/mapper/tux--vg-home  210G  850M  199G   1% /home
/dev/sda1                 236M   39M  185M  18% /boot
/dev/mapper/tux--vg-var   2.7G  396M  2.2G  16% /var
tmpfs                     381M  4.0K  381M   1% /run/user/108
tmpfs                     381M   16K  381M   1% /run/user/1000
malvidx@tux:~$

malvidx · 2016-12-30 21:30:42

and i tried to install ncdu and it says it wasnt found

edited: stupid me i forgot to update first

Last edited by malvidx (2016-12-30 21:35:07)

malvidx · 2016-12-31 00:29:02

so apparently im going to have to reinstall because i have separate partitions, which is frustrating. oh well.

porkpiehat · 2016-12-31 00:42:07

Unless you have installed an extraordinary amount of extra crap, there is no normal way your root partition should have 7G used. What does ncdu tell you? The command hoas gave you:

sudo ncdu -x /usr

Or the command

sudo du -sh /*

Somewhere you have a problem that should be solvable without reinstalling.

Horizon_Brave · 2016-12-31 01:05:17

malvidx, you using an LVM partitioned disk?

malvidx · 2016-12-31 03:10:52

Horizon_Brave - yes i am

Porkpiehat:

11M	/bin
37M	/boot
4.0K	/dev
8.3M	/etc
732M	/home
0	/initrd.img
329M	/lib
4.0K	/lib64
16K	/lost+found
12K	/media
4.0K	/mnt
234M	/opt
du: cannot access '/proc/5498/task/5498/fd/4': No such file or directory
du: cannot access '/proc/5498/task/5498/fdinfo/4': No such file or directory
du: cannot access '/proc/5498/fd/4': No such file or directory
du: cannot access '/proc/5498/fdinfo/4': No such file or directory
0	/proc
1.2M	/root
du: cannot access '/run/user/1000/gvfs': Permission denied
9.3M	/run
14M	/sbin
4.0K	/srv
0	/sys
15K	/tmp
4.2G	/usr
520M	/var
0	/vmlinuz

Last edited by malvidx (2016-12-31 03:13:25)

malvidx · 2016-12-31 03:19:33

and this is the output of sudo ncdu -x /usr

    2.0 GiB [##########]  /share
    1.9 GiB [######### ] /lib
  159.8 MiB [          ] /bin
   27.0 MiB [          ] /include
   22.2 MiB [          ] /sbin
   15.6 MiB [          ] /local
   44.0 KiB [          ] /games
    4.0 KiB [          ] /src

malvidx · 2016-12-31 04:20:12

its that stupid katoolin that someone on the bunsenlabs irc channel told me to install. now i cant uninstall it because there is no way to from what i can tell doing a google search.

update: so i went in and manually did an apt-get purge on every package i installed. thankfully i only installed one group of tools.

i got root down to 57% available. it will probably go a bit up when a i re-intstall some packages i deleted but its only a few. so i found the culprit, and i advise folks NOT to install katoolin.

Last edited by malvidx (2016-12-31 05:18:24)

Horizon_Brave · 2016-12-31 05:31:32

Going to assume you didn't get that from the Debian stable repos?
This looks like an Ubuntu-centric package, that installs kali repos...

Someone fact check me on this, but the way I see it...you may have to remove the kali repositories first from your /etc/apt/sources or /etc/apt/sources.d/ then do a:

 sudo apt-get update

followed by:

sudo apt-get autoremove

(to remove packages that are no long relevant, hence removing the kali repos.)

Then you probably can remove the binary of the kalitoolin

sudo rm /usr/bin/katoolin

If I'm mistaken anyone please correct me!

Last edited by Horizon_Brave (2016-12-31 05:31:53)

malvidx · 2016-12-31 05:59:15

horizon_brave:

ive done all that and it didnt do anything. im just gonna leave it as is for now and if i run into it again ill probably do a re-install to redo my partitions.

thanks though

Head_on_a_Stick · 2016-12-31 11:32:57

I say we take off and nuke the entire site from orbit.

It's the only way to be sure.

8o

Horizon_Brave · 2016-12-31 16:38:44

Call the drop ship Cheyenne!

#1 2016-12-30 04:12:18

root partition full

#2 2016-12-30 05:16:53

Re: root partition full

#3 2016-12-30 06:48:26

Re: root partition full

#4 2016-12-30 11:43:11

Re: root partition full

#5 2016-12-30 15:02:40

Re: root partition full

#6 2016-12-30 17:41:27

Re: root partition full

#7 2016-12-30 18:47:29

Re: root partition full

#8 2016-12-30 18:56:11

Re: root partition full

#9 2016-12-30 21:14:08

Re: root partition full

#10 2016-12-30 21:30:42

Re: root partition full

#11 2016-12-31 00:29:02

Re: root partition full

#12 2016-12-31 00:42:07

Re: root partition full

#13 2016-12-31 01:05:17

Re: root partition full

#14 2016-12-31 03:10:52

Re: root partition full

#15 2016-12-31 03:19:33

Re: root partition full

#16 2016-12-31 04:20:12

Re: root partition full

#17 2016-12-31 05:31:32

Re: root partition full

#18 2016-12-31 05:59:15

Re: root partition full

#19 2016-12-31 11:32:57

Re: root partition full

#20 2016-12-31 16:38:44

Re: root partition full

Board footer