[Bug 1568889] Re: OTA and u-d-f fail if image is too big for the system partition

Alan Bell alanbell at ubuntu.com
Fri Jun 3 10:11:07 UTC 2016


after flashing over USB I have this

phablet at ubuntu-phablet:/$ df -h
Filesystem                                   Size  Used Avail Use% Mounted on
udev                                         479M  4.0K  479M   1% /dev
tmpfs                                         97M  348K   96M   1% /run
/dev/mmcblk0p7                               4.4G  840M  3.4G  20% /userdata
/dev/mmcblk0p6                               2.0G  1.6G  392M  81% /
/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   12M  677M   2% /android/cache
none                                         4.0K     0  4.0K   0% /sys/fs/cgroup
tmpfs                                        481M  2.1M  479M   1% /tmp
cgmfs                                        100K     0  100K   0% /run/cgmanager/fs
none                                         5.0M     0  5.0M   0% /run/lock
none                                         481M  7.6M  473M   2% /run/shm
none                                         100M     0  100M   0% /run/user
tmpfs                                        481M     0  481M   0% /media
tmpfs                                        481M  8.0K  481M   1% /var/lib/sudo
tmpfs                                         97M   48K   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

phablet at ubuntu-phablet:/$ sudo du -sh *
129M	android
6.7M	bin
4.0K	boot
0	cache
206M	custom
0	data
4.0K	dev
7.3M	etc
0	factory
0	firmware
429M	home
33M	lib
4.0K	lost+found
788M	media
4.0K	mnt
191M	opt
0	persist
du: cannot access ‘proc/948/task/1554/fdinfo/74’: No such file or directory
du: cannot access ‘proc/948/task/1554/fdinfo/77’: No such file or directory
du: cannot access ‘proc/20526/task/20526/fd/4’: No such file or directory
du: cannot access ‘proc/20526/task/20526/fdinfo/4’: No such file or directory
du: cannot access ‘proc/20526/fd/4’: No such file or directory
du: cannot access ‘proc/20526/fdinfo/4’: No such file or directory
0	proc
12K	root
4.7M	run
7.2M	sbin
4.0K	srv
0	sys
0	system
2.1M	tmp
76M	userdata
1.1G	usr
260M	var
0	vendor

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1568889

Title:
  OTA and u-d-f fail if image is too big for the system partition

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  New
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  On Meizu MX4 upgrade from OTA-9.1 to OTA-10 fails.
  Upgrade downloads normally, phone restarts and starts system upgrade and after a while it freezes with strange icon (small microchip with red sign on it)

  When you turn off the phone and start it again it still presents itself as OTA-9.1 and again it founds and offer upgrade.
  Anyway some changes from OTA-10 seems to be applied, because I can see design changes, copy function in web browser etc.

  It's reproducible on my phone any time I try to upgrade. If I can help
  with output of some log, or anything else, please let me know.

  Well described here by Lars Kristian Wichmann Hansen:
  http://askubuntu.com/questions/754963/upgrade-meizu-mx4-ubuntu-edition-to-ota-10-fails

  * u-d-f case described in bug 1582325

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1568889/+subscriptions



More information about the foundations-bugs mailing list