El disco raíz / está lleno

If none of the more specific forums is the right place to ask

El disco raíz / está lleno

Postby Guilledebian » 2018-04-19 02:35

Hola, me encuentro con ese problema: me aparece el mensaje que el disco raíz / está lleno.
He usado Bleachbit para limpiar, pero generalmente ahí es cuando me aparece el mensaje. Además el sistema me anda lento, se cuelga internet todo el tiempo, el indicador del tiempo meteorológico no recarga...

Según creo es importante relevar esta información para que me ayuden, aunque no soy un gran conocedor, quiero dar la información necesaria para que puedan ayudarme.

Ingreso en terminal y pongo:
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda5 during installation
UUID=ed61df78-447d-486a-a117-e88652a78b72 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda9 during installation
UUID=c188acee-db41-4da1-9d36-5c851eb44be6 /home ext4 defaults 0 2
# swap was on /dev/sda7 during installation
UUID=7ab1c185-75c6-48cc-ba4c-fe95d651b6d3 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0

df -h
S.ficheros Tamaño Usados Disp Uso% Montado en
/dev/sda5 8,2G 4,3G 3,5G 55% /
udev 10M 0 10M 0% /dev
tmpfs 1,6G 9,1M 1,6G 1% /run
tmpfs 3,9G 22M 3,9G 1% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 3,9G 0 3,9G 0% /sys/fs/cgroup
/dev/sda9 53G 15G 36G 29% /home
tmpfs 790M 4,0K 790M 1% /run/user/120
tmpfs 790M 20K 790M 1% /run/user/1000

uname -r
3.16.0-5-amd64

uname -a
Linux cpe-80ee734c16c0 3.16.0-5-amd64 #1 SMP Debian 3.16.51-3+deb8u1 (2018-01-08) x86_64 GNU/Linux

ls -l /boot
total 41428
-rw-r--r-- 1 root root 157756 dic 14 18:27 config-3.16.0-4-amd64
-rw-r--r-- 1 root root 157786 ene 9 08:42 config-3.16.0-5-amd64
drwxr-xr-x 5 root root 4096 ene 11 17:21 grub
-rw-r--r-- 1 root root 15217874 ene 10 15:23 initrd.img-3.16.0-4-amd64
-rw-r--r-- 1 root root 15218459 ene 11 17:21 initrd.img-3.16.0-5-amd64
-rw-r--r-- 1 root root 2684316 dic 14 18:27 System.map-3.16.0-4-amd64
-rw-r--r-- 1 root root 2683305 ene 9 08:42 System.map-3.16.0-5-amd64
-rw-r--r-- 1 root root 3137712 dic 14 18:25 vmlinuz-3.16.0-4-amd64
-rw-r--r-- 1 root root 3139776 ene 9 08:40 vmlinuz-3.16.0-5-amd64


Luego hago lo mismo poniendo sudo su y la contraseña:

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda5 during installation
UUID=ed61df78-447d-486a-a117-e88652a78b72 / ext4 errors=remount-ro 0 1
# /home was on /dev/sda9 during installation
UUID=c188acee-db41-4da1-9d36-5c851eb44be6 /home ext4 defaults 0 2
# swap was on /dev/sda7 during installation
UUID=7ab1c185-75c6-48cc-ba4c-fe95d651b6d3 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/sr1 /media/cdrom1 udf,iso9660 user,noauto 0 0

df -h
S.ficheros Tamaño Usados Disp Uso% Montado en
/dev/sda5 8,2G 4,3G 3,5G 55% /
udev 10M 0 10M 0% /dev
tmpfs 1,6G 9,1M 1,6G 1% /run
tmpfs 3,9G 55M 3,9G 2% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 3,9G 0 3,9G 0% /sys/fs/cgroup
/dev/sda9 53G 15G 36G 29% /home
tmpfs 790M 4,0K 790M 1% /run/user/120
tmpfs 790M 20K 790M 1% /run/user/1000

uname -r
3.16.0-5-amd64

uname -a
Linux cpe-80ee734c16c0 3.16.0-5-amd64 #1 SMP Debian 3.16.51-3+deb8u1 (2018-01-08) x86_64 GNU/Linux

ls -l /boot
total 41428
-rw-r--r-- 1 root root 157756 dic 14 18:27 config-3.16.0-4-amd64
-rw-r--r-- 1 root root 157786 ene 9 08:42 config-3.16.0-5-amd64
drwxr-xr-x 5 root root 4096 ene 11 17:21 grub
-rw-r--r-- 1 root root 15217874 ene 10 15:23 initrd.img-3.16.0-4-amd64
-rw-r--r-- 1 root root 15218459 ene 11 17:21 initrd.img-3.16.0-5-amd64
-rw-r--r-- 1 root root 2684316 dic 14 18:27 System.map-3.16.0-4-amd64
-rw-r--r-- 1 root root 2683305 ene 9 08:42 System.map-3.16.0-5-amd64
-rw-r--r-- 1 root root 3137712 dic 14 18:25 vmlinuz-3.16.0-4-amd64
-rw-r--r-- 1 root root 3139776 ene 9 08:40 vmlinuz-3.16.0-5-amd64

