linaro-android-media-create can't burn Android on mx53loco

Bug #837191 reported by Spring Zhang
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linaro Image Tools
Invalid
Undecided
Unassigned

Bug Description

on 11.08 release, can't burn Android image on i.MX53loco, it will wait a long time and won't quit.

Log:
$ sudo linaro-android-media-create --dev iMX53 --mmc /dev/sdc --system system.tar.bz2 --boot boot.tar.bz2 --userdata userdata.tar.bz2
====================================================================
            linaro-android-media-create is EXPERIMENTAL

 The command line parameters as well as the distribution format will
 be changed and we will not keep backward compatibility for the
 current version here.
====================================================================

I see...
Device Mount point Size
/dev/sda none 238475MB
/dev/sda1 none 51200MB
/dev/sda2 none 80009MB
/dev/sda3 none 107262MB
/dev/sda5 / 55309MB
/dev/sda6 /home 41958MB
/dev/sda7 /var 6087MB
/dev/sda8 none 3906MB
/dev/sdc none 3780MB
/dev/sdc1 none 3MB
/dev/sdc2 none 128MB
/dev/sdc3 none 256MB
/dev/sdc4 none 3392MB
/dev/sdc5 none 255MB
/dev/sdc6 none 511MB
/dev/sdc7 none 2623MB
/dev/sr0 none 0MB
Are you 100% sure, on selecting [/dev/sdc] (y/n)? y
Checking that no-one is using this disk right now ...
OK
Warning: bad partition start (earliest 794625)
end of partition 4 has impossible value for cylinders: 1023 (should be in 0-1022)

Revision history for this message
Fathi Boudra (fboudra) wrote :

I'm not able to reproduce with linaro-image-tools 2011.08-0ubuntu1~linaro2, using the following commands:
$ wget --no-check-certificate http://releases.linaro.org/platform/linaro-n/android/11.08/leb-imx53/boot.tar.bz2 http://releases.linaro.org/platform/linaro-n/android/11.08/leb-imx53/system.tar.bz2 http://releases.linaro.org/platform/linaro-n/android/11.08/leb-imx53/userdata.tar.bz2
$ sudo linaro-android-media-create --mmc /dev/sdb --dev iMX53 --system system.tar.bz2 --boot boot.tar.bz2 --userdata userdata.tar.bz2

Could you retry with another SD card?

Changed in linaro-image-tools:
status: New → Triaged
Revision history for this message
Mattias Backman (mabac) wrote : Re: [Bug 837191] [NEW] linaro-android-media-create can't burn Android on mx53loco

I can't reproduce the error either.

> end of partition 4 has impossible value for cylinders: 1023 (should be in 0-1022)

This looks strange, then end of the extended partition seems to be
invalid. Could you try to use --image_file instead of --mmc and see if
the resulting image file would fit on the sd card you're using?

Also testing with another card as Fathi suggests would be good.
Perhaps format the one you're using and make sure that you can use the
full size of the card?

Revision history for this message
Spring Zhang (qzhang) wrote :

I doubt it's card problem, it's a new card

Revision history for this message
Zach Pfeffer (pfefferz) wrote :

All the same would you try a different card. Also would you send details about the card you're using?

Revision history for this message
Spring Zhang (qzhang) wrote :

It's not related with SD card but my host machine, it can't finish parted a USB device. After reboot, it also has the issue.

Revision history for this message
Spring Zhang (qzhang) wrote :

the burning is successful after changing host even if there is warning "end of partition 4 has impossible value for cylinders: 1023 (should be in 0-1022)"
Thanks for your help

Revision history for this message
Fathi Boudra (fboudra) wrote :

Set status to invalid as it isn't l-i-t issue.

Changed in linaro-image-tools:
milestone: none → 2011.08
status: Triaged → Invalid
Revision history for this message
Irvin Sirotic (irvin-sirotic) wrote :

I experienced same issue. After correcting cylinder/head/sector parameters according to the link bellow, i was able to burn image without problems

http://www.omappedia.org/wiki/Android_SD_Configuration#Step_by_Step_Instructions_to_format_SD_card

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.