Can you do a sudo apt-get update first?
At the end I found the problem: my sd was full. I removed some files from /home/xbian and now I'm able to update & upgrade.
But the problem just changed: why is my 8G SD is (now almost) full?
Quote:xbian@xbian / $ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 7.4G 7.3G 70M 100% /
/dev/mmcblk0p2 7.4G 7.3G 70M 100% /
tmpfs 38M 588K 37M 2% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 10M 0 10M 0% /dev
tmpfs 75M 0 75M 0% /run/shm
/dev/sda 917G 325G 546G 38% /media/Tera
/dev/mmcblk0p1 34M 11M 23M 33% /boot
tmpfs 187M 88K 187M 1% /var/log
tmpfs 100M 8.0K 100M 1% /tmp
//192.168.254.101/RaspberryPI 233G 211G 22G 91% /media/share
xbian@xbian / $
Quote:xbian@xbian / $ sudo du -s * --exclude=media | sort -n
du: cannot access `proc/4100/task/4100/fd/4': No such file or directory
du: cannot access `proc/4100/task/4100/fdinfo/4': No such file or directory
du: cannot access `proc/4100/fd/4': No such file or directory
du: cannot access `proc/4100/fdinfo/4': No such file or directory
0 dev
0 proc
0 sys
4 mnt
4 selinux
4 srv
8 tmp
24 root
540 lost+found
588 run
3692 etc
4528 opt
5656 bin
7164 sbin
11151 boot
43364 lib
244156 home
287820 var
483412 usr
xbian@xbian / $
adding the biggest directories I am hardly near to 8G.
I found in the forum an user which had the same issue and I copied the command line he used:
Quote:xbian@xbian / $ sudo find // -xdev -type f -size +10000000c -exec ls -ladh {} \;
-rw-r--r-- 1 xbian xbian 16M May 2 20:40 //home/xbian/.xbmc/addons/skin.metropolis/media/Steampunk.xbt
-rw-r--r-- 1 xbian xbian 114M May 2 20:41 //home/xbian/.xbmc/addons/skin.metropolis/media/Textures.xbt
-rw-r--r-- 1 xbian xbian 148M May 2 20:32 //home/xbian/.xbmc/addons/packages/skin.metropolis-2.6.3.zip
-rwxr-xr-x 1 root staff 16M Mar 18 08:50 //usr/local/lib/xbmc/xbmc.bin
-rw-r--r-- 1 root root 34M May 28 17:08 //var/lib/apt/lists/partial/mirrordirector.raspbian.org_raspbian_dists_wheezy_main_binary-armhf_Packages
-rw-r--r-- 1 root root 34M May 28 17:08 //var/lib/apt/lists/partial/mirrordirector.raspbian.org_raspbian_dists_wheezy_main_binary-armhf_Packages.decomp.FAILED
-rw-r--r-- 1 root root 34M May 27 17:08 //var/lib/apt/lists/mirrordirector.raspbian.org_raspbian_dists_wheezy_main_binary-armhf_Packages
-rw-r--r-- 1 root root 125M Jan 1 1970 //var/swapfile
-rw-r--r-- 1 root root 18M May 28 19:05 //var/cache/apt/pkgcache.bin
-rw-r--r-- 1 root root 18M May 28 17:38 //var/cache/apt/srcpkgcache.bin
xbian@xbian / $
Apparently there are no reason for my sd to be full.
I also checked and the partition is already resized to maximum.
Any help? I'm drowning here...
Try a sudo apt-get clean, there seems to be a lot of content in your /usr folder
did it, i went from 37M free to 72M free:
Code:
xbian@xbian / $ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 7.4G 7.3G 72M 100% /
/dev/mmcblk0p2 7.4G 7.3G 72M 100% /
tmpfs 38M 376K 38M 1% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 10M 0 10M 0% /dev
tmpfs 75M 0 75M 0% /run/shm
/dev/mmcblk0p1 34M 11M 23M 33% /boot
tmpfs 187M 52K 187M 1% /var/log
solved: it was a cronjob that tries to write a full sd backup on a network share. if the network is not available the cronjob creates the file on a directory with the same name of the mountpint, then when the network share is available again the file is hidden.
(29th May, 2013 06:13 AM)effemmeffe Wrote: [ -> ]solved: it was a cronjob that tries to write a full sd backup on a network share. if the network is not available the cronjob creates the file on a directory with the same name of the mountpint, then when the network share is available again the file is hidden.
do a test before you do the backup. you can test for mountpoint existence like this:
mountpoint -q /path/to/network_mount || { echo "network not available"; exit 1; }
this way the script will exit without trying to backups if the network share is not mounted.
( ... nicer output "du -xhd1 /" -x will not descent into different filesystem (mount), -h human readable numbers (G/M/K), -d deepness level)