UNSOLVED

thaCoolest

updated

3 months ago

T

thaCoolest

1 Message

0

5274

April 2nd, 2008 14:00

PowerEdge 2950 RIS install issue with textmode using SAS 5 controller..

I was able to get past the Broadcom nic driver error. Then, after adding the $oem$ ---> $1 ---> textmode directory and dumping the files in, the Install fails with Error (21) Line 1896 error.  Any suggestions would be appreciated. Thanks.

 

my sif:

 

[data]
floppyless = "1"
msdosinitiated = "1"
Orisrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
OriTyp = "4"
LocalSourceOnCD = 1
DisableAdminAccountOnDomainJoin = 1

[SetupData]
OsLoadOptions = "/noguiboot /fastdetect"
SetupSourceDevice = "\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%"

[OEMBootFiles]
lsi_sas.sys
lsi_sas.inf
s2k3am64.cat
lsi_sas.tag
txtsetup.oem

[MassStorageDrivers]
"Dell SAS 5x and SAS 6x Controller Driver (Windows Server 2003 x64)"= OEM

[Unattended]
OemPreinstall = yes
DriverSigningPolicy = Ignore
FileSystem = LeaveAlone
ExtendOEMPartition = 0
TargetPath = \WINDOWS
OemPnpDriversPath = \Drivers\Broadcom
OemSkipEula = yes
InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 1


[UserData]
FullName = "%USERFIRSTNAME% %USERLASTNAME%"
OrgName = "%ORGNAME%"
ComputerName = %MACHINENAME%

[GuiUnattended]
OemSkipWelcome = 1
OemSkipRegional = 1
TimeZone = %TIMEZONE%
AdminPassword = "3amNthem0rning"

[LicenseFilePrintData]
AutoMode = PerSeat

[Display]
BitsPerPel = 16
XResolution = 800
YResolution = 600
VRefresh = 60

[Networking]

[NetServices]
MS_Server=params.MS_PSched

[Identification]
JoinDomain = %MACHINEDOMAIN%
DoOldStyleDomainJoin = Yes

[RemoteInstall]
Repartition = Yes
UseWholeDisk = Yes


[OSChooser]
Description ="Windows Server 2003 Standard x64 Edition"
Help ="Automatically installs Windows Server 2003 Standard x64 Edition without prompting the user for input."
LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"
ImageType =Flat
Version="5.2 (3790)"

 

my textmode.oem:

 

# txtsetup.oem - version S2003.2 for LSI_SAS Windows Server 2003 driver
#
# ***********************************************************************
#                                                                       *
#   Copyright 2006 LSI Logic, Corp.  All rights reserved.               *
#                                                                       *
#   This file is property of LSI Logic, Corp. 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 Logic, Corp.            *
#                                                                       *
# ***********************************************************************
#
# 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 = "Dell SAS 5x and SAS 6x Controller Driver (Windows Server 2003 x64)",\TXTSETUP.OEM,\


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


[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

DELL_SAS = "Dell SAS 5x and SAS 6x Controller Driver (Windows Server 2003 x64)",lsi_sas

[HardwareIds.scsi.DELL_SAS]
id = "PCI\VEN_1000&DEV_0054&SUBSYS_1F041028", "lsi_sas"
id = "PCI\VEN_1000&DEV_0054&SUBSYS_1F061028", "lsi_sas"
id = "PCI\VEN_1000&DEV_0054&SUBSYS_1F071028", "lsi_sas"
id = "PCI\VEN_1000&DEV_0054&SUBSYS_1F081028", "lsi_sas"
id = "PCI\VEN_1000&DEV_0054&SUBSYS_1F091028", "lsi_sas"
id = "PCI\VEN_1000&DEV_0058&SUBSYS_1F0E1028", "lsi_sas"
id = "PCI\VEN_1000&DEV_0058&SUBSYS_1F0F1028", "lsi_sas"
id = "PCI\VEN_1000&DEV_0058&SUBSYS_1F101028", "lsi_sas"
id = "PCI\VEN_1000&DEV_0058&SUBSYS_021D1028", "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.DELL_SAS]
driver  = d1,lsi_sas.sys,LSI_SAS
inf     = d1,lsi_sas.inf
catalog = d1,s2k3am64.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

 

No Responses