Just wondering, has anyone tried to restore an image using the reverse of this process? I can't seem to restore my "bricked" BBB. I would like to restore to my most recent backup so that I can get on with my thesis, but I'm struggling to get this working. I've tried the reversing the command, while booting the BBB from the microSD with an Ubuntu image, but /dev/mmcblk0p2 won't unmount.
Any help is much appreciated! Thanks, Mike On Wednesday, September 11, 2013 12:19:26 PM UTC-7, Michael Darling wrote: > > I finally got it to work by changing (creating) the ~/.ssh/config file on > my Mac to include the lines: > > ServerAliveInterval 300 > ServerAliveCountMax 3 > ClientAliveInterval 300 > ClientAliveCountMax 3 > > The transfer also seemed to occur much faster than what I was trying > before. Thanks for the tips anyways, Dale! > > > On Wed, Sep 11, 2013 at 11:11 AM, Dale Schaafsma > <[email protected]>wrote: > >> md5sum for the raw device won't be the same as for the running >> system...the only way you'd have a shot at having the md5's match is if you >> boot off of an SD card. Which actually is probably a better idea since a >> running system is going to modify the data you're trying to backup. >> >> You might want to make sure that your BBB & Mac are on a wired network, >> the broken pipe sounds like you're maybe seeing network drops? >> I'd also make sure that for each attempt that you're trying a new >> filename (more precisely a file that doesn't exist at the start of the dd). >> >> As a last resort, you can start trying to look at whether packets are >> streaming across correctly with wireshark/tcpdump. >> >> -Dale >> ps. this process worked ok for me going to a Debian laptop. >> >> On Wednesday, September 11, 2013 4:59:24 AM UTC-5, Michael Darling wrote: >> >>> I'm trying to do the same thing, but end up with the data transfer >>> stalling and eventually displaying an error message about a broken pipe. I >>> can confirm that no additional data is being transferred by running "ls -l >>> *.img" on my Mac and checking the size of the file in bytes. The size >>> grows with repeated calls, but eventually stops. If I try executing >>> anything in the BeagleBone terminal, the "dd" command returns with the >>> broken pipe error. >>> >>> I have made sure that my Mac is set up for Remote Login from System >>> Preferences -> Sharing -> Remote Login, and confirmed that I can "ssh" into >>> the Mac from the BeagleBone. >>> I am executing the following command from the BeagleBone: >>> >>> root@beaglebone:~# dd if=/dev/mmcblk0 bs=1M | ssh >>> [email protected] 'dd of=/Users/michaeldarling/ >>> Desktop/BBB_Angstrom_Backup.img bs=1m' >>> >>> >>> >>> Is it possible that the transfer was completed correctly? I end up with >>> a final byte size of 1,919,287,296 for BBB_Angstrom_Backup.img, but I am >>> not sure what size the file should actually be. I tried to compare md5sums >>> of the BBB_Angstrom_Backup.img and /dev/mmcblk0 but they do not match -- >>> should they? >>> >>> Any tips? >>> >>> On Friday, May 17, 2013 8:51:29 PM UTC-7, Duane Johnson wrote: >>>> >>>> Very helpful, thank you. >>>> >>>> SSHing to my Mac I had to alter the 1M to 1m: >>>> >>>> dd if=/dev/mmcblk0 bs=1M | ssh [email protected] 'dd >>>> of=/Users/duane/Desktop/origBBB.img bs=1m' >>>> >>>> >>>> On Sunday, May 12, 2013 6:59:07 PM UTC-6, Jason Stapels wrote: >>>>> >>>>> If you have access to a remote Linux / Mac system, you could use an >>>>> SSH pipe to dump the contents of the MMC. I don't have a board handy to >>>>> verify this, but it should work. >>>>> >>>>> (From the BBB) >>>>> $ sync ; dd if=/dev/mmcblk0 bs=1M | ssh user@local_ip 'dd >>>>> of=/path/to/image/myBBB.img bs=1M' >>>>> (Should ask for you for SSH password here, just enter it and press >>>>> enter) >>>>> >>>>> Be warned! This is kind of a hack. Try not to use the board while >>>>> you're dumping the image as it'll increase the risk of corrupted log >>>>> files. >>>>> Ideally, you should really be running those commands after booting from >>>>> the >>>>> SDCard so you know processes aren't trying to access the MMC while you're >>>>> trying to dump it. >>>>> >>>>> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "BeagleBoard" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/beagleboard/vnXk58eMaPc/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- 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/groups/opt_out.
