Re: Using Drive Image to adjust space?

"Rod Speed" wrote:
Terry Pinnell wrote:
Rod Speed wrote
Terry, UK 

Happy to report my approach proved successful. These were steps:

1) Copied C:\Documents and Settings\Janet\My Documents to
G:\C-MyDocs\My Documents to reduce size of C: by about 3GB, and
provide another backup in addition to one made automatically last
night of entire C:\Documents and Settings.

2) Installed PM 7.0 and made Rescue Diskettes. (I'd previously done
chkdsk on C: and G:)

3) With PM, resized 38GB C: partition to about 8GB. That was the
step I was most nervous about, but it went smoothly as you'd
suggested. (Note that I could *not* do this in DI as I'd thought
earlier.)

4) Used Drive Image 2002 to Copy Drive C: to F: That took a long
time but again went well.

5) Was then able to dual boot as desired!

6) Used PM 7 to resize C: back up to 38GB 

There was no need to do that, you could have just imaged
the C drive and produced the F drive from that image.


Ok, thanks. But can I just be sure I have it straight please. You're saying
use DI Create Image facility with C: as source and G: as destination,


Any destination with enough space for it, yes.

then Restore the image (PQI files) on G:,
but with F: as the destination, yes?


Yes.

But how does that get around F: being marginally too small? 

I doubt DI will see it as marginally to small in that situation,
as you said originally, its a bit bigger than it needs to be.

Wouldn't I have to resize it first anyway? 

Nope, should be fine. You said that there are 7G of files
in the C drive and that original size of the F drive was 8G.

If so, Copy Drive accomplishes the
objective in one operation, instead of two.


Correct, but that isnt one operation when you have to resize.
You avoid the resize by doing it via an image file.



       Notice, Terry, that Rod is saying "image file" and not "clone".
       This differentiating terminology is not used consistently from
       one copy utility to another, but at least here in this NG, an
       "image" is the entire contents of a partition formatted as a
       standard file and stored as a file for later "restoration" to a
       partition format on a HD.  "Clone" refers to the byte-for-byte,
       sector-by-sector duplicate of one HD partition in another HD
       partition.  (You can see why "clones" cannot be made to
       optical media since the optical media have an entirely different
       sector format.)

       I may be wrong, but I believe images are made file-by-file
       from the original partition, and thus they don't preserve the
       sector format and can ignore unused sectors and, in effect,
       "compress" the contents of the partition down to just the
       space necessary to contain the data.  Thus, in a two-step
       process, i.e. "imaging" and then "restoration", one could, in
       effect, "shrink" a partition (in transit) down to a smaller size.

*TimDaniels*
.

Relevant Pages

  • RE: Change Tracks Per Sector on system Partition
    ... mirroring system partitions of a cluster to an offsite SAN due to differing ... We cannot physically read the file system boot sector usually at ... If your software mirror a Windows NT/2000/2003 operating system partition ... another disk that is translated as 32spt, ...
    (microsoft.public.windows.server.setup)
  • Re: OT File recovery Software
    ... > I guess some of you never used the fix MBR command? ... > The Master Boot Record will be created when you create the first ... > partition on the hard disk. ... > first sector on the disk. ...
    (alt.med.fibromyalgia)
  • FreeBSD 4.4-REL to FreeBSD 4.8-STABLE upgrade problem.
    ... parameters extracted from in-core disklabel are: ... Figures below won't work with BIOS for partitions not in cyl 1 ... BIOS sector numbering starts with sector 1 ... The data for partition 1 is: ...
    (freebsd-questions)
  • FreeBSD 4.4-REL to FreeBSD 4.8-STABLE upgrade problem.
    ... parameters extracted from in-core disklabel are: ... Figures below won't work with BIOS for partitions not in cyl 1 ... BIOS sector numbering starts with sector 1 ... The data for partition 1 is: ...
    (freebsd-stable)
  • Re: usb hp floppy drive recognition fedora 4 installation
    ... >> Boot into Linux and copy the boot image from the first sector of your ... You'll want to take 512 bytes of this partition once, ... floppy device may be the SCSI device of 'sdc' or something else. ...
    (linux.redhat)