Greetings, Clint Olsen! > I'm also interested in generating images to preserve the entire disk. > What I'm wondering is whether doing this on a live system through > Cygwin would produce a safe, bootable disk image or if the the APIs > that Cygwin has to use or having the disk mounted would make this > unreliable?
Bootable? Likely. Safe? not even in the slightest. And as Eric pointed out, this has nothing to do with Cygwin. > A friend speculated that dd might complain about open files or > some-such thing. You don't have files on a block device level. >.< Tell your friend to speculate something better. > I went and tried it on /dev/sda and it seemed to work > without complaining. With conv=noerror ? I'm wondering, what did you expect? > Example: > $ dd if=/dev/sda of=/path/to/NAS/sda.img bs=512 conv=noerror,sync bs=4k at least. NTFS uses 4k clusters by default, there's no reason to use smaller chunks to read it. Actually, even bigger chunks may greatly speed up the read. conv is just bogus. You are trying to create a mess of the image with these options. You don't want any padding. You don't want errors ignored. Writing disk image to NAS uncompressed is even more questionable. Consider piping it through some archiver. > It would be great if something like this would work since dd is so > ubiquitous that I could restore a drive in a number of ways and not > lock me into something proprietary. It wouldn't work. Not directly. For a number of reasons. If you still intend to do it, at the very least consider using ERUNT for registry snapshots. That will let you have a consistent registry copy even if the one in image would turn up damaged. -- With best regards, Andrey Repin Thursday, September 3, 2015 04:50:29 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
