Integrate the RAID drivers with WSIN, and configure UEFI partitions?

Pergunta Integrate the RAID drivers with WSIN, and configure UEFI partitions?

  • domingo, 8 de abril de 2012 20:47
     
      Contém Código

    I want to integrate the chipset and mass storage drivers for my brand new Intel x79 system at install time, and set up the partitions and basic directories. I was hoping to make my Windows 7 installation easier by creating an AutoUnattend.xml file. There are a number of “complications” for my hardware:

    1. The mass storage drivers and chipset drivers are not available in my Windows 7 (pre-service-pack) install media.
    2. The system is UEFI, so I need the EFI, the reserved, and the OS partitions on the first drive.
    3. There are multiple drives.

    Using Windows System Image Manager 6, I loaded install.wim, but I could not create a catalog, even though everything is 64bit. I skipped that by copying the “install_Windows 7 PROFESSIONAL.clg” from the DVD. Maybe that is the heart of my problems, but it does not seem so. I created a DistributionShare and a new answer file.

    The next problem seems to be the biggest. I copied the Intel ACHI drivers into Out-of-Box Drivers\AHCI, and created a PathAndCredentials entry for it. But the WinPE installer always stops, and demands that I browse to, and load the mass storage drivers. I believe this is messing up all the subsequent stages of my install attempts. Hence my question, how do I integrate the mass storage drivers at install time?

    After I manually load the iaStor drivers, I get the partitions interface. No matter what I do here, (delete all existing partitions, ignore them, format, any combination of these) the install fails with “Cannot perform operation on partition” or currently, "Windows could not prepare the partition selected for installation". What I WANT, is to wipe both drives, create the correct partitions, and modify the OS and data partitions. I need them to be C and D respectively, or I cannot install applications. I have changed and checked the DriveIds and PartitionIds for my CreatePartition and ModifyPartition items.

     The oddest thing I have discovered is that my first DiskID must be 1, instead of 0, else the install aborts with “Cannot find Drive”. Here is my latest, still failing, configuration, that attempts to modify an existing Drive2 partition.

     
                <DiskConfiguration>
                    <Disk wcm:action="add">
                        <DiskID>1</DiskID>
                        <WillWipeDisk>true</WillWipeDisk>
                        <CreatePartitions>
                            <CreatePartition wcm:action="add">
                                <Order>1</Order>
                                <Size>400</Size>
                                <Type>EFI</Type>
                            </CreatePartition>
                            <CreatePartition wcm:action="add">
                                <Order>2</Order>
                                <Size>128</Size>
                                <Type>MSR</Type>
                            </CreatePartition>
                            <CreatePartition wcm:action="add">
                                <Order>3</Order>
                                <Extend>true</Extend>
                                <Type>Primary</Type>
                            </CreatePartition>
                        </CreatePartitions>
                        <ModifyPartitions>
                            <ModifyPartition wcm:action="add">
                                <Format>FAT32</Format>
                                <Label>ESP</Label>
                                <Active>true</Active>
                                <Order>1</Order>
                                <PartitionID>1</PartitionID>
                            </ModifyPartition>
                            <ModifyPartition wcm:action="add">
                                <Order>2</Order>
                                <PartitionID>2</PartitionID>
                            </ModifyPartition>
                            <ModifyPartition wcm:action="add">
                                <Format>NTFS</Format>
                                <Label>System_WIN_7</Label>
                                <Letter>C</Letter>
                                <Order>3</Order>
                                <PartitionID>3</PartitionID>
                            </ModifyPartition>
                        </ModifyPartitions>
                    </Disk>
                    <WillShowUI>OnError</WillShowUI>
                    <Disk wcm:action="add">
                        <DiskID>2</DiskID>
                        <WillWipeDisk>false</WillWipeDisk>
                        <ModifyPartitions>
                            <ModifyPartition wcm:action="add">
                                <Format>NTFS</Format>
                                <Label>USERS</Label>
                                <Letter>D</Letter>
                                <Order>1</Order>
                                <PartitionID>1</PartitionID>
                            </ModifyPartition>
                        </ModifyPartitions>
                    </Disk>
                </DiskConfiguration>
    

     Any help would be greatly appreciated.


    • Editado Charlweed domingo, 8 de abril de 2012 21:55
    •  

Todas as Respostas

  • domingo, 8 de abril de 2012 21:50
     
     
    Actually, it is important to note that I DID get past "cannot perform operation on partition", when I used only modify items for disk1. However, that install failed with a "Unexpected Error" after boot.
  • quarta-feira, 11 de abril de 2012 09:18
     
     
    Please check the following Microsoft articles:
    Create an Answer File for UEFI-based Computers
    http://technet.microsoft.com/en-us/library/cc765950(v=ws.10).aspx

    Walkthrough: Build an Answer File for UEFI-based Computers
    http://technet.microsoft.com/en-us/library/dd744565(WS.10).aspx

    Thanks
    Zero

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • sábado, 14 de abril de 2012 05:02
     
     

    Just checking if you need our further assistance.


    Thanks
    Zero

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • domingo, 15 de abril de 2012 17:16
     
     

    I already read and followed technet article.

    I have verified there are bugs in Windows System Image Manager, or the installer when used with the answer file. WSIM gets confused in my system when there are multiple hard-drives. WSIM confuses the drive ID,s and tries to perform operations specified for one drive, on a different drive. It also messes up the drive letters, and writes the wrong boot target into the UEFI boot table. In particular, by boot drive is C:, but the boot table entry specifies drive F:

    This is easily reproducible on my Gigabyte GA-x79-UD7 motherboard with 4 hard drives and a DVD drive on the Intel x79 C600 RAID controller.

  • terça-feira, 17 de abril de 2012 11:20
     
     
    1. Could you please remove some additional disk settings, just leave one disk settings and try it again?
    2. Change the disk ID back to 0.

    Thanks
    Zero

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.