I've been using dd for a couple of years now, most of the time successfully. I usually use it to dd Linux images to USB drives. My workflow doing so is as such:
- convert
.isoimage to a.imgformat usinghdiutil convert -format UDRW output.img input.iso - unmount the drive using
diskutil unmountDisk /dev/diskX ddthe image to the drive usingdd if=./image.img of=/dev/rdiskX bs=1m
Lately, and namely since I upgraded to Yosemite, dd has been showing some weird behavior. When I specify the block-size flag (bs=1m), it quits after about a minute, showing the default successful write message with the numbers of records in/out and bytes transferred and all that. What you would expect on a successful write. The problem is, it writes just a very small part of the image, then quits.
When I do not specify the block-size flag dd behaves as expected, writing the image to the disk in the ordinary fashion. Does anyone have any idea why this is happening?
obs=1m– mikeserv Jun 25 '15 at 14:12cat. Not only is it guaranteed not to drop bytes randomly, it may even be faster. – Gilles 'SO- stop being evil' Jun 25 '15 at 22:42