P2950 Windows 2003 X64 Install cannot load raid drivers

Hi, you will have to create an image of Windows Server 2003 that contains the correct RAID drivers.  The easiest way to do this is to use nLite to extract the OS, slipstream the driver into your image then burn the image on to a disk.  I have added a guide, so all you will need to to is substitute Windows 2K3 for Windows XP.  If theres any issues let us know.

maxeasyguide.blogspot.com/.../preparations-for-winxp-installation-cd.html

Steve

2003 and XP cannot obtain driver files from media other than a floppy disk, which is by default drive letter 'A'.  If you can't use the floppy method at F6 (or don't want to ... and who could blame you), do as Steve suggests and use nLiteOS.com.  It is very easy to use and pretty much standard procedure for adding drivers to old operating systems nowadays.

Are you loading this via floppy?  If so, try a new floppy and/or fully formatting it before putting the files on it.  That is a common error when using poor floppies.

If you are not using a floppy, what is your PERC 5's firmware at (CTRL MGMT tab in CTRL-R utility)?

Thanks. Sorry for the delay.

After booting into the OS I keep getting  an error:

File:\percsas.sys caused an unexpected error (274) at line 2335 in d:\srvrtm\base\boot\setup\oemdisk.c.

It looks like the system is reading the wrong raid driver, but I can't figure out how to change it. The system has a PERC 5/I LSI raid controller and I am running SAS drives.

The current txtsetup file looks as follows: Can you tell me what I need to change and where? Thanks.

[Disks]

PERC_64 = "DELL PERC5 and PERC6/CERC6 RAID Controller Driver (Server 2003 for x64)", \percsas.sys, \

[Defaults]

# This section lists the default selection for each 'required'

# hardware component.  If a line is not present for a component,

# the default defaults to the first item in the [ ]

# section (see below).

#

# is one of computer, display, keyboard, mouse, scsi

# is a unique string to be associated

#   with an option.

scsi = PERC_64

[scsi]

# This section lists the options available for a particular component.

#

# is the unique string for the option

# is a text string, presented to the user in a menu

# gives the name of the key to be created for the component in

#   HKEY_LOCAL_MACHINE\ControlSet001\Services

PERC_64    = "DELL PERC5 and PERC6/CERC6 RAID Controller Driver (Server 2003 for x64)",percsas

[HardwareIds.scsi.PERC_64]

PERC_64 = "PCI\VEN_1028&DEV_0015&SUBSYS_1F011028", "percsas"

PERC_64 = "PCI\VEN_1028&DEV_0015&SUBSYS_1F021028", "percsas"

PERC_64 = "PCI\VEN_1028&DEV_0015&SUBSYS_1F031028", "percsas"

PERC_64 = "PCI\VEN_1000&DEV_0060&SUBSYS_1F0A1028", "percsas"

PERC_64 = "PCI\VEN_1000&DEV_0060&SUBSYS_1F0B1028", "percsas"

PERC_64 = "PCI\VEN_1000&DEV_0060&SUBSYS_1F0C1028", "percsas"

PERC_64 = "PCI\VEN_1000&DEV_0060&SUBSYS_1F0D1028", "percsas"

PERC_64 = "PCI\VEN_1000&DEV_0060&SUBSYS_1F111028", "percsas"

[Files.scsi.PERC_64]

driver  = PERC_64, percsas.sys, percsas

inf     = PERC_64, oemsetup.inf, percsas

inf     = PERC_64, nodev.inf

catalog = PERC_64, percsas.cat

[Config.percsas]

value=parameters\PnpInterface,5, REG_DWORD,1

value = "", Tag, REG_DWORD, 20

Why go through all the trouble of loading it bare metal without the drivers or creating nLite image when Dell has already done the leg work for you?

Get the Dell CD ISO - Dell Systems Build and Update Utility

You can use SBUU so long as it is not volume license media downloaded from Microsoft's oepen website AND your 2003 media has SP2 on it.

I have yet to see VL media fail with SBUU 6.5. I did an install last week with VL media....

I don't think I've tried 2003 since 5.5 or 6.1, so the issues there may have been fixed.

I have yet to see any VL media fail with using SBUU even all the way up to 2008 R2. Despite the service packs not being listed with the OS using the latest and greatest still works even using 2003 R2 when it only lists 2003.

The SBUU is going to be the easiest way to ensure all drivers will work.

However, the PE2950 has a 'Floppy Emulation" feature in the BIOS. If you change the USB detection mode from Auto to Floppy, you can add the drivers to a USB drive and it will be read as if it were a floppy.

S-i-i-i-i-h. All I want is to load Windows 2003 X64. I tried the slipstream process with nlite. I couldn't get it to work. Tried the USB process - doesn't work.  I'm back to the floppy. On the textsetup.oem file I have changed the PERC_32″ to “scsi = PERCsas. On the F6 procedure on the WIndows 2003 CD install, the floppy loads the drivers, but I still get the percsas.sys error (273). I want to stay with the floppy procedure as this has at least gotten me to where the system is attempting to load the raid drivers. Any help would be appreciated.

I am a very frustrated camper.

Just to make sure ... this should be the driver you are using:

Depending on your PERC 5/i firmware, though, you may need to use an older version ... maybe this one:

When using nLiteOS.com, you will choose the Multiple Driver Files option, select ALL the drivers presented, then use TextMode.

Is this 2003 R2 or non-R2?

What SP level is your 2003 media?

U can use "USBKeyPrepF6" this software to boot from win2k3 disk ...after plugin the thumb drive...when its says to hit F6, press it then load ur raid driver. Instruction inside the read me.txt file inside the software.

http://ftp.us.dell.com/utility/USBKeyPrepA00.exe

Follow this link:: http://en.community.dell.com/support-forums/servers/f/1466/p/19115173/19238159.aspx

Also check this ::

http://support.dell.com/support/edocs/software/win2003/wsr2x64/en/YY3140MR.pdf

Regards,

Rajib