Espero contar con la ayuda de personas experimentadas ya que he visto muchas pseudo soluciones en internet y termino mareado.
Gracias
Guideb :
Guilledebian
 
Posts: 7
Joined: 2015-08-10 21:30

Re: El disco raíz / está lleno

Postby pylkko » 2018-04-19 07:10

En primer lugar, el idioma utilizado aqui is inglés, y hay un foro español
http://www.garryricketsonartworks.org/Debian-spanish/

En segundo lugar, segun lo que escribes el raíz no está llenó (55% en df -h). Pero el disco es pequeño, solo 8 GB, es por eso es possible que se llena de vez en cuando, Cuando dices que la computadora anda lento, esto sucede todo el tiempo o sólo de vez en cuando?

Una possibilidad es que tienes algun problema causando meansages de error escrito en un "log file" que crece y crece hasta que llena el disco.

Puedes mostrarnos

Code: Select all
lsblk


Code: Select all
free -h


y

Code: Select all
du -ah / | sort -n -r | head -n 50



y para ver si haya algo grande en /var/log

Code: Select all
du -ah /var | sort -n -r | head -n 10


y tambien

Code: Select all
du -ah /var/log | sort -n -r | head -n 10


Estás usando GNOME? Puedes utilizar "Baobab" para ver más información del uso de sus discos.
User avatar
pylkko
 
Posts: 1353
Joined: 2014-11-06 19:02

Re: El disco raíz / está lleno

Postby Guilledebian » 2018-04-19 13:42

Thank you for your response; Excuse me to write in spanish. I wrote in spanish trying to not forget any detail. I will write in english since now.

The computer goes slow in different moments. Internet signal break down very often. Many apps are slow to initiate. etc... I have Windows in other partitions but I think that not may cause problem.


Here I bring the information you ask:

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 149,1G 0 disk
├─sda1 8:1 0 100M 0 part
├─sda2 8:2 0 75,3G 0 part
├─sda3 8:3 0 487M 0 part
├─sda4 8:4 0 1K 0 part
├─sda5 8:5 0 8,4G 0 part /
├─sda6 8:6 0 2,8G 0 part
├─sda7 8:7 0 8,3G 0 part [SWAP]
├─sda8 8:8 0 380M 0 part
└─sda9 8:9 0 53,4G 0 part /home
sr0 11:0 1 1024M 0 rom

free -h
total used free shared buffers cached
Mem: 7,7G 4,0G 3,7G 164M 201M 1,8G
-/+ buffers/cache: 2,0G 5,7G
Swap: 8,3G 0B 8,3G

du -ah / | sort -n -r | head -n 50

