Thread history
From Talk:BeagleBone Black Extracting eMMC contents
Viewing a history listing
Viewing a history listing
| Time | User | Activity | Comment |
|---|---|---|---|
| 06:08, 12 March 2015 | Jkridner (talk | contribs) | New reply created |
(Reply to restore: No space left on device) |
| 04:43, 20 February 2015 | Jeddonix (talk | contribs) | Changed subject from "Out of space with dd " to "restore: No space left on device" |
|
| 04:42, 20 February 2015 | Jeddonix (talk | contribs) | Comment text edited |
|
| 04:39, 20 February 2015 | Jeddonix (talk | contribs) | Comment text edited |
|
| 04:39, 20 February 2015 | Jeddonix (talk | contribs) | New thread created |
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.
