Thanks Robert, I assume when using rsync method that you boot the BBB's eMMC that you want to clone and then run the "beaglebone-black-make-microSD-flasher-from-eMMC.sh" script as opposed to executing script after booting up from a SD card - is this correct?
If so, what about any changes to 'source' files while running rsync? Can this not be an issue as you are syncing a live system - this is one of the reasons why I thought it best to boot from a SD card first. I do like the idea rsync vs dd for exact issue I am experiencing. ~Colin On Thursday, June 11, 2015 at 3:13:14 PM UTC-5, RobertCNelson wrote: > > On Thu, Jun 11, 2015 at 3:04 PM, Colin Bester <bester...@gmail.com > <javascript:>> wrote: > > After backing up eMMC contents to SD card and then restoring via method > > similar to mentioned in > > http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents, booting > from a > > SD card and using dd to write to eMMC I have issue with failed write > with > > error "Out of disk space" being reported. > > > > Firing up two Rev C cards, one from Mouser and one from Element14 show > > following differences running fdisk /dev/mmcblk0 > > > Disk /dev/mmcblk0: 3925 MB, 3925868544 bytes > > > Disk /dev/mmcblk0: 3867 MB, 3867148288 bytes > > One's probally Micron, other Kingston... > > You can try resizing the *.img manually with gparted and other tools. > > This is why i prefer the rsync approach vs dd... > > 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
