Closed Bug 1184980 Opened 4 years ago Closed 4 years ago
System partition size should be updated
As documented in bug 1085230 comment 12, we should use 439877632 (419.5*1024*1024).
The size of 419.5 comes from the output of gdisk on the gpt_bothO_big.bin.
Target Milestone: --- → FxOS-S3 (24Jul)
Comment on attachment 8635324 [details] [review] Flame KK PR Slightly concerned about people getting confused from this..
Attachment #8635324 - Flags: review?(mwu) → review+
We placed in the partitioning in the partition sector, we had not updated the system partition size; hence we still had the issue in bug 1181372 Made a build and flashed it. Build is located here: https://drive.google.com/a/mozilla.com/file/d/0B_0LdM1CVycIdWRLdUJkQ2lXb3c/view?usp=sharing You will need the latest contributor build flashed first : http://bit.ly/1NWi45L Output of adb shell df /system Filesystem Size Used Free Blksize /system 412.5M 209.5M 203.0M 4096
Comment on attachment 8635324 [details] [review] Flame KK PR see https://bugzilla.mozilla.org/show_bug.cgi?id=1184980#c3
Attachment #8635324 - Flags: feedback?(nhirata.bugzilla) → feedback+
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Chris, I think we should make it clear on MDN that users without the proper partitionning will not be able to flash system.img now :). The error they will get is: > Flashing out/target/product/flame/system.img failed because the image was too large. They should update base image in this case.
(In reply to Alexandre LISSY :gerard-majax from comment #6) > Chris, I think we should make it clear on MDN that users without the proper > partitionning will not be able to flash system.img now :). > > The error they will get is: > > Flashing out/target/product/flame/system.img failed because the image was too large. > > They should update base image in this case. Ok, so I've added a note to cover this at the bottom of the following section of the Flame guide: https://developer.mozilla.org/en-US/Firefox_OS/Phone_guide/Flame/Updating_your_Flame#Updating_your_Flame_to_a_nightly_build Is this ok?
That looks good to me :) Thanks !
I encountered a weird case. Bug 1214298. FYI.
You need to log in before you can comment on or make changes to this bug.