Repartitioning Corrupts Partition Table

Last reviewed: May 8, 1997
Article ID: Q103102

The information in this article applies to:
  • Microsoft Windows NT operating system, version 3.1
  • Microsoft Windows NT Advanced Server, version 3.1

Disk Administrator (and the FDisk engine it shares with Setup) writes partition table information to the disk based on the disk's Cylinder-Head- Sector geometry. For SCSI disks, this geometry is invented by the driver, rather than being an inherent property of the disk. Windows NT follows a relatively standard method of using a geometry that produces 1-Megabyte tracks. However, other systems (or SCSI disks run with BIOS) can use different geometries.

When a disk with multiple partitions is taken from one system to another that uses a different geometry, repartitioning it with Disk Administrator can cause the partition table to become corrupt. This problem occurs because Disk Administrator aligns all partitions on track boundaries based on the current disk geometry. If the partition table entry for an existing partition is rewritten with a new starting offset, the data on that partition becomes inaccessible.

You can avoid or correct this situation by editing the partition table to set the partition starting sector and length back to its original value. You can use the BIOS Parameter Block (BPB) in sector one of the physical volume to determine the geometry, or you can use sector zero of the partition, which also contains a BIOS Parameter Block, to find the starting sector offset.


Additional query words: prodnt
Keywords : kbtool ntutil
Version : 3.1
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.