Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


Microsoft Deployment Toolkit 2013 Error Deploying to RAID cluster

Posted on 2014-02-28
Medium Priority
Last Modified: 2016-12-08
I am currently attempting to deploy Server 2008 R2 Datacenter on a RAIDed drive pair, using MDT 2013.

I am unable to select the option to leave the existing drive structure intact, which is what I used to do when dealing with a RAID drive MDT deployment.

I have injected the RAID driver into the WIM already, but it is still showing  18 errors and 1 warning when I start the deployment.

The error reported are;

Dish(0) was not found. Unable to continue. - Possible Cause: Missing Storage Drive (this error appears twice)

FAILURE (7711): Disk OSDiskIndex(0) can not be found! Litetouch Deployment failed, Return code = -2147467259 0x0004005 (this error appears twice)

Failed to save environment to (80070057)

Failed to run the action: Format and Partition Disk

Unknown error (Error: 80004004; Source: Windows)

The Execution of the group (preinstal) has been aborted. An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Format and Partition Disk. Execution of task sequence failed.

Unknown error (Error: 00001E1F; Source: Unknown)

Task sequence engine failed! Code: exExecutionFail

Task sequence failed with error code 80004005.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Anyone have any idea how I can get around this?
Question by:Mdamon808
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
  • 3
LVL 18

Assisted Solution

by:Mike T
Mike T earned 750 total points
ID: 39896869

You need the RAID drivers in both the OS WIM and the boot WIM (in WinPE). All the errors above are because WinPE does not recognise the disk and can't do anything with it.

LVL 83

Assisted Solution

by:David Johnson, CD, MVP
David Johnson, CD, MVP earned 750 total points
ID: 39897111
are the raid drivers ALSO in the litetouch boot files... it is winpe that has control of the disk until the first reboot.

Author Comment

ID: 39901031
I have the raid drivers in both the MDT 2013 and the Windows Deployment Server (images attached).

The driver listed is the one that should apply to the RAID controller on the server, but there are others I can try. I will load the rest of the available drivers and see if makes a difference.
Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  


Accepted Solution

Mdamon808 earned 0 total points
ID: 39901444
All drivers listed on the Dell site, for the machine in question, have been loaded into the Windows Deployment Server and the MDT 2013 driver set. But the server is still producing the same error messages.

I am injecting the drivers into the LitetouchDeployment.exe. If that doesn't work I will be out of ideas.
LVL 83

Expert Comment

by:David Johnson, CD, MVP
ID: 39902031
did you update your deployment share after adding the drivers and which selection did you use in the drivers area of the properties of the deployment share?  Did you after updating the deployment share copy the litetouch .iso's into wds boot area and update wds?
LVL 18

Expert Comment

by:Mike T
ID: 39902242

I always verify that drivers work before going near MDT. Have you tried just booting into WinPE and manually testing the bcraid driver using drvload?

If that works, then it ought to work in MDT too but I did Google this and found someone saying they have version 11.0 and only 11.2 worked, direct from Intel in their case.

The other way I tested RAID drivers for HP workstations in the past was to boot from the gold DVD and provide that drivers manually as explained here:
which leaves no room for doubt whether it's a good driver or not.

If you are 100% sure you have the right driver then check you don't have it excluded in MDT profiles and Update the deployment share. You can check the driver file is there once you boot into PE, or, use DISM

Dism /Mount-Image /ImageFile:C:\test\images\boot.wim /Name:"Windows Drive" /MountDir:C:\test\offline
Dism /Image:C:\test\offline /Get-Drivers

Finally, for the HP workstations, they needed RAID drivers in both the boot.wim file AND the injected later in the deploy OS phase. It was the same driver both times. All the above applies to only the boot.wim that MDT generates.


Author Comment

ID: 39909951
Actually I am trying to inject the drivers into the LiteTouchPE_x64.WIM file, so I am trying to inject into the PE (I have backups of the original that I am using). I have successfully loaded the drivers into the MDT and the WDS.

