On Fri, Jul 1, 2016 at 1:38 AM, <[email protected]> wrote: > Hi, > > So I'm working with a modified version of Robert Nelson's flasher script > (https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/bbb-eMMC-flasher-eewiki-ext4.sh). > I am flashing debian, but I'm having issues with corrupt results. > > The main differences are: > > - It does some things specific to my application, like performing a few web > requests. > - Instead of just creating one partition, it creates the root/boot > partition, and a second read-write partition. > > The partition table looks like this: > > Formatting: /dev/mmcblk1 > > Disk /dev/mmcblk1: 119808 cylinders, 4 heads, 16 sectors/track > Old situation: > New situation: > Units: 1MiB = 1024*1024 bytes, blocks of 1024 bytes, counting from 0 > > Device Boot Start End MiB #blocks Id System > /dev/mmcblk1p1 * 1 1500 1500 1536000 83 Linux > /dev/mmcblk1p2 1501 3743 2243 2296832 83 Linux > /dev/mmcblk1p3 0 - 0 0 0 Empty > /dev/mmcblk1p4 0 - 0 0 0 Empty > Successfully wrote the new partition table > > Re-reading the partition table ... > > - It was originally based on an older version of the script, however, some > parts have been updated. The EEPROM flashing for instance, has been upgraded > to the current version of RCN's script. > > > The program flow of dd_bootloader -> sfdisk -> format -> rsync is still the > same as in RCN's script. > > The problem: > Sometimes (only sometimes, and not with a predictable pattern that I can > discern), the flashing will fail and produce an unbootable image. > When the flasher will produce a corrupt image, errors in rsync's attempts to > copy over files to the root file system occur, just after the ext4 > filesystems for both partitions have been created. > > Here is an example: > Copying: /dev/mmcblk0p1 -> /dev/mmcblk1p1 > mount /dev/mmcblk1p1 /tmp/rootfs/ -o async,noatime > rsync: / -> /tmp/rootfs/ > [ 432.938083] EXT4-fs error (device mmcblk1p1): ext4_mb_generate_buddy:757: > group 0, block bitmap and bg descriptor inconsistent: 32768 vs 23112 free > clusters
Most often, these ext4's errors are actually due to power fluctuations. They seem to happen more often when powering via USB, but i've seen it happen via a 5v DC supply too. Or if a cape is installed that is sharing the eMMC pins'. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhVuD-Ekcx1L3Nx0xP_zw5ZWNEGcKpP0KFZ8vEb7XnhVw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
