Winpe 2.1 and Windows 2003 R2 x32 and x64

[Cherie.Watts]

Hi

I have a problem when I create partitions with winpe 2.1 and format NTFS to perform an unattended installation of Windows 2003 R2 with i386.

When the server reboots I get a "A disk read error occurred".

When I first started I came across this error and fixed it by applying KB931761 and using Bootsect to set the boot sector for ntldr, not a problem. However originally I chose FAT32 and configured Win 2003 to convert to NTFS to avoid any possible NTFS version/compatibility complications between winpe 2.0(Vista) and 2003 etc...

Now I have upgraded to Winpe 2.1 and the servers have to have partitions that are 65Gb and hence can't use FAT32 any longer. Every time I have attempted this the server boots with the "A disk read error occurred".

I have run bootsect in almost all it's variations, ie /nt52 with all, c:, SYS and including the /force switch. None of which have made any difference. I have run secinspect whilst in winpe 2.1 before and after each command and there is no change at all to the mbr or the bootsector on the partition.

I downloaded mbrfix.exe and gave it a run as well, with no success.

However if I change the partition size and format with FAT32, everything works like a charm.

I have read and looked at heaps of sites. I understand that this has been covered by heaps of people but I haven't read a solution that fits my problem...I have tried most solutions I have read.

I would really appreciate it if someone has a solution or can give me a direction to go in.

Most Appreciated

[leen2]

We use the second method detailed in KB931761, change the registry as follows:

1. Click Start, click Run, type Regedit, and then click OK.

2. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\VDS\ALIGNMENT

3. On the Edit menu, point to New, and then click DWORD value.

4. Type LessThan4GB as the new entry name.

5. Right-click LessThan4GB, and then click Modify.

6. In the Edit DWORD Value dialog box, click Decimal.

7. In the Value data box, type 0, and then click OK.

8. Repeat steps 3 through 7 to add the following registry entries:

Between4_8GB

Between8_32GB

GreaterThan32GB

Each registry entry must have a value of 0.

9. Exit Registry Editor.

We actaully have these settings made by script, but it works for us.

[Cherie.Watts]

Hey

Thanks for the reply..unfortunately I already have the registry entries loaded. I implemented them the first time I came across the problem.

Any other thoughts?

I can post the MBR produced with secinspect...I haven't had to go to this level previously and hence I don't really understand what I am looking at. Although I can identify information in some of the Hex code.. ie the OS and disk signature

I just can't help thinking it just shouldn't be this difficult, there has to be a simple solution..and I am missing it.

Cheers

[IcemanND]

post our diskpart script or steps

[Cherie.Watts]

Hey

The steps are

1. PXE Boot winpe 2.1 image

2. Delete any existing Virtual Disk on the RAID controller and create new VDs

3. Run Diskpart /s script file

list disk

Select disk 0

clean

create partition primary size=65000

select partition 1

active

format FS=NTFS Label="System" QUICK

4. Copy OS files to C drive

5. Copy Raid Controller and NIC driver files into the OS installation files

6. Copy unattended.txt and post OS installation scripts to c:

7. Kick off unattended installation

c:\w2k3r2\i386\winnt32.exe /syspart:c: /unattend:C:\netinst\unattend.txt

8. Run Bootsect.exe

bootsect /NT52 All /force

Then reboot.

I have also tried

bootsect /NT52 SYS /force

bootsect /NT52 c: /force

With and without the /force switch.

Thanks

C

[IcemanND]

try running bootscet /nt52 c: right after you format the drive.

[jaclaz]

Let's first thing "separate" the issues.

The "error messages" in the MBR and PBR are (usually):

http://www.msfn.org/board/error-0xc000000e...90120&st=25

And Vista MBR has not changed AFAIK:

http://www.multibooters.co.uk/mbr.html

Thus we need to find out from where

"A disk read error occurred"

comes. Or maybe you reported it not EXACTLY ?

Bootsect.exe "fixes" the bootsector or PBR, you can run it all the times you want and using all the parameters in the world , but it WON'T touch the MBR (Master Boot Record).

Since using the "FAT32 first"/"convert after" worked, could it be some form of problems between the "normal" XP/2003 NTFS filesystem and the "enhanced" Vista/2008 one?

Is there a reason why you need to use PE 2.1 to deploy/install Server 2003 instead of using a PE 1.x or a bartPE/WinbuilderPE based on the same 2003?

jaclaz

[Tripredacus]

I've also had difficulty getting an unattended XP from running off the hard drive in this way. I am not sure if I had the same error as you, but I tried multiple different steps. In my case, my "OS files" were a WIM capture of the C drive after the Text Mode reboot.

I didn't research the issue any further, but I figured that this idea would work.

Where did you get your OS files from and/or how did you prepare them?

[Cherie.Watts]

Hi

I think my source is OK as I can build fine if I format with FAT32.

But in answer the source is off Microsoft CDs, Windows 2003 R2 SP2.

Cheers

[Cherie.Watts]

I will go check out your links to see if there is anything that could help.

But in answer...I know the current version of the bootsect.exe doesn't rewrite the MBR...I tried to get my hands on the version released with AIK 1.1 (I believe it's this version) as it does write the MBR as well...but no luck on this.

As to the idea that NTFS could be the culprit...yeah I have been thinking along these lines...that there is a difference in the Vista version and windows 2003...but I haven't found anything to support this idea.

As to why I am using Winpe2.1....firstly...why not.

Wasn't version 1.1 only for OEM providers?? I thought version 2.0 was the first release for general usage...but I am not certain of this.

As for Bartpe versus Winpe..I guess I thought that the microsoft product would have more inherent support and less compatibility issues

[jaclaz]

I will go check out your links to see if there is anything that could help.

As for Bartpe versus Winpe..I guess I thought that the microsoft product would have more inherent support and less compatibility issues

I guess that you are finding, the hard way, that your thought might not be completely true.

I was suggesting that the problem might not really be WinPE as opposed to bartPE, but rather later release of core OS files vs. previous ones.

WinPE 1.x, as well as bartPE's and XP/2003 based winbuilder projects can use the SAME OS files as the build you are trying to install, thus you won't have compatibility problems.

If I had suggested you VistaPE:

http://www.boot-land.net/forums/index.php?showforum=51

or

http://www.boot-land.net/forums/index.php?...ic=4431&hl=

http://www.boot-land.net/forums/index.php?...ic=7053&hl=

as a replacement to WinPE 2.1, your concerns might (but they do not actually ) be justified.

Completely unrelated, actually the opposite, but FYI:

http://www.boot-land.net/forums/index.php?showtopic=2280

If you try building a "simple" 2003 based PE, like one using the "preconfigured" LiveXP:

http://www.boot-land.net/forums/index.php?showtopic=4111

using the same source as the one you are installing/deploying, you can easily find out if using the 2003 diskpart and format solves the issue or not (and then maybe it could be something hardware specific )

However, you can use MBRFIX or MBRWIZ to check/change the MBR CODE or DATA:

http://www.sysint.no/nedlasting/mbrfix.htm

http://mbrwizard.com/

jaclaz

Edited February 16, 2009 by jaclaz

[Cherie.Watts]

Hey

The solution suggested by IcemanND, worked. Which is totally awesome and most appreciated.

Thanks heaps for everyones suggestions

Happy Building

Cherie