Comment 14 for bug 1568889

From last_log_r:

e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/mtk-msdc.0/by-name/system: 64906/132192 files (0.2% non-contiguous), 523388/528128 blocks
Applying update:
tar: write error: No space left on device
E:Ubuntu update failed
Slowly SD retry failed (/dev/block/mmcblk1p1)
W:failed to mount /dev/block/mmcblk1p1 (No such file or directory); trying /dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:unknown volume for path [/sdcard2/logs/recovery]
E:unknown volume for path [/sdcard1/logs/recovery]
Ubuntu update complete.
I:Ubuntu update complete.

So it looks like the partition is out of space. I wonder if that could be the cause of the AssertionError in the client, possibly because either udm isn't noticing the ENOSPACE and returning a success code anyway?

Take a look at /android/cache/recovery. Delete any big .xz files (and the associated .asc files) you find there and try again. But maybe there just isn't enough space available if the updates are big enough. In that case, delete those files again and try forcing a full update, e.g. `system-image-cli -b 0 -vv` to see if those are small enough to fit in the available space.