RIS Hangs after entering OS details

[Jim Watts]

Hi,

I've a RIS problem that i don't know how to start diagnosing. The systems
i'm trying to build are DELL PowerEdge 2650's. They boot from the PXE
enabled Broadcom NetExtreme gigabits cards successfully, and start the RIS
process. I enter the system name into the RIS screens etc, and choose the
operating system. (I've tried Win2000 Pro, XP, 2000 Server and 2003 Server).
I get though the warning about wiping the disk, and get shown the machine
name and GUID details. Then when i press enter, i briefly see the 'waiting
for reboot' message, and then the system hangs. It never starts the actual
windows install.

I'm guessing that the system doesnt get sent the bootstrap code, but i've no
idea why. All other types of system build happily from the RIS server in
question, which is running Win2000 SP4. To check that the target server is
actually supported, i've done manual and unattend.txt builds on it, and
these builds find the Broadcom card, install the drivers and work fine.

Has anybody seen any examples of RIS builds hanging here?. Where should i
start looking, PXE client, network?

Many thanks
--
Jim Watts,
Technology Consultant
Directories, Authentication and Border Security
Information Systems Services
University of Southampton

 

[Shawn Shepherd [MSFT]]

Jim,

This may be of some value:

Copied the Perc3di 2.7-1 drivers to the following directories:

\I386\INF
perc2.inf
perc2mgt.inf

\I386\SYSTEM32
perc2evt.exe
perc2cin.dll

\I386\SYSTEM32\DRIVERS
perc2.sys
perc2hib.sys

Added the following Plug and Play IDs to the TXTSETUP.SIF.

PCI\VEN_1011&DEV_0046&SUBSYS_13659005 = "perc2"
PCI\VEN_1028&DEV_000A&SUBSYS_01061028 = "perc2"
PCI\VEN_1028&DEV_000A&SUBSYS_011B1028 = "perc2"
PCI\VEN_1028&DEV_000A&SUBSYS_01211028 = "perc2"
PCI\VEN_9006&DEV_2140&SUBSYS_21409006 = "perc2"

Changed the layout.inf from:

perc2.sys = 1,,27296,,,,4_,4,1,,,1,4
perc2hib.sys = 1,,5504,,,,4_,4,1,,,1,4

to:

perc2.sys = 1,,33360,,,,4_,4,1,,,1,4
perc2hib.sys = 1,,6128,,,,4_,4,1,,,1,4

I then commented out the following lines in the Winpeoem.sif since we're
manually
adding the drivers:

;[OemDriverParams]
;OemDriverRoot=""
;OemDriverDirs=perc3di

(2) Downloaded the following files from
(http://www.compaq.com/support/files/server/us/download/13437.html) and
sent them
to Alex

Compaq Smart Array 5x Controller Driver For Windows 2000
Version 5.40.2.0 (29 Apr 02)


Shawn Shepherd[MSFT]
MCSE2000/MCSA
Online Support Professional

This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! - www.microsoft.com/security

 

[Jim Watts]

This can't be right for a RIS build (or i'm missing something important).
The \INF and \SYSTEM32\DRIVERS folders dont exist on a RIS share
(reminst\Setup\English\Images\w2003std.sp0\i386), nor does the TXTSETUP.SIF.

Thanks for the help, and i'm sure that it is on the right lines (i.e. the
image doesnt have the drivers for the DELL hardware) but i need to know how
to get them into a RIS build

Many thanks
Jim
--
Jim Watts,
Technology Consultant
Directories, Authentication and Border Security
Information Systems Services
University of Southampton

 

[Shawn Shepherd [MSFT]]

Jim,

I'll look into this further, you might need to contact service delivery,
but let me check again. I'll get back to you shorly.

Shawn Shepherd[MSFT]
MCSE2000/MCSA
Online Support Professional

This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! - www.microsoft.com/security

 

[Melb]

For RIS to pick Mass Storage drivers you need to perform the following:

Open your ristndrd.sif file under templates folder in your image directory

now add the following flags:

[MassStorageDrivers]
"Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers" = "OEM"

[OEMBootFiles]
perc2.sys
perc2hib.sys
perc2.cat
oemsetup.inf
perc2mgt.inf
perc2cin.dll
Txtsetup.oem

Edit the txtsetup.oem file and comment out any reference to the .dll extenstion in the Files.Scsi section.

Copy the above files in the $OEM$\Textmode folder (except the .dll) under your image folder

for example win2k\$OEM$\Textmode

Also add the following $1\$$\system32\<filename.dll> under the $OEM$ folder

This is the .dll file from the list above.

As fas as the Broadcom NIC support is concerned copy the .cat, .inf, .sys files into the i386 folder in your image. Stop & start the BINL service. This will create the .PNF file required by RIS. You should now be able to run the RIS client install.

Good luck