Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Determine partitions sizes in cloning with selective down-sizing
1 view
Skip to first unread message
AndyHancock
Jan 12, 2012, 2:36:53 AM1/12/12
to
The 640GB HDD in my Toshiba Satellite came with 4 partitions. I am
trying to clone them to a smaller 500GB Momentus XT HDD all using
Norton Ghost 15. I will have to shrink partition 2, which is the
mostly-empty C-drive (and the overwhelmingly largest partition).
Ghost's Copy Drive can do this in the cloning so I don't have adjust
partitions in the source HDD. However, I assume that I need to
partition the target HDD with partition sizes equal to the source HDD
except for the smaller partition 2, then clone one partition at a
time. I will use Disk Management (diskmgmt.msc) to do this.
In partitioning the target HDD, however I'm at a bit of a loss as to
how to find the precise partition sizes of the partitions on the
source HDD. Diskmgmt.msc only shows the 4 partition sizes on the
source HDD to a limited precision, (2 decimal places in GiB). I used
PowerQuest Partition Table Editor (PTEDIT32.EXE) to show a whole bunch
of data about the partitions, and one field is "Sectors", which seems
like the number of sectors in each partition. As a sanity check,
partition 2 has 1,173,360,640 sectors. At 512 bytes/sector, that's
600.76 GB. This compares well with diskmgmt.msc's 559.5 GiB
(Windows's "GB" is actually a GiB, or 2 to the power of 30, which
multiples with 559.5 to give 600.76 GB actual).
1) Is this the right way to determine the precise partition sizes in
the source HDD so that I can replicate their sizes in the target HDD
(with the exception of partition 2)?
2) Since I want partition 2 to fill up the remaining space, can I
somehow define partition 2 last (and still have it as partition 2)?
3) If I have can't do #2, then I have to explicitly calculate the
smaller size of partition 2 based on the unallocated space and the yet-
to-be-defined partitions 1,3,4. Does of partition of some size "x"
use up precisely "x" amount of unallocated space, or is there some
overhead?
4) Can anyone explain the following discrepancy between the target HDD
capacity shown on diskmgmt.msc and PTEDIT32.EXE? Diskmgmt.msc shows
465.76 GiB (limited precision), which is about 500.11 GB, which makes
sense for a 500 GB HDD. However, PTEDIT32.EXE shows 476,937 MB.
Thanks!
P.S. I'm running Windows 7 Professional 64-bit.
trying to clone them to a smaller 500GB Momentus XT HDD all using
Norton Ghost 15. I will have to shrink partition 2, which is the
mostly-empty C-drive (and the overwhelmingly largest partition).
Ghost's Copy Drive can do this in the cloning so I don't have adjust
partitions in the source HDD. However, I assume that I need to
partition the target HDD with partition sizes equal to the source HDD
except for the smaller partition 2, then clone one partition at a
time. I will use Disk Management (diskmgmt.msc) to do this.
In partitioning the target HDD, however I'm at a bit of a loss as to
how to find the precise partition sizes of the partitions on the
source HDD. Diskmgmt.msc only shows the 4 partition sizes on the
source HDD to a limited precision, (2 decimal places in GiB). I used
PowerQuest Partition Table Editor (PTEDIT32.EXE) to show a whole bunch
of data about the partitions, and one field is "Sectors", which seems
like the number of sectors in each partition. As a sanity check,
partition 2 has 1,173,360,640 sectors. At 512 bytes/sector, that's
600.76 GB. This compares well with diskmgmt.msc's 559.5 GiB
(Windows's "GB" is actually a GiB, or 2 to the power of 30, which
multiples with 559.5 to give 600.76 GB actual).
1) Is this the right way to determine the precise partition sizes in
the source HDD so that I can replicate their sizes in the target HDD
(with the exception of partition 2)?
2) Since I want partition 2 to fill up the remaining space, can I
somehow define partition 2 last (and still have it as partition 2)?
3) If I have can't do #2, then I have to explicitly calculate the
smaller size of partition 2 based on the unallocated space and the yet-
to-be-defined partitions 1,3,4. Does of partition of some size "x"
use up precisely "x" amount of unallocated space, or is there some
overhead?
4) Can anyone explain the following discrepancy between the target HDD
capacity shown on diskmgmt.msc and PTEDIT32.EXE? Diskmgmt.msc shows
465.76 GiB (limited precision), which is about 500.11 GB, which makes
sense for a 500 GB HDD. However, PTEDIT32.EXE shows 476,937 MB.
Thanks!
P.S. I'm running Windows 7 Professional 64-bit.
0 new messages