du: no se puede acceder a «/run/user/1000/gvfs»: Permiso denegado
du: no se puede acceder a «/proc/4308/task/4308/fd/4»: No existe el fichero o el directorio
du: no se puede acceder a «/proc/4308/task/4308/fdinfo/4»: No existe el fichero o el directorio
du: no se puede acceder a «/proc/4308/fd/4»: No existe el fichero o el directorio
du: no se puede acceder a «/proc/4308/fdinfo/4»: No existe el fichero o el directorio
1020K /usr/share/perl/5.20.2/ExtUtils
1020K /usr/share/hal/fdi/information/20thirdparty
1020K /usr/share/evolution/3.12/ui
1020K /usr/share/dbus-1
1020K /usr/lib/x86_64-linux-gnu/librbd.so.1.0.0
1020K /usr/lib/x86_64-linux-gnu/libliveMedia.so.23.1.0
1020K /usr/lib/ure/lib/libuno_cppuhelpergcc3.so.3
1020K /usr/lib/telepathy/telepathy-gabble
1020K /lib/modules/3.16.0-5-amd64/kernel/drivers/staging/rtl8192ee
1020K /lib/modules/3.16.0-5-amd64/kernel/drivers/net/wireless/brcm80211
1020K /lib/modules/3.16.0-4-amd64/kernel/drivers/staging/rtl8192ee
1020K /lib/modules/3.16.0-4-amd64/kernel/drivers/net/wireless/brcm80211
1020K /home/guille/Música/SisiseñoresyosoydeBoca.wav
1020K /home/guille/Documentos/POPCORNTIMElinux64/node_modules/nedb/node_modules
1016K /usr/share/icons/gnome/scalable/status
1016K /usr/share/icons/Adwaita/256x256/apps
1016K /usr/share/hal/fdi/information/20thirdparty/20-libmtp9.fdi
1016K /usr/share/backgrounds/gnome/adwaita-morning.jpg
1016K /usr/lib/libreoffice/presets/database/biblio
1016K /lib/modules/3.16.0-5-amd64/kernel/drivers/staging/rtl8192ee/r8192ee.ko
1016K /lib/modules/3.16.0-4-amd64/kernel/drivers/staging/rtl8192ee/r8192ee.ko
1016K /home/guille/xiphos/help/fa
1016K /home/guille/Imágenes/Los Molinos 2017/2° C 2017/Y que viva el fútbol OK/IMG_20170519_090329913.jpg
1016K /home/guille/Imágenes/Fotos Anchorena/Inventario/IMG_20170806_191907528.jpg
1016K /home/guille/.config/libreoffice/4/user/database/biblio
1012K /usr/share/yelp/mathjax/jax
1012K /usr/share/icons/gnome/256x256/mimetypes
1012K /usr/share/doc/docutils-doc/docs/ref
1012K /usr/lib/python3/dist-packages/orca/__pycache__
1012K /usr/lib/libreoffice/program/liblwpftlo.so
1012K /home/guille/Imágenes/Los Molinos 2017/2° C 2017/Taller de lectura Ok/IMG_20170512_100636125.jpg
1012K /home/guille/Documentos/pilas-engine-bloques-master/node_modules/ember-cli-qunit/node_modules/broccoli-merge-trees/node_modules/heimdalljs/dist
1012K /home/guille/Documentos/pilas-engine-bloques-master/node_modules/ember-cli-qunit/node_modules/broccoli-jshint/node_modules/broccoli-persistent-filter/node_modules/heimdalljs/dist
1012K /home/guille/Documentos/pilas-engine-bloques-master/node_modules/ember-cli-qunit/node_modules/broccoli-babel-transpiler/node_modules/broccoli-persistent-filter/node_modules/heimdalljs/dist
1012K /home/guille/Documentos/pilas-engine-bloques-master/node_modules/ember-cli-qunit/node_modules/broccoli-babel-transpiler/node_modules/broccoli-funnel/node_modules/heimdalljs/dist
1012K /home/guille/Documentos/pilas-engine-bloques-master/node_modules/ember-cli/node_modules/testem/node_modules/socket.io/node_modules/socket.io-adapter
1012K /home/guille/Documentos/pilas-engine-bloques-master/node_modules/ember-cli/node_modules/ember-cli-preprocess-registry/node_modules/broccoli-merge-trees/node_modules/heimdalljs/dist
1012K /home/guille/Documentos/pilas-engine-bloques-master/node_modules/ember-cli/node_modules/ember-cli-preprocess-registry/node_modules/broccoli-funnel/node_modules/heimdalljs/dist
1012K /home/guille/Documentos/pilas-engine-bloques-master/node_modules/ember-cli-babel/node_modules/broccoli-funnel/node_modules/heimdalljs/dist
1012K /home/guille/Documentos/pilas-engine-bloques-master/node_modules/ember-cli-babel/node_modules/broccoli-babel-transpiler/node_modules/broccoli-persistent-filter/node_modules/heimdalljs/dist
1012K /home/guille/Documentos/pilas-engine-bloques-master/node_modules/ember-cli-babel/node_modules/broccoli-babel-transpiler/node_modules/broccoli-merge-trees/node_modules/heimdalljs/dist
1008K /usr/src/linux-headers-3.16.0-5-common/include/sound
1008K /usr/share/libreoffice/help/en-US/sbasic.jar
1008K /usr/share/gettext/intl
1008K /usr/sbin/exim4
1008K /lib/modules/3.16.0-5-amd64/kernel/drivers/scsi/lpfc
1008K /lib/modules/3.16.0-4-amd64/kernel/drivers/scsi/lpfc
1008K /home/guille/Imágenes/Los Molinos 2017/2° C 2017/Y que viva el fútbol OK/IMG_20170621_100957531.jpg
1008K /home/guille/Documentos/POPCORNTIMElinux64/node_modules/i18n/node_modules/messageformat/node_modules/watchr
1008K /home/guille/Documentos/pilas-engine-bloques-master/vendor

du -ah /var | sort -n -r | head -n 10
856K /var/cache/cracklib
800K /var/lib/firebird/2.5/system/help.fdb
800K /var/cache/cracklib/cracklib_dict.pwd
792K /var/lib/dkms/ndiswrapper/1.59/build
784K /var/lib/firebird/2.5/system/default-security2.fdb
756K /var/lib/dpkg/info/gnome-user-guide.md5sums
708K /var/lib/dpkg/info/libqtgui4:amd64.symbols
660K /var/lib/dpkg/info/gnome-user-guide.list
572K /var/lib/dpkg/info/keyboard-configuration.templates
560K /var/lib/dpkg/info/exim4-config.templates

du -ah /var/log | sort -n -r | head -n 10
488K /var/log/kern.log
444K /var/log/installer/partman
440K /var/log/daemon.log
168K /var/log/syslog
120K /var/log/installer/cdebconf/questions.dat
84K /var/log/dpkg.log
76M /var/log
64K /var/log/wtmp
60K /var/log/debug
56K /var/log/installer/status

Thanks for your help.
Guillermo
Guilledebian
 
Posts: 7
Joined: 2015-08-10 21:30

Re: El disco raíz / está lleno

Postby pylkko » 2018-04-19 19:01

