Friday, May 3, 2024
 Popular · Latest · Hot · Upcoming
7
rated 0 times [  7] [ 0]  / answers: 1 / hits: 14827  / 2 Years ago, sun, february 27, 2022, 9:01:57

Ubuntu 12.04.



After an update, I get a red warning icon in the system tray, warning about an error: broken count >0



Opening Update manager, I see that the broken package is linux-headers-3.2.0-33-generic-pae (new install)



Specificaly I have my ubuntu on an AspireOne with 8gb internal storage.



I tried apt-get clean as suggested in another question on this site, and tried reinstalling the package in Synaptic.



I have tried to reboot but to no avail.



I have also tried apt-get install --fix-broken and I get the following:



sudo apt-get install --fix-broken
[sudo] password for elina:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
linux-headers-3.2.0-33-generic-pae
The following NEW packages will be installed:
linux-headers-3.2.0-33-generic-pae
0 upgraded, 1 newly installed, 0 to remove and 38 not upgraded.
1 not fully installed or removed.
Need to get 0 B/977 kB of archives.
After this operation 11,3 MB of additional disk space will be used.
Do you want to continue [Y/n]; y
(Reading database ... 437051 files and directories currently installed.)
Unpacking linux-headers-3.2.0-33-generic-pae (from .../linux-headers-3.2.0-33-generic-pae_3.2.0-33.52_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/linux-headers-3.2.0-33-generic-pae_3.2.0-33.52_i386.deb (--unpack):
unable to create `/usr/src/linux-headers-3.2.0-33-generic-pae/include/config/usb/gspca/sonixb.h.dpkg-new' (while processing `./usr/src/linux-headers-3.2.0-33-generic-pae/include/config/usb/gspca/sonixb.h'): No space left on device
No apport report written because the error message indicates a disk full error
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/linux-headers-3.2.0-33-generic-pae_3.2.0-33.52_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


I've tried all suggestions I could find:



sudo apt-get clean
sudo apt-get autoclean
sudo apt-get autoremove
sudo apt-get update
sudo apt-get upgrade
sudo apt-get -f install
sudo apt-get install --fix-broken


Then I saw that on the error there was a mention about free space. So I did a df -h and the result was:



Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1 7,0G 5,5G 1,1G 84% /
udev 235M 4,0K 235M 1% /dev
tmpfs 97M 816K 96M 1% /run
none 5,0M 0 5,0M 0% /run/lock
none 242M 352K 242M 1% /run/shm


I see that on my root folder I have 1.1Gb free. The broken package is



linux-headers-3.2.0-33-generic-pae_3.2.0-33.52_i386.deb


which only takes up 11.3Mb on my hard drive.



I'm soooo lost.
I really hope there is something I'm missing here. I don't want to go about reformatting this bucket. It's really not worth the time.
Any help for fixing this would be hot.


More From » apt

 Answers
2

I actually found the solution to my problems. It seemed that using root to launch nautilus caused all inodes to go up to 100%. Had to clean those up in the trashes of the root. So I did the following:



df -i


That gave me the following:



$ df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda1 460560 456125 4435 100% /
udev 60125 491 59634 1% /dev
tmpfs 61943 403 61540 1% /run
none 61943 3 61940 1% /run/lock
none 61943 8 61935 1% /run/shm


woops! inodes in use 100%? that means lots and lots of tiny files stored somewhere. Where?



I used the command:



sudo du -h /* | grep '[0-9]M'


That gave a huge list of files which seemed ok except the fact that the root trashes was full of files in:



/root/.local/share/Trash/files/


So I ran:



sudo rm -r /root/.local/share/Trash/files/


and:



sudo touch /forcefsck


and then restarting to let the last command do its thing.



After that, running:



df -i
and df -Th


produced the following:



$ df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sda1 460560 196674 263886 43% /
udev 60125 487 59638 1% /dev
tmpfs 61943 393 61550 1% /run
none 61943 3 61940 1% /run/lock
none 61943 8 61935 1% /run/shm

$ df -Th
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda1 ext4 7,0G 4,7G 2,0G 71% /
udev devtmpfs 235M 4,0K 235M 1% /dev
tmpfs tmpfs 97M 816K 96M 1% /run
none tmpfs 5,0M 0 5,0M 0% /run/lock
none tmpfs 242M 356K 242M 1% /run/shm


iNodes were back to normal and I actually saw a slight increase in disk space (from 1,1 to 2,0 Gb) That made the system very fast too so there was a positive side effect to fixing the issue since my computer now seems to be lightning fast!



I want to note that if you suffer from the same issue, any folder in your system might hold those tiny files that fill up your inodes. Carefully examining the list that is created using:



sudo du -h /* | grep '[0-9]M'


will help you find which folder needs correction.


[#33986] Tuesday, March 1, 2022, 2 Years  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
clegian

Total Points: 283
Total Questions: 115
Total Answers: 115

Location: Morocco
Member since Tue, Feb 2, 2021
3 Years ago
clegian questions
;