On Saturday 11 Feb 2012 14:18:59 Ralph Corderoy wrote:
> I'd expect a recovery partition would already have compressed contents
> with high entropy so your compression is probably just burning CPU time
> and coming up with a slightly larger result; "Here's a large number of
> bytes that aren't compressed" followed by the original data. The
> exception to that may be the filesystem's data, but it's probably a
> small amount of the partition.
>
> Also, it sounds like you've made a filesystem in the destination
> partition and want the copy to appear there as a file or two. That
> filesystem will use up some of the partition's space for its own data,
> e.g. what you see with `ls -l', so to image a 1GiB partition to a file
> in a filesystem needs at least 1GiB of free space in that filesystem, as
> reported by `df'.
Right. So I definitely need a bigger target partition.
> Let me get this right, you want to an image of a partition split across
> two files so each can be burned to a DVD? Ensure the source partition
> is unmounted, we don't want it changing during the copy, then
Well. What I really wanted was one file that could be burnt to a single dual-
layer DVD. The Novatech disk creation program somehow does that, but it
invokes Windows burner, which throws up the error.
It sounds as if it might be easier to use the technique that you've suggested
and accept that I've got to span the image across two dual-layer disks. The
trouble is that I only have one left...
> dd can be used to copy back the image files into a partition. One word
> of caution, is everything need for recovery definitely in the one
> partition? No hidden bits around the disk anywhere? That would catch
> out PartedMagic as well, of course.
I think so, but who knows with Microsoft? It would seem stupid to me to rely
on a recovery strategy that may need files on the possibly damaged partition.
However, it is Microsoft that designed it.
--
Terry Coles
64 bit computing with Kubuntu Linux
--
Next meeting: Bournemouth, Tuesday 2012-03-06 20:00
Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/
New thread on mailing list: mailto:dorset@mailman.lug.org.uk
How to Report Bugs Effectively: http://goo.gl/4Xue
