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: ubuntu-1159f4dbbd369d693a371b78c9df7550531ba346b20ade297214ff4c7c7eb7ad.delta-ubuntu-5f4806a2d26af9d26279d1e66d217281dfa19219a85d2fd64999460f47d6efb9.tar.xz
tar: write error: No space left on device
E:Ubuntu update failed
fw_upgrade_finish
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.
From last_log_r:
e2fsck 1.41.14 (22-Dec-2010) platform/ mtk-msdc. 0/by-name/ system: 64906/132192 files (0.2% non-contiguous), 523388/528128 blocks 1159f4dbbd369d6 93a371b78c9df75 50531ba346b20ad e297214ff4c7c7e b7ad.delta- ubuntu- 5f4806a2d26af9d 26279d1e66d2172 81dfa19219a85d2 fd64999460f47d6 efb9.tar. xz mmcblk1p1) mmcblk1p1 (No such file or directory); trying /dev/block/mmcblk1 logs/recovery] logs/recovery]
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/
Applying update: ubuntu-
tar: write error: No space left on device
E:Ubuntu update failed
fw_upgrade_finish
Slowly SD retry failed (/dev/block/
W:failed to mount /dev/block/
E:failed to mount /sdcard (No such file or directory)
E:unknown volume for path [/sdcard2/
E:unknown volume for path [/sdcard1/
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.