Difference between revisions of "Thread:Talk:BeagleBone Black Extracting eMMC contents/Out of space with dd"

From eLinux.org
Jump to: navigation, search
m
m
 
Line 1: Line 1:
with some BBB's we have no problem restoring an older angstrom image with dd (Angstrom image uncompressed is 2.1GB) . Image was creating with dd from running system.However,, anyone know why even using this script that some fail with "out of spsace" . Yes, the image is compressed as well. Is the only option to recreate the iamge and bring the image down to < 2 GB ?  Its just odd that it restores the image on some devices w/out issue.
+
with some BBB's we have no problem restoring an older angstrom image with dd (Angstrom image uncompressed is 2.1GB) . Image was creating with dd from running system.However,, anyone know why even using this script that some fail with "dd: writing '/dev/mmcblk1': No space left on device" . Yes, the image is compressed as well. Is the only option to recreate the iamge and bring the image down to < 2 GB ?  Its just odd that it restores the image on some devices w/out issue.

Latest revision as of 05:42, 20 February 2015

with some BBB's we have no problem restoring an older angstrom image with dd (Angstrom image uncompressed is 2.1GB) . Image was creating with dd from running system.However,, anyone know why even using this script that some fail with "dd: writing '/dev/mmcblk1': No space left on device" . Yes, the image is compressed as well. Is the only option to recreate the iamge and bring the image down to < 2 GB ? Its just odd that it restores the image on some devices w/out issue.