Closed Bug 1217583 Opened 10 years ago Closed 8 years ago

Flame FOTA getting stuck before launching recovery (not wiping cache correctly)

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::System
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: kairo, Unassigned)

Details

When the first FOTA was provided to Flame now, I had my device download and uncompress it, then go into the "System update" screen (the Gaia one) but never actually reboot into recovery and applying the FOTA. I could only get out of this state by long-pressing the power button and forcing a reboot that way. Having the possibility of getting into this state is probably its own bug, I should get back to the running system when the actual update can't be started. I tried the same process again with adb logcat running and saw those lines: E/librecovery( 210): Unable to create recovery directory "/cache/recovery": No space left on device I/Gecko ( 210): -*- RecoveryService: Error: FOTA install failed. Trying again after clearing cache. E/librecovery( 210): Unable to create recovery directory "/cache/recovery": No space left on device I/Gecko ( 210): -*- RecoveryService: Error: FOTA install failed again E/GeckoConsole( 210): [JavaScript Error: "uncaught exception: 2147500037" {file: "jar:file:///system/b2g/omni.ja!/components/nsUpdateService.js" line: 3108}] I/Gecko ( 210): *** AUS:SVC UpdateService:applyOsUpdate - Error: Couldn't reboot into recovery to apply FOTA update /mnt/media_rw/sdcard/updates/fota/update.zip I/GeckoConsole( 210): AUS:SVC UpdateService:applyOsUpdate - Error: Couldn't reboot into recovery to apply FOTA update /mnt/media_rw/sdcard/updates/fota/update.zip I/Gecko ( 210): UpdatePrompt: Update error, state: applied, errorCode: 83 E/GeckoConsole( 210): [JavaScript Error: "formatURLPref: Couldn't get pref: app.update.url.details" {file: "jar:file:///system/b2g/omni.ja!/components/nsURLFormatter.js" line: 145}] I/Gecko ( 210): UpdatePrompt: Setting gecko.updateStatus: Install Failed I/Gecko ( 210): *** AUS:SVC getFileFromUpdateLink linkFile.path: /data/local/updates/0/update.link, link: /mnt/media_rw/sdcard/updates/0/update.mar I/GeckoConsole( 210): AUS:SVC getFileFromUpdateLink linkFile.path: /data/local/updates/0/update.link, link: /mnt/media_rw/sdcard/updates/0/update.mar I/GeckoDump( 210): XXX FIXME : Got a mozContentEvent: update-prompt-apply-result The first 4 lines there pointed me to the actual issue: We found the space in /cache to be too little and tried to clear it, but still had too little space, which I found strange. So I did this: root@flame:/ # df Filesystem Size Used Free Blksize /dev 451.7M 132.0K 451.6M 4096 /sys/fs/cgroup 451.7M 0.0K 451.7M 4096 /mnt/asec 451.7M 0.0K 451.7M 4096 /mnt/obb 451.7M 0.0K 451.7M 4096 /system 412.0M 267.1M 144.9M 4096 /data 2.0G 270.2M 1.8G 4096 /cache 70.8M 22.4M 48.4M 4096 /persist 4.9M 4.0M 852.0K 4096 /firmware 64.0M 31.7M 32.2M 16384 /storage/sdcard 3.8G 101.5M 3.7G 4096 /storage/sdcard1 3.5G 299.1M 3.2G 4096 /mnt/media_rw/sdcard 3.8G 101.5M 3.7G 4096 /mnt/media_rw/sdcard1 3.5G 299.1M 3.2G 4096 You see, that /cache still has space filled. I looked into that and saw that a cache2 directory with a date from two months ago was still there (obviously not deleted by this process) with all kinds of cache files in it. I deleted it myself: root@flame:/ # rm -rf /cache/* After this, I could install the FOTA without issues. So, 1) somehow, we seem to be trying to clear the cache but not do it correctly, and 2) if we fail there, we get the whole phone stuck on this update screen in Gaia.
QA Whiteboard: FOTA → [FOTA Issues]
I am pretty sure I remember similar issues reported and fixed on Dolphin ... ?
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.