As I’ve mentioned in previous posts, I tend to image an entire harddisk before wiping it and then destroying it. I do this because, sometimes, I need to access data from that harddisk after I’ve already destroyed it.

Usually, after I’ve mounted the relevant partition of the harddisk image I’m interested in, I’ll use the incedibly handy rsync to make a perfect copy of the data from the image. Today, I encountered an unusual error when I tried using rsync to copy some data from an old HFS+ partition:

todd@debian: ~$ rsync -avHAX /mnt/hfsplus_partition/Users/ mediaserver@mediaserver4:/mediatank/dd_images/mbp_laptop_sda1/
sending incremental file list
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(605) [sender=3.0.9]

Turns out, there’s some kind of incompatibility between rsync‘s -H, -A, and/or -X and an HFS+ parition mounted in read-only mode. Since I didn’t care about preserving hard links, ACLs, or extended attributes, I just removed those arguments and was able to get the data I needed:

todd@debian: ~$ rsync -av /mnt/hfsplus_partition/Users/ mediaserver@mediaserver4:/mediatank/dd_images/mbp_laptop_sda1/

Comments are closed.