I have confirmed that I am using the correct drivers, and I have downloaded new versions of the drivers three times now. So either the drivers on the site have been bad for nearly a week, or they are fine and the issue is somewhere else.

When I attempt to inject the drivers by right clicking the .wim and selecting "Add driver packages to image..." it fails with error code: 0xc0000135.

I have just tried injecting them via DISM.exe with no luck either.

I have attached the DISM log data. If you look, you will see the same error code: 0xc0000135 in the logs as well.

Can someone take a look and see if they have any idea why this is failing? I can't find anything relevant to my situation on the interwebs. Everything I can find relates to Server 2012.

I haven't posted deployment server stats yet so here they are in case it matters;

Server 2008 R2 Datacenter running on VMWare 5.5. 2x 2Ghz processor, 4GB RAM, 2x 100 GB HDD (Thick Partitioned). Don't know if any of that matters, but better not to leave anything out.
LVL 18

Expert Comment

by:Mike T
ID: 39910174

Just thought - if you installed Windows on that VM previously did you add this driver and see it happy in device manager? That is the other acid test I apply and is usually where I start.
For boot drivers then I guess I would resort to manually checking first as above.

Anyway, that's the theory. I just found another clue elsewhere in your log that someone saw:
Failed to load the image session from the temporary location:C:\Users\usadmin\AppData\Local\Temp\52EE9EA1-6159-4715-ADF4-9E89099A3901 - CDISMManager::CreateImageSession(hr:0xc0000135)

DISM uses the C drive to do all the work, so I've seen machines run out of space by filling the C drive when working on a large WIM update - never a good idea.

The other possibility is permissions to that path - you can check if the path above exists to show if it is permissions. Either way, the easy work-around is to use DISM's /SCRATCHDIR option:

Dism.exe /Online [/LogPath:path_to_log_file] [/LogLevel:n] [/Quiet] [/NoRestart] [/ScratchDir:path_to_scratch_directory]

Ref: DISM command line and give it a big drive with everyone permissions applied.

Error 135 seems to be "process cannot be initiated"

I hope that works. I'm running out of ideas otherwise!


Author Comment

ID: 39910407
I think I may have caused a bit of confusion in my last post. The deployment server is the VM. It is not using the raid drivers as VM's drive management is performed by VMWare rather than the server itself.

The driver in question is for a Dell PowerEdge R210 II server, and I have confirmed that it is the correct driver for my specific machine with Dell.

The path in the DISM command does exist, I know because I created it. It is located on the C: drive and has no restrictions on it. Drive space shouldn't be an issue either as there is still 47.2GB of space still available on C: and the .wim in question is only just over 1GB.

The .wim being mounted is actually on the E: drive rather than C:. Do you think that could be having an effect?

I will give your command line a shot and I will let you know the results.
LVL 18

Expert Comment

by:Mike T
ID: 39910841

Yes - I'm totally confused what VMware is doing here but let's ignore it. I can't see it's relevant.

To re-cap
You have a physical Dell server
It has a RAID card with physical drives already setup in RAID
You have a driver: Dell inc. SCSIAdapter, v2.0.0.0162, bcraid.inf
Dell have told you, categorically, that is the driver to install the OS with?

I don't think having the OS WIM on E makes any difference at all.
LVL 83

Expert Comment

by:David Johnson, CD, MVP
ID: 39910926
boot into winpe on the system. use shift f10 to get a command prompt bring up diskpart list disk is your hard drive accessible? if not then you need to go back rebuild your winpe and if you are using WDS add the litetouch.iso  as the boot.iso

Author Closing Comment

ID: 39948396
Unable to inject the required raid drivers but that is a different issue.

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The question appears often enough, how do I transfer my data from my old server to the new server while preserving file shares, share permissions, and NTFS permisions.  Here are my tips for handling such a transfer.
Windows Server 2003 introduced persistent Volume Shadow Copies and made 2003 a must-do upgrade.  Since then, it's been a must-implement feature for all servers doing any kind of file sharing.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question