Unsolved

This post is more than 5 years old

45429

December 17th, 2015 00:00

PE1950 SAS 5 1068 (B0) driver issue installing Windows Server 2003

Can anyone out there please offer me some assistance. I am trying to install Windows Small Business Server Premium 2003 on a Poweredge 1950 server. Under device manager the storage controller is listed as Dell 5/i controller. However, when system is booting it only displays Dell SAS 5 V 6.06.00.02 2006-4-5. Removed cover and card indicates LSI Logi 1068 (b0) Rev A00 on main Chip. with 62089a2.

My primary drive is a 73 gig SAS MAX3073RC

Secondary drive is ATA ST 3750640NS SATA 750GB

I am trying to install SBS, however keeps telling me it can't locate local disk. I've downloaded the Dell utility to load the files on USB drive since there is no floppy available. However I cannot find the correct files to download anywhere!!! Way too many listed on Dells site. None refer to 1068. I see alot of 1068e...

The USB seems to work when I first press f6, brings up all of my partitions, then immediately prompts me for LSI Fusion MPT SAS Store Diskette for additional drivers. I am at a loss. Can anyone point me in the right direction?

At one point , it actually went passed the error and started copying files, then asked for a reboot and then just Boot error and I have to start entire process over again...Any help would be greatly appreciated.

The firmware revision from within the SAS5 utility says 0.06.40.00-IT. Adapter 1068

Here is what I have in the Dell USBKEYPREPf6 utility txtsetup.oem.

# txtsetup.oem - version S2003.2 - LSI_SAS Windows Server 2003 X86 driver
#
# ***********************************************************************
# *
# Copyright 2007 LSI Corporation. All rights reserved. *
# *
# This file is property of LSI Corporation. and is licensed for *
# use as is. The receipt of or posession of this file does not *
# convey any rights to modify its contents, in whole, or in part, *
# without the specific written consent of LSI Corporation. *
# *
# ***********************************************************************
#
# format for txtsetup.oem.
#
# General format:
#
# [section]
# key = value1,value2,...
#
#
# The hash ('#') introduces a comment.
# Strings with embedded spaces, commas, or hashes should be double-quoted
#


[Disks]

# This section lists all disks in the disk set.
#
# is a descriptive name for a disk, used when
# prompting for the disk
# is a file whose presence allows setup to recognize
# that the disk is inserted.
# is where the files are located on the disk.
#

d1 = "LSI Fusion-MPT SAS Storport Driver",\lsi_sas.tag,\


[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 = LSI_SAS_32


[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

LSI_SAS_32 = "LSI Fusion-MPT SAS Driver (Server 2003 32-bit)",lsi_sas


[HardwareIds.scsi.LSI_SAS_32]

id = "PCI\VEN_1000&DEV_0050", "lsi_sas"
id = "PCI\VEN_1000&DEV_0054", "lsi_sas"
id = "PCI\VEN_1000&DEV_0058", "lsi_sas"
id = "PCI\VEN_1000&DEV_005E", "lsi_sas"
id = "PCI\VEN_1000&DEV_0056", "lsi_sas"
id = "PCI\VEN_1000&DEV_005A", "lsi_sas"
id = "PCI\VEN_1000&DEV_0062", "lsi_sas"


# This section lists the files that should be copied if the user
# selects a particular component option.
#
# is one of driver, port, class, dll, hal, inf, or detect.
# See below.
# identifies where the file is to be copied from, and must
# match en entry in the [Disks] section.
# is the name of the file. This will be appended to the
# directory specified for the disk in the [Disks] section to form the
# full path of the file on the disk.

[Files.scsi.LSI_SAS_32]
driver = d1,lsi_sas.sys,LSI_SAS
inf = d1,lsi_sas.inf
inf = d1,lsinodrv.inf
catalog = d1,s2k332.cat


[Config.LSI_SAS]

# This section specifies values to be set in the registry for
# particular component options. Required values in the services\xxx
# key are created automatically -- use this section to specify additional
# keys to be created in services\xxx and values in services\xxx and
# services\xxx\yyy.
#
# is relative to the services node for this device.
# If it is empty, then it refers to the services node.
# If specified, the key is created first.
# specifies the value to be set within the key
# is a string like REG_DWORD. See below.
# specifies the actual value; its format depends on
value = Parameters\PnpInterface,5,REG_DWORD,1

December 19th, 2015 05:00

Two days and no response...Wow, so much for Dell Forums!

11 Legend

 • 

16.3K Posts

December 19th, 2015 07:00

We are volunteers and have a life outside of the forums, if you can believe that.

Dell had a non-RAID SAS controller called the SAS 5/i. It is a rebranded LSI controller using the 1068 chipset. You should always refer to these cards as the Dell equivalent: SAS 5/i.

2003 x86 Driver:

http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=57DY9

Use the Hard Drive format and download/run to extract the files before use.

Don't use the F6KeyPrep utility ... it is far too flaky (the message you saw is the most common result of using it). Use nLiteOS.com to integrate the drivers into the installation media.

Alternatively, you can use SMTD to install, including all the drivers and OMSA during the install:

http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=PYKGK&fileId=3365348005&osCode=WNET&productCode=poweredge-1950&languageCode=EN&categoryId=SZ

HOWEVER ... this method will require your 2003 media to be R2 AND SP2 (nLite can also integrate SP's).

Why 2003?! It's end-of-life and obsolete. Just curious.

If you need more assistance, let me know.

December 19th, 2015 16:00

Thank you very much for the assistance. I am a small business and I found a copy online for $50 bucks, hard to argue with on my budget. I've tried 10 different drivers already, Including the one in your response. Ive never used nlite, but will attempt to figure out what it is and how it works and let you know.

Thanks

11 Legend

 • 

16.3K Posts

December 26th, 2015 12:00

When using nLiteOS, choose Multiple Driver Files, select all listed, then select TextMode drivers.

Like I said, the F6KeyPrep utility doesn't work. You used the right driver, but the utility is flaky.

I could argue it. You can get nearly a year of evaluation usage from Server 2012 R2 and it works just fine on the 1900. What will your server be doing? What industry is your business in?

No Events found!

Top