← Back to team overview

ubuntu-phone team mailing list archive

Re: OTA 11 doesn't appear to install (probably)

 



On 02/06/16 14:35, Sergio Schvezov wrote:
You can also check `/android/cache/recovery/last_log` right after trying
the update or the general `log` file.
we have a winner! that file ends with:


progress: 5367
progress: 5371
progress: 5374
progress: 5378
tar: write error: No space left on device
progress: 5379
I:Ubuntu update complete
Ubuntu update complete.

so, I ran out of disk space, which is odd, because I think I have 3.8GB free, I have a ton of file systems mounted, but no real idea which one it is attempting to write to, and how much space each one should have, or how much space it requires to do an update.

phablet@ubuntu-phablet:/android/cache/recovery$ df -h
Filesystem Size Used Avail Use% Mounted on
udev                                         479M  4.0K  479M   1% /dev
tmpfs                                         97M  340K   96M   1% /run
/dev/mmcblk0p7                               4.4G  900M  3.3G  22% /userdata
/dev/mmcblk0p6                               2.0G  2.0G     0 100% /
/dev/loop0 141M 139M 1.8M 99% /android/system
none                                         4.0K     0  4.0K   0% /android
tmpfs 481M 4.0K 481M 1% /etc/fstab /dev/disk/by-path/platform-mtk-msdc.0-part5 688M 198M 491M 29% /android/cache none 4.0K 0 4.0K 0% /sys/fs/cgroup
tmpfs                                        481M   28K  481M   1% /tmp
cgmfs 100K 0 100K 0% /run/cgmanager/fs
none                                         5.0M     0  5.0M   0% /run/lock
none                                         481M  112K  481M   1% /run/shm
none                                         100M     0  100M   0% /run/user
tmpfs                                        481M     0  481M   0% /media
tmpfs 481M 4.0K 481M 1% /var/lib/sudo tmpfs 97M 44K 97M 1% /run/user/32011 tmpfs 97M 0 97M 0% /run/user/0 /dev/mmcblk1p1 1.9G 794M 1.1G 42% /media/phablet/9016-4EF8





References