Well, since you have 8 G RAM and a swap partition that is separate from the root, I think it is possible to rule out running out of RAM and getting slow down from that some how. Since you are getting messages about root being full, but df showing 55% there are only a few things that could cause this: 1) root is on some fancy fs like btrfs and not ext4 and therefor df is inaccurate 2) you are doing something which is writing massive temporary files (maybe ripping large optical media, you appear to have two /sr drives) and these temp files were not there when you typed "df -h" or 3) hardware failure, which can cause lock ups and temporary slow downs (and perhaps message about root full was unrelated)

You can run a SMART test on the drive, this should be done every now and then anyway.

use Gnome Disks from the menu button and select SMART tests or if you don't have that

Code: Select all
apt install smartmontools

Code: Select all
smartctl -a /dev/hda


The slow internet does not sound like it is relate to the disk issue, unless of course the disk is so full that temp internet files are not being able to load. But this is all guessing. It would be much better if you could get more information (like search for relevant error messages in the logs).

The root partition is a bit small, and you have space elsewhere on the disk, so it might be a good idea to enlargen it. But you need to make a back up first
User avatar
pylkko
 
Posts: 1353
Joined: 2014-11-06 19:02

Re: El disco raíz / está lleno

Postby Guilledebian » 2018-04-19 19:50

I don't plenty understand what option 1: " 1) root is on some fancy fs like btrfs and not ext4 and therefor df is inaccurate" means
About the 2nd option: "2) you are doing something which is writing massive temporary files (maybe ripping large optical media, you appear to have two /sr drives) and these temp files were not there when you typed "df -h"" I usually conect an external hard drive where I have information and backups.
About option 3: "3) hardware failure, which can cause lock ups and temporary slow downs (and perhaps message about root full was unrelated)" That means that if hardware wroke down may be causing the notification of full space why not?

Here I did the smart test, just I change hda for sda.

