Convert/Autoconv Fails with "Cannot Create Elementary File System Structures"

This article was previously published under Q191850
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
Conversion from FAT to NTFS fails and the following error message appears:

Cannot create the elementary file system structures.
The conversion failed
C: was not converted to ntfs
This error occurs on Alpha systems when performing an unattendedinstallation using the following options in the Unattend.txt file:
   [Unattended]   OemPreinstall = yes   FileSystem = ConvertNTFS   ExtendOemPartition = 1				
CAUSE
This problem only occurs if you apply the Alpha-based hotfix referenced inthe following article in the Microsoft Knowledge Base:

ARTICLE-ID: 185773
TITLE : NTFS Corruption on Drives > 4 GB Using ExtendOEMPartition
The ExtendOEMPartition option extends the partition to the maximum size ofthe drive. The above hotfix enables this feature so that it works correctlyon drives exceeding 4 GB in size. There is a BIOS limitation on x86-basedcomputers that limit the maximum size of a partition to 7.8 GB. Becausethis limitation does not exist on Alpha systems, the byte offset may exceed32 bits. A problem in Fastfat.sys fails any disk access that calculateda byte offset exceeding 32 bits.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

NOTE: This fix applies to both x86 and Alpha platforms and supercedes thehotfix referenced in the following article in the Microsoft Knowledge Base:

ARTICLE-ID: 185773
TITLE : NTFS Corruption on Drives > 4 GB Using ExtendOEMPartition
NOTE: In addition to the above file, the following additional files must beobtained from the latest Windows NT 4.0 Service Pack. The service packshould be of the same language as that being installed:
   x86           Alpha   --------------------------   Gdi32.dll     Gdi32.dll   Hal.dll       Halgammp.dll   Hal486c.dll   Halpinna.dll   Halapic.dll   Halrawmp.dll   Halast.dll    Halsabmp.dll   Halcbus.dll   Kernel32.dll   Halcbusm.dll  Ntdll.dll   Halmca.dll    Ntkrnlmp.exe   Halmps.dll    Ntoskrnl.exe   Halmpsm.dll   User32.dll   Haloli.dll    Win32k.sys   Halsp.dll     Winsrv.dll   Halwyse7.dll   Kernel32.dll   Ntdll.dll   Ntkrnlmp.exe   Ntoskrnl.exe   User32.dll   Win32k.sys   Winsrv.dll				

Perform the following steps to successfully install this hotfix:

  1. Start the computer in MS-DOS mode and prepare the drive for Windows NTunattended installation as usual. This includes copying the .\I386 or.\Alpha folder from the Windows NT CD to the install directory on driveC.
  2. Copy the fixed files into a temporary folder.
  3. Apply the fixed files and required service pack dependency files to theinstall directory on drive C. The service pack CD should be that of thesame language as that being installed. Because the service pack CDs arein Windows NT Unicode format, they cannot be read directly from MS-DOS.The service pack files may need to be transferred from a Windows NTsystem capable of reading the service pack CD or the service pack filescan be read directly using MS-DOS from the Enterprise Server CD in the"\SP3\i386" or "\SP3\Alpha" directory. The service pack dependency filesare listed above. This step can be performed automatically using theOemsetup.bat batch file if you have the dependency files in an MS-DOSreadable format. Otherwise, you must perform this step manually:

    Manual Instructions for the Intel Platform

    Batch File Option

    From the temporary folder, run Oemsetup.bat, specifying both the sourceservice pack folder and the target install folder. For example (assumeD: is a service pack folder and C:\I386 is the install folder):

    OEMSETUP D:\SP3\I386 C:\I386

    This copies the necessary files to the I386 and C:\I386\System32folders on drive C where the installation folder is located.

    Manual Option

    You can also perform this step manually by first copying Fastfat.sysfrom the fix to the C:\I386 install folder, and then copy the followingfiles from the latest Windows NT 4.0 service pack to the C:\I386 andC:\I386\System32 folders as denoted below:
          Fastfat.sys     -> ..\I386      Hal.dll         -> ..\I386      Hal486c.dll     -> ..\I386      Halapic.dll     -> ..\I386      Halast.dll      -> ..\I386      Halcbus.dll     -> ..\I386      Halcbusm.dll    -> ..\I386      Halmca.dll      -> ..\I386      Halmps.dll      -> ..\I386      Halmpsm.dll     -> ..\I386      Haloli.dll      -> ..\I386      Halsp.dll       -> ..\I386      Halwyse7.dll    -> ..\I386      Ntdll.dll       -> ..\I386 and  -> ..\I386\SYSTEM32      Ntoskrnl.exe    -> ..\I386      Ntkrnlmp.exe    -> ..\I386      Win32k.sys      -> ..\I386      User32.dll      -> ..\I386      Kernel32.dll    -> ..\I386      Gdi32.dll       -> ..\I386      Winsrv.dll      -> ..\I386						

    Then remove the compressed versions of these files from the C:\I386 andC:\I386\System32 folders. Compressed files are identified by the lastcharacter of the file type containing an underscore (_). For example,delete Fastfat.Sy_, Hal.dl_, Ntdll.dl_, Ntoskrnl.ex_, and so on.

    Manual Instructions for the Alpha Platform

    Batch File Option

    From the temporary folder, run Oemsetup.bat specifying both the sourceservice pack folder and the target install folder. For example (assumeD: is a service pack folder and C:\Alpha is the install folder):

    OEMSETUP D:\SP3\Alpha C:\Alpha

    This copies the necessary files to the Alpha and C:\Alpha\System32folders on drive C where the installation folder is located.

    Manual Option

    You can also perform this step manually by first copying Fastfat.sysfrom the fix to the C:\Alpha install folder then copy the followingfiles from the latest Windows NT 4.0 service pack to the C:\Alpha andC:\Alpha\System32 folders as denoted below:
          Fastfat.sys     -> ..\Alpha      Halgammp.dll    -> ..\Alpha      Halpinna.dll    -> ..\Alpha      Halrawmp.dll    -> ..\Alpha      Halsabmp.dll    -> ..\Alpha      Ntdll.dll       -> ..\Alpha and  -> ..\Alpha\SYSTEM32      Ntoskrnl.exe    -> ..\Alpha      Ntkrnlmp.exe    -> ..\Alpha      Win32k.sys      -> ..\Alpha      User32.dll      -> ..\Alpha      Kernel32.dll    -> ..\Alpha      Gdi32.dll       -> ..\Alpha      Winsrv.dll      -> ..\Alpha						

    Then remove the compressed versions of these files from the C:\Alpha andC:\Alpha\System32 folders. Compressed files are identified by the lastcharacter of the file type containing an underscore (_). For example,delete Fastfat.Sy_, Halgammp.dl_, Ntdll.dl_, Ntoskrnl.ex_, and so on.
  4. Run Winnt.exe as usual to complete the Windows NT installation.
  5. When the Windows NT installation is complete, apply the latest servicepack immediately. This eliminates inconsistent releases of systemfiles.
STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
corrupt user domain
Properties

Article ID: 191850 - Last Review: 12/05/2015 09:11:20 - Revision: 1.3

Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbqfe KB191850
Feedback
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)