Unsolved

This post is more than 5 years old

4 Posts

57087

May 16th, 2011 09:00

MDT2010 - Missing Operating System on 4k Drives

Anyone seeing this issue? Windows 7 MDT deployment onto 4k drive, upon first reboot, "missing operating system". Issue looks to be the BDE partition created by the ZTI script. Without using BDE partition, everything ok but you add the BDE (format tasks sequence), error returns. This is on both WD and Seagate drives.

*note: this is with AHCI set in BIOS, if you change it to RAID ON, then it will boot into Windows and continue with the build process**

1.1K Posts

May 19th, 2011 12:00

I haven't seen that scenario. Which Dell system are you testing on?

19 Posts

May 23rd, 2011 09:00

I had the same problem...I injected the MS hotfix KB982018 into my image using DISM then I was able to re-image the computer successfully.

hope this helps you out.

4 Posts

May 23rd, 2011 14:00

It was with either the E6420 or the E6410. Turns out that at least with the E6420, installing the recent release of Bios A03 fixed the issue. The E6410 will require a Bios fix as well.

4 Posts

May 23rd, 2011 14:00

thanks for your reply... elijefe357.... what model systems were you seeing this with?

19 Posts

May 24th, 2011 08:00

I was using the E6520. I was able to boot into MDT and choose an image, the image would load but would fail when trying to install drivers and completing the process. I searched for a couple of days for a fix and came across this article: http://myitforum.com/cs2/blogs/gramsey/archive/2011/05/02/dell-systems-and-advanced-format-hard-drives.aspx. and from there I injected the 982018 patch into the images and was able to complete imaging. If you need instructions on how to apply the updates with DISM...this site is helpful: http://msdn.microsoft.com/en-us/library/ff794819%28v=winembedded.60%29.aspx

We just got in a E6420 and a E6320 soon and I will let you know how it goes.

Good Luck

3 Posts

September 1st, 2011 15:00

I am facing the same issue when deploying a custom Windows 7 with SP1 image on Dell E5420 with Advanced Format drive. The Operating System installs but after the first reboot I get the error message “Missing Operating System”

Below Is the setup

1. MDT 2010 Update 1 with latest E5420 drivers imported in Out of Box drivers. (Latest SATA drivers too)

2. WAIK for Windows 7 (WinPE 3.0)

3. As per Dell site I have added KB982018 patch to both boot.wim and also the OS.WIM http://www.delltechcenter.com/page/Deploying+Dell+systems+with+Advanced+Format+Hard+Drives#fbid=CghFtPnx1VR

4. WDS to deploy
5. BIOS with AHCI on

I also have tried deploying without BDE partition (i.e DoNotCreateExtraPartition=YES in CS.ini), there is no issue when the machine reboots for the first time. When enabling Bitlocker after OS deployment, the machine reboots to create the BDE partition but it again fails with the same error "Missing Operating System"

The things I have not tried:

1. Update to WAIK for Windows 7 SP1 – (adding KB982018 to WinPE 3.0 should be sufficient right?)

2. Update BIOS


Windows 7 SP1 should ideally support AF drives but wondering what is happening. Any help???

1.1K Posts

September 6th, 2011 10:00

The BIOS update would be my first suggestion. Let us know if that has an effect.

19 Posts

September 6th, 2011 12:00

Sounds like the hotfix did not get applied correctly but I'm just guessing. I've been using MDT 2010 update 1, WinPE 3.0 and imaging Win7 SP1 on AF drives without issues for a while now. I did come across an article that applies the KB982018 hotfix automatically everytime you update the MDT share and rebuild the Litetouch ISO's. You can find the instructions here:
http://myitforum.com/cs2/blogs/cnackers/archive/2011/06/15/advanced-format-hard-drives-automatically-patching-winpe-3-0-with-the-microsoft-deployment-toolkit-2010-mdt.aspx
I would also verify that the custom OS WIM file is updated with the hotfix too.... One more thing, just for troubleshooting, try changing the drive in the BIOS to ATA and re-image it again.





3 Posts

September 6th, 2011 13:00

I tried updating the BIOS yesterday and it fixed the issue. I updated from A00 to A01 and it worked. I also verified with A02 as well.
Thank you guys

1.1K Posts

September 6th, 2011 15:00

kantzy,

Thanks for posting your solution. I'm sure others will run into the same issue.

3 Posts

September 7th, 2011 02:00

FYI: There are issues with Windows XP on AF drives and Microsoft does not support it. For the people who want to deploy Windows XP on AF drives below is some information.

I was able to successfully deploy Windows XP ghost image(.gho) using align=1mb Ghost32.exe command line switch. You need at least Ghost 11 or 11.5. Use can integrate Ghost to WinPE and deploy images using the command line switch.

I have verified the alignment on Windows XP using various methods like Paragon utility, StartingOffset/4096(WMIC partition list full) and Seagate tool.
Also, we had issues with Pointsec 6.3.1 encryption on XP. Once we reboot after the installation of Pointsec, the machine gets stuck at black screen just after Pointsec loading screen and XP does not load. Aligning the disk fixed the issue.

Hope it helps

8 Posts

February 1st, 2012 13:00

I have a E6420 and a M4600 both with 4K drives, erroring out during an MDT installation of Windows 7 x64 Enterprise SP1 with "Windows Setup could not configure Windows to run on this computer's hardware."  This happens right before the "Completing Installation" step of Windows Setup.

Same models with 512k drives work fine.

I have created the build from scratch on a 4K drive and installed patch KB98201 and the most recent Intel SATA drivers.  Fully patched machine from Windows Update.

I have added the KB98201 update to my PE WIM's.

I've alligned the drive with Paragon.

I captured the WIM

When I redeploy the WIM I get the above error on both peices of hardware.

BIOS is already up to date.

1.1K Posts

February 1st, 2012 15:00

What mass storage drivers are included in your WinPE?  Make sure you only have the latest version of Intel RST and not earlier ones.  This has caused issue with others.

I would recommend that you do not use the Paragon tool unless you have a deployed system that cannot be re-built using an AFHDD compliant deployment process.

8 Posts

February 2nd, 2012 09:00

For testing only the newest RST driver is in that selection profile.  Paragon was only used in one attempt to eliminate it as a possible cause.  Reading over this article, stealthfield.wordpress.com/.../microsoft-mdt-2010-sp1-512e-hard-drives-4k-hard-drives, it looks as if WAIK version might be the issue.  Going to try this next.

8 Posts

February 2nd, 2012 18:00

Well that didn't work.

I even went as far as to create a new distribution share, only put the M4600 drivers in it, and rebuilt everything from scratch.  Still failing at the same point.

0 events found

No Events found!

Top