smartctl -a /dev/sda
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-5-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint M5
Device Model: SAMSUNG HM160HI
Serial Number: S18PJDNZ224904
LU WWN Device Id: 5 0f0000 0ea224904
Firmware Version: HH100-15
User Capacity: 160.041.885.696 bytes [160 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS, ATA/ATAPI-7 T13/1532D revision 0
SATA Version is: SATA 2.5, 1.5 Gb/s
Local Time is: Thu Apr 19 17:27:40 2018 -03
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 56) seconds.
Offline data collection
capabilities: (0x51) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 56) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 1
3 Spin_Up_Time 0x0007 252 252 025 Pre-fail Always - 2000
4 Start_Stop_Count 0x0032 095 095 000 Old_age Always - 6043
5 Reallocated_Sector_Ct 0x0033 097 097 010 Pre-fail Always - 37
7 Seek_Error_Rate 0x000f 252 252 051 Pre-fail Always - 0
8 Seek_Time_Performance 0x0025 252 252 015 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 085 085 000 Old_age Always - 7680
10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 10
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 542
12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 2854
184 End-to-End_Error 0x0033 252 252 070 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 384
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 619
190 Airflow_Temperature_Cel 0x0022 063 040 040 Old_age Always In_the_past 37 (Min/Max 12/60)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 4912
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 206
193 Load_Cycle_Count 0x0032 082 082 000 Old_age Always - 188824
194 Temperature_Celsius 0x0022 063 040 000 Old_age Always - 37 (Min/Max 12/60)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 23
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 3
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 33
201 Soft_Read_Error_Rate 0x0032 252 252 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 325 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 325 occurred at disk power-on lifetime: 7674 hours (319 days + 18 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 88 b8 9b bf e9 Error: UNC 136 sectors at LBA = 0x09bf9bb8 = 163552184

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 88 b8 9b bf e9 00 01:37:13.250 READ DMA
c8 00 08 88 0b 00 e0 00 01:37:05.812 READ DMA
ef 05 fe 00 00 00 40 00 01:37:05.687 SET FEATURES [Enable APM]
c8 00 08 20 9b 79 ea 00 01:37:05.687 READ DMA
c8 00 20 30 9b bf e9 00 01:37:05.687 READ DMA

Error 324 occurred at disk power-on lifetime: 7619 hours (317 days + 11 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 f0 f7 d2 ea Error: UNC 8 sectors at LBA = 0x0ad2f7f0 = 181598192

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 f0 f7 d2 ea 00 01:22:24.812 READ DMA
ef 05 fe 00 00 00 40 00 01:22:17.312 SET FEATURES [Enable APM]
c8 00 08 80 f7 d2 ea 00 01:22:17.312 READ DMA
c8 00 08 80 8f 79 ea 00 01:22:17.250 READ DMA
c8 00 20 08 77 3e ea 00 01:22:17.250 READ DMA

Error 323 occurred at disk power-on lifetime: 7619 hours (317 days + 11 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 88 b0 0d 8f e9 Error: UNC 136 sectors at LBA = 0x098f0db0 = 160370096

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 88 b0 0d 8f e9 00 01:16:32.625 READ DMA
c8 00 08 60 2b 03 e0 00 01:16:25.187 READ DMA
c8 00 08 a8 9b 79 ea 00 01:16:25.187 READ DMA
c8 00 90 00 ba d1 e9 00 01:16:25.187 READ DMA
ef 05 fe 00 00 00 40 00 01:16:25.000 SET FEATURES [Enable APM]

Error 322 occurred at disk power-on lifetime: 7619 hours (317 days + 11 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 f8 54 6d e9 Error: UNC 8 sectors at LBA = 0x096d54f8 = 158160120

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 f8 54 6d e9 00 01:16:22.000 READ DMA
c8 00 c8 60 9a 79 e9 00 01:16:14.562 READ DMA
ef 05 fe 00 00 00 40 00 01:16:14.500 SET FEATURES [Enable APM]
c8 00 08 80 54 6d e9 00 01:16:14.500 READ DMA
c8 00 08 80 27 03 e0 00 01:16:14.437 READ DMA

Error 321 occurred at disk power-on lifetime: 7613 hours (317 days + 5 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 f0 ff e6 eb Error: UNC 8 sectors at LBA = 0x0be6fff0 = 199688176

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 f0 ff e6 eb 00 00:00:54.562 READ DMA
c8 00 08 f8 a9 95 e9 00 00:00:47.125 READ DMA
ef 05 fe 00 00 00 40 00 00:00:47.000 SET FEATURES [Enable APM]
c8 00 08 80 ff e6 eb 00 00:00:47.000 READ DMA
c8 00 08 80 17 db eb 00 00:00:47.000 READ DMA

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Guilledebian
 
Posts: 7
Joined: 2015-08-10 21:30

Re: El disco raíz / está lleno

Postby pylkko » 2018-04-20 07:23

If you don't understand what btrfs/zfs and so on are, then you likely aren't using them.

Your drive is probably old. The firmware (these are not always right) claims about 8000 hours of usage. Since there are only about 8000 hours in a year and this machines is probably not on all the time (2854 power cycles), it means that it has been in use for many years (for example, assuming 3h / day average = 7 years). But maybe you can say more exactly?

There appear to be 37 reallocated sectors and 3 pending ones. Also some error messages (quite recent and not old). These are signs of the drive degrading, but these numbers do not sound bad if the drive has been around for ages (in normal use these happen here and there). However, you should keep an eye on these, and if they change rapidly, then the disk is likely going to die soon. If they stay at those numbers, then it probably indicates that there was a time (a single bad incident) when they happened and it is not a sign of death.

Here is a simple guide to interpreting these values if you are interested:
https://www.z-a-recovery.com/manual/smart.aspx

you could also do a test with:
Code: Select all
smartctl -t long /dev/sda

and see the results with:
Code: Select all
smartctl -l /dev/sda


You still have not copy pasted here the error message about / lleno. Could you give that so as to be able to see more exactly what it is?

Since your /tmp directory is on root (/) and not separate, I think one possibility is that you are at some points of using the machine getting enough temporary files that the root is becomming full. This would also explain all the symptoms you mention (slowing down, apps take long to open or don't open at all) etc.

In this case you should make more space on the root. If it is on ext4 file system, then this is quite easy. You need to boot a live disk (because the size can be changed only when the disks are not in use), for example Gparted live (based on Debian). Then use Gparted to decrease the partition with /home on it (maybe 5 GB or more) and increase the partition with / root on it. This process is pretty intense and copies all the data on the disk to new locations, and is therefore something were everything can go well and nice or everything can get messed up, especially if you give wrong commands by error, so make a backup before!
User avatar
pylkko
 
Posts: 1353
Joined: 2014-11-06 19:02

Re: El disco raíz / está lleno

Postby Guilledebian » 2018-04-20 17:16

Well, I bought my computer about 2011. I take to repair it about two years ago, maybe some disfunction with electric parts but also I think they change the disk.

I can't give you an image about the erro message about /lleno ( disk is full), because the site doesn't allow to do of space reasons. But the message is: " Espacio de disco bajo en / El volumen solo tiene ...mb disponible". I open bleachbit and when it does the analysis there it appears that message. I tried to do it again with bleachbit yet and now it says "Espacio de disco bajo en "home". El volumen "home" solo tiene 231,9 mb disponible". And also, may contribute this information: "Bleachbit as root" never start when I tried to use it.

Here, the results:

smartctl -t long /dev/sda
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-5-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Extended self-test routine immediately in off-line mode".
Drive command "Execute SMART Extended self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 56 minutes for test to complete.
Test will complete after Fri Apr 20 13:33:02 2018

Use smartctl -X to abort test.
root@cpe-80ee734c16c0:/home/guille# smartctl -l /dev/sda
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-5-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=======> INVALID ARGUMENT TO -l: /dev/sda
=======> VALID ARGUMENTS ARE: error, selftest, selective, directory[,g|s], xerror[,N][,error], xselftest[,N][,selftest], background, sasphy[,reset], sataphy[,reset], scttemp[sts,hist], scttempint,N[,p], scterc[,N,M], devstat[,N], ssd, gplog,N[,RANGE], smartlog,N[,RANGE] <=======

Use smartctl -h to get a usage summary

smartctl -h
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-5-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

Usage: smartctl [options] device

============================================ SHOW INFORMATION OPTIONS =====

-h, --help, --usage
Display this help and exit

-V, --version, --copyright, --license
Print license, copyright, and version information and exit

-i, --info
Show identity information for device

--identify[=[w][nvb]]
Show words and bits from IDENTIFY DEVICE data (ATA)

-g NAME, --get=NAME
Get device setting: all, aam, apm, lookahead, security, wcache, rcache, wcreorder

-a, --all
Show all SMART information for device

-x, --xall
Show all information for device

--scan
Scan for devices

--scan-open
Scan for devices and try to open each device

================================== SMARTCTL RUN-TIME BEHAVIOR OPTIONS =====

-q TYPE, --quietmode=TYPE (ATA)
Set smartctl quiet mode to one of: errorsonly, silent, noserial

-d TYPE, --device=TYPE
Specify device type to one of: ata, scsi, sat[,auto][,N][+TYPE], usbcypress[,X], usbjmicron[,p][,x][,N], usbsunplus, marvell, areca,N/E, 3ware,N, hpt,L/M/N, megaraid,N, aacraid,H,L,ID, cciss,N, auto, test

-T TYPE, --tolerance=TYPE (ATA)
Tolerance: normal, conservative, permissive, verypermissive

-b TYPE, --badsum=TYPE (ATA)
Set action on bad checksum to one of: warn, exit, ignore

-r TYPE, --report=TYPE
Report transactions (see man page)

-n MODE, --nocheck=MODE (ATA)
No check if: never, sleep, standby, idle (see man page)

============================== DEVICE FEATURE ENABLE/DISABLE COMMANDS =====

-s VALUE, --smart=VALUE
Enable/disable SMART on device (on/off)

-o VALUE, --offlineauto=VALUE (ATA)
Enable/disable automatic offline testing on device (on/off)

-S VALUE, --saveauto=VALUE (ATA)
Enable/disable Attribute autosave on device (on/off)

-s NAME[,VALUE], --set=NAME[,VALUE]
Enable/disable/change device setting: aam,[N|off], apm,[N|off],
lookahead,[on|off], security-freeze, standby,[N|off|now],
wcache,[on|off], rcache,[on|off], wcreorder,[on|off]

======================================= READ AND DISPLAY DATA OPTIONS =====

-H, --health
Show device SMART health status

-c, --capabilities (ATA)
Show device SMART capabilities

-A, --attributes
Show device SMART vendor-specific Attributes and values

-f FORMAT, --format=FORMAT (ATA)
Set output format for attributes: old, brief, hex[,id|val]

-l TYPE, --log=TYPE
Show device log. TYPE: error, selftest, selective, directory[,g|s],
xerror[,N][,error], xselftest[,N][,selftest],
background, sasphy[,reset], sataphy[,reset],
scttemp[sts,hist], scttempint,N[,p],
scterc[,N,M], devstat[,N], ssd,
gplog,N[,RANGE], smartlog,N[,RANGE]

-v N,OPTION , --vendorattribute=N,OPTION (ATA)
Set display OPTION for vendor Attribute N (see man page)

-F TYPE, --firmwarebug=TYPE (ATA)
Use firmware bug workaround:
none, nologdir, samsung, samsung2, samsung3, xerrorlba, swapid

-P TYPE, --presets=TYPE (ATA)
Drive-specific presets: use, ignore, show, showall

-B [+]FILE, --drivedb=[+]FILE (ATA)
Read and replace [add] drive database from FILE
[default is +/etc/smart_drivedb.h
and then /var/lib/smartmontools/drivedb/drivedb.h]

============================================ DEVICE SELF-TEST OPTIONS =====

-t TEST, --test=TEST
Run test. TEST: offline, short, long, conveyance, force, vendor,N,
select,M-N, pending,N, afterselect,[on|off]

-C, --captive
Do test in captive mode (along with -t)

-X, --abort
Abort any non-captive test on device

=================================================== SMARTCTL EXAMPLES =====

smartctl --all /dev/hda (Prints all SMART information)

smartctl --smart=on --offlineauto=on --saveauto=on /dev/hda
(Enables SMART on first disk)

smartctl --test=long /dev/hda (Executes extended disk self-test)

smartctl --attributes --log=selftest --quietmode=errorsonly /dev/hda
(Prints Self-Test & Attribute errors)
smartctl --all --device=3ware,2 /dev/sda
smartctl --all --device=3ware,2 /dev/twe0
smartctl --all --device=3ware,2 /dev/twa0
smartctl --all --device=3ware,2 /dev/twl0
(Prints all SMART info for 3rd ATA disk on 3ware RAID controller)
smartctl --all --device=hpt,1/1/3 /dev/sda
(Prints all SMART info for the SATA disk attached to the 3rd PMPort
of the 1st channel on the 1st HighPoint RAID controller)
smartctl --all --device=areca,3/1 /dev/sg2
(Prints all SMART info for 3rd ATA disk of the 1st enclosure
on Areca RAID controller)


Before changing the root space I prefer to find which problem is, just for not have the some problem then doing that.

Thanks,
Guilledebian
 
Posts: 7
Joined: 2015-08-10 21:30

Re: El disco raíz / está lleno

Postby pylkko » 2018-04-20 18:03

As the output of the first commmand says, you need to wait an hour for the test to complete. Then you can see the results with
Code: Select all
smartctl -l selftest /dev/sda


but showing all

Code: Select all
smartctl -a /dev/sda


should show also the test data.

I think you should open a terminal, do whatever it is you do with bleachbit and wait for the "full" message. Then do
Code: Select all
df -h
and paste that here.
User avatar
pylkko
 
Posts: 1353
Joined: 2014-11-06 19:02

Re: El disco raíz / está lleno

Postby Guilledebian » 2018-04-20 18:37

I did it, I wait until it says and I gave the information in my previously post...


smartctl -l selftest /dev/sda
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-5-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 7683 -

smartctl -a /dev/sda
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-5-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint M5
Device Model: SAMSUNG HM160HI
Serial Number: S18PJDNZ224904
LU WWN Device Id: 5 0f0000 0ea224904
Firmware Version: HH100-15
User Capacity: 160.041.885.696 bytes [160 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS, ATA/ATAPI-7 T13/1532D revision 0
SATA Version is: SATA 2.5, 1.5 Gb/s
Local Time is: Fri Apr 20 16:19:07 2018 -03
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 56) seconds.
Offline data collection
capabilities: (0x51) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 56) minutes.
SCT capabilities: (0x003f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 1
3 Spin_Up_Time 0x0007 252 252 025 Pre-fail Always - 2000
4 Start_Stop_Count 0x0032 095 095 000 Old_age Always - 6049
5 Reallocated_Sector_Ct 0x0033 097 097 010 Pre-fail Always - 37
7 Seek_Error_Rate 0x000f 252 252 051 Pre-fail Always - 0
8 Seek_Time_Performance 0x0025 252 252 015 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 085 085 000 Old_age Always - 7685
10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 10
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 542
12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 2857
184 End-to-End_Error 0x0033 252 252 070 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 387
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 624
190 Airflow_Temperature_Cel 0x0022 058 040 040 Old_age Always In_the_past 42 (Min/Max 12/60)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 4914
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 206
193 Load_Cycle_Count 0x0032 082 082 000 Old_age Always - 188824
194 Temperature_Celsius 0x0022 058 040 000 Old_age Always - 42 (Min/Max 12/60)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 23
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 2
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 33
201 Soft_Read_Error_Rate 0x0032 252 252 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 328 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 328 occurred at disk power-on lifetime: 7682 hours (320 days + 2 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 88 b0 0d 8f e9 Error: UNC 136 sectors at LBA = 0x098f0db0 = 160370096

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 88 b0 0d 8f e9 00 00:00:46.687 READ DMA
ef 05 fe 00 00 00 40 00 00:00:39.062 SET FEATURES [Enable APM]
c8 00 e0 20 b8 d1 e9 00 00:00:39.062 READ DMA
c8 00 20 40 0c 8f e9 00 00:00:39.062 READ DMA
c8 00 08 00 18 00 e0 00 00:00:39.062 READ DMA

Error 327 occurred at disk power-on lifetime: 7682 hours (320 days + 2 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 00 0b 00 e0 Error: UNC 8 sectors at LBA = 0x00000b00 = 2816

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 00 0b 00 e0 00 00:00:37.812 READ DMA
c8 00 10 70 99 71 e9 00 00:00:30.375 READ DMA
ef 05 fe 00 00 00 40 00 00:00:30.187 SET FEATURES [Enable APM]
c8 00 38 40 08 00 e0 00 00:00:30.187 READ DMA
c8 00 18 20 08 00 e0 00 00:00:30.187 READ DMA

Error 326 occurred at disk power-on lifetime: 7682 hours (320 days + 2 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 90 30 35 d0 e9 Error: UNC 144 sectors at LBA = 0x09d03530 = 164640048

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 90 30 35 d0 e9 00 00:00:28.562 READ DMA
c8 00 08 e0 dd 6e e9 00 00:00:21.125 READ DMA
ef 05 fe 00 00 00 40 00 00:00:21.062 SET FEATURES [Enable APM]
c8 00 78 40 15 6c ea 00 00:00:21.062 READ DMA
c8 00 08 18 64 42 ea 00 00:00:21.062 READ DMA

Error 325 occurred at disk power-on lifetime: 7596 hours (316 days + 12 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 90 00 ba d1 e9 Error: UNC 144 sectors at LBA = 0x09d1ba00 = 164739584

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 90 00 ba d1 e9 00 04:56:28.125 READ DMA
c8 00 08 38 28 03 e0 00 04:56:20.687 READ DMA
ef 05 fe 00 00 00 40 00 04:56:20.562 SET FEATURES [Enable APM]
c8 00 20 00 b8 d1 e9 00 04:56:20.562 READ DMA
c8 00 f0 d8 7f 91 e9 00 04:56:20.562 READ DMA

Error 324 occurred at disk power-on lifetime: 7586 hours (316 days + 2 hours)
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 08 00 2b 03 e0 Error: UNC 8 sectors at LBA = 0x00032b00 = 207616

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 00 2b 03 e0 00 00:05:57.937 READ DMA
c8 00 08 18 0b 00 e0 00 00:05:50.500 READ DMA
ef 05 fe 00 00 00 40 00 00:05:50.437 SET FEATURES [Enable APM]
ef 05 fe 00 00 00 40 00 00:05:50.312 SET FEATURES [Enable APM]
c8 00 30 d0 29 03 e0 00 00:05:50.312 READ DMA

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 7683 -

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Completed [00% left] (0-65535)
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

About: "I think you should open a terminal, do whatever it is you do with bleachbit and wait for the "full" message. Then do" I run bleachbit in terminal, then it opens (graphic mode); it appears the "full" message of / and I open a new terminal (because the one with I open bleachbit not have prompt just when Bleachbit is in use there) and then did df -h
df -h
S.ficheros Tamaño Usados Disp Uso% Montado en
/dev/sda5 8,2G 8,2G 0 100% /
udev 10M 0 10M 0% /dev
tmpfs 1,6G 9,1M 1,6G 1% /run
tmpfs 3,9G 40M 3,9G 1% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 3,9G 0 3,9G 0% /sys/fs/cgroup
/dev/sda9 53G 15G 36G 29% /home
tmpfs 790M 4,0K 790M 1% /run/user/120
tmpfs 790M 28K 790M 1% /run/user/1000
Guilledebian
 
Posts: 7
Joined: 2015-08-10 21:30

Re: El disco raíz / está lleno

Postby pylkko » 2018-04-20 20:17

Interestingly, as you can see, the later df says 100% full root. So whatever you did (ran bleachbit apparently, or maybe something before that) filled to root. Also you have two new error messages from the disk although it passed the test. But as said before an 8 GB root is quite small. You could consider getting rid of the separate partitions and just have one. Whatever you do, you will eventually need more space on that root.
User avatar
pylkko
 
Posts: 1353
Joined: 2014-11-06 19:02

Re: El disco raíz / está lleno

Postby Guilledebian » 2018-04-20 21:41

Well, I will resize the / ...
Thank you for your support, if you discover other solution let me know please.
Guilledebian
 
Posts: 7
Joined: 2015-08-10 21:30

Re: El disco raíz / está lleno

Postby Guilledebian » 2018-04-22 16:54

I did the resize but the problem continues.

df -h
S.ficheros Tamaño Usados Disp Uso% Montado en
/dev/sda5 16G 8,0G 7,2G 53% /
udev 10M 0 10M 0% /dev
tmpfs 1,6G 37M 1,6G 3% /run
tmpfs 3,9G 46M 3,9G 2% /dev/shm
tmpfs 5,0M 4,0K 5,0M 1% /run/lock
tmpfs 3,9G 0 3,9G 0% /sys/fs/cgroup
/dev/sda9 45G 6,9G 36G 17% /home
tmpfs 790M 4,0K 790M 1% /run/user/120
tmpfs 790M 20K 790M 1% /run/user/1000

Maybe something related with log files? I don't know about but

sudo find / -size +100000k

/home/guille/Vídeos/BACHILLERES 1994 COLEGIO MANUEL BELGRANO/Bachilleres 1994-Colegio Manuel Belgrano-Maristas.mpg
/home/guille/.cache/tracker/meta.db
/home/guille/kdenlive/Segundo grado 2017 Los Molinos.mp4
/home/guille/Documentos/IDIOMA CHINO/chino-en-zip/AUDIOS EN ZIP/汉语十日通 1.zip
/home/guille/Documentos/Cursos-formación profesional Guille/Cursos LinkedIn/archivos_base_tecnicas_diseno_logos.zip
/sys/devices/pci0000:00/0000:00:02.0/resource2_wc
/sys/devices/pci0000:00/0000:00:02.0/resource2
find: «/run/user/1000/gvfs»: Permiso denegado
/proc/kcore
find: «/proc/2830/task/2830/fd/5»: No existe el fichero o el directorio
find: «/proc/2830/task/2830/fdinfo/5»: No existe el fichero o el directorio
find: «/proc/2830/fd/5»: No existe el fichero o el directorio
find: «/proc/2830/fdinfo/5»: No existe el fichero o el directorio
/usr/lib/chromium/chromium
/opt/google/chrome/chrome
/var/log/syslog
/var/log/messages
/var/log/user.log
Guilledebian
 
Posts: 7
Joined: 2015-08-10 21:30


Return to General Questions

Who is online

Users browsing this forum: No registered users and 9 guests

fashionable