Master Boot Record Not Written to Mirrored Shadow Partition

Last reviewed: May 5, 1997
Article ID: Q117131

The information in this article applies to:

- Microsoft Windows NT Advanced Server version 3.1 - Microsoft Windows NT Server versions 3.5 and 3.51 - Microsoft Windows NT Server versions 4.0

SYMPTOMS

After you make the previously shadowed partition of a mirrored system partition into the primary partition, when you restart your computer, it stops responding (hangs). Only the initial system and peripheral BIOS startup text is displayed on the monitor.

CAUSE

Windisk is the utility that manages disk partitioning in Windows NT Server. When it establishes a mirrored partition on a previously unused disk, it does not check for the existence of valid boot code in the Master Boot Record. At startup, the system BIOS of an Intel 80x86-based computer expects the Master Boot Record to contain executable code which is responsible for locating and passing control to the boot sector on the active partition. When this code is not present, the processor attempts to execute random memory and the computer hangs.

NOTE: If the disk used to hold the shadow of the mirrored system partition was previously partitioned, either by Windows NT Server, MS-DOS, or any other operating system which uses the same partitioning scheme, the Master Boot Record will already contain valid boot code and the system will boot successfully when started from the former shadow partition. Only when the secondary disk was not previously partitioned will this result in your computer hanging.

WORKAROUND

Through the use of a Windows NT "boot floppy", the operating system can still be initialized. For information on how to create such a floppy, see pages 161 and 162 of the "Windows NT Advanced Server Concepts and Planning Guide," or see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q119467
   TITLE     : Creating a Boot Disk for an NTFS or FAT Partition

It is possible to initialize the boot code in the Master Boot Record by using WINDISK.EXE to modify the disk partition structure. When you manually make and format a primary partition Windisk.exe will initialize the master Boot Records boot code.

STATUS

Microsoft has confirmed this to be a problem in Windows NT Server. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: prodnt repair tshoot fdisk mbr
Keywords : kbbug3.10 kbother ntboot ntfault
Version : 3.1 3.5 3.51 4.0
Platform : WinNT


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 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.