Keep in mind that NAND has bad sectors. That is why they use NAND controllers. NAND size will vary from one part to another.
Gerald On Wed, Sep 9, 2015 at 10:28 AM, Robert Nelson <[email protected]> wrote: > On Wed, Sep 9, 2015 at 10:23 AM, Fohnbit <[email protected]> wrote: > > Hi! > > > > Maybe I found a problem. I put my Image on the uSD and flash again. The > Log: > > http://pastebin.com/HiZR9USh > > > > Here I see now: > > Running /dev/mmcblk0p1/autorun.sh...<\r><\n> > > dd: writing '/dev/mmcblk1': No space left on device<\r><\n> > > 0+115617 records in<\r><\n> > > 0+115616 records out<\r><\n> > > [ 373.638162] EXT3-fs (mmcblk1p2): error: couldn't mount because of > > unsupported optional features (240)<\r><\n> > > [ 373.649135] EXT2-fs (mmcblk1p2): error: couldn't mount because of > > unsupported optional features (244)<\r><\n> > > [ 373.660107] EXT4-fs (mmcblk1p2): bad geometry: block count 933632 > exceeds > > size of device (909056 blocks)<\r><\n> > > [ 373.673511] F2FS-fs (mmcblk1p2): Magic Mismatch, valid(0xf2f52010) - > > read(0x39180)<\r><\n> > > [ 373.681473] F2FS-fs (mmcblk1p2): Can't find a valid F2FS > > filesystem<\r><\n> > > mount: mounting /dev/mmcblk1p2 on /mnt failed: Invalid argument<\r><\n> > > /etc/init.d/S99autorun: /mnt/autorun.sh: line 12: ed: not found<\r><\n> > > umount: can't umount /mnt: Device or resource busy<\r><\n> > > <\r><\r><\n> > > Welcome to Buildroot<\r><\n> > > <\r>beaglebone login: > > > > This mean the eMMC is to small?? > > I made the Image from the element14 BBB with: > > #!/bin/sh > > echo timer > /sys/class/leds/beaglebone\:green\:usr0/trigger > > > > #un-comment the following line to perform a backup > > #dd if=/dev/mmcblk1 bs=16M | gzip -c > /mnt/BBB-eMMC-$RANDOM.img.gz > > > > #un-comment the following 6 lines to perform a restore (be sure to > replace > > XXXXX with your image name) > > gunzip -c /mnt/BBB-eMMC-2510.img.gz | dd of=/dev/mmcblk1 bs=16M > > UUID=$(/sbin/blkid -c /dev/null -s UUID -o value /dev/mmcblk1p2) > > mkdir -p /mnt > > mount /dev/mmcblk1p2 /mnt > > ed -i "s/^uuid=.*\$/uuid=$UUID/" /mnt/boot/uEnv.txt > > umount /mnt > > > > sync > > echo default-on > /sys/class/leds/beaglebone\:green\:usr0/trigger > > > > (of course comment the correct lines) > > > > Can someone confirm this? > > And when yes ... why I was able to flash the element14 BBB? > > Yes, relying on "all" 4GB eMMC's to be 100% the same size is not a > good "backup/flash" design. > > This is why the official images use rsync and not dd.. > > Here are 3 of the eMMC's used for bbb's.. > > #Micron 3744MB: 3925868544 bytes -> 3925.86 Megabyte > #Kingston 3688MB: 3867148288 bytes -> 3867.15 Megabyte > #Kingston 3648MB: 3825205248 bytes -> 3825.21 Megabyte > > All "sold" ad 4GB models.. When crafting a *.img i usually assume > "80%" of advertised space to play it safe.. > > 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]. > For more options, visit https://groups.google.com/d/optout. > -- Gerald [email protected] http://beagleboard.org/ -- 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]. For more options, visit https://groups.google.com/d/optout.
