ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Unattend.txt + DL380 G3

SOLVED
Go to solution
Thomas Sords
Advisor

Unattend.txt + DL380 G3

Does anyone have a sample unattend.txt or winnt.sif for a DL380 G3? I specifically need the drivers section, as it blue screens with "unavailable boot device" error.

Thomas
20 REPLIES
Jeff Mathews
Respected Contributor

Re: Unattend.txt + DL380 G3

This should be the sections you need, and this should work for the entire ML/DL lines:

[MassStorageDrivers]
"Adaptec Ultra160 Family Manager Set"=OEM
"Compaq Smart Array Controllers"=OEM
"Smart Array 5300 Controller"=OEM
"Smart Array 5i, 532, 5312 Controllers"=OEM
"Smart Array 6i, 641, 642, 6400 EM, 6400 Controllers"=OEM
"CSB-6 Ultra ATA-100 IDE RAID Controller"=OEM
"Integrated Ultra ATA-100 Dual Channel Controller"=OEM
"Integrated Ultra ATA-100 IDE RAID Controller"=OEM
"LSI Logic Ultra320 1020/1030 Driver"=OEM
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller"=RETAIL
"Symbios Logic C8100 PCI SCSI Host Adapter"=RETAIL
"Symbios Logic C896 PCI SCSI Host Adapter"=RETAIL
"Symbios Logic C8xx PCI SCSI Host Adapter"=RETAIL

[OEMBootFiles]
ADPU160M.SYS
CPQARRY2.SYS
CPQCISSM.SYS
LSICSB6.SYS
MEGAIDE.SYS
SYMMPI.SYS
TXTSETUP.OEM

Jeff
Thomas Sords
Advisor

Re: Unattend.txt + DL380 G3

Well, I added the information from your last post, but still blue screen on the reboot after the winnt.exe command. It starts up, then goes thru starting to load drivers, but blue screens with unavailable boot device again. Any other ideas?
Jeff Mathews
Respected Contributor
Solution

Re: Unattend.txt + DL380 G3

Make sure you have a textmode folder beneath the $OEM$ share that has all the drivers mentioned. You also need to have a txtsetup.oem file that contains mappings to the controller name -> driver file. Here is a copy of my file:

[Disks]
d1 = "ProLiant(R) Support Pack for Windows 2000",.\disk1,.

[Defaults]
SCSI = B178

[SCSI]
adpu160m = "Adaptec Ultra160 Family Manager Set"
cpqarry2 = "Compaq Smart Array Controllers"
B060 = "Smart Array 5300 Controller"
B178 = "Smart Array 5i, 532, 5312 Controllers"
0046 = "Smart Array 6i, 641, 642, 6400 EM, 6400 Controllers"
megaide100_nt5 = "CSB-6 Ultra ATA-100 IDE RAID Controller"
megaide100_nt5c = "Integrated Ultra ATA-100 Dual Channel Controller"
megaide100_nt5l = "Integrated Ultra ATA-100 IDE RAID Controller"
symmpi = "LSI Logic Ultra320 1020/1030 Driver"


[Files.scsi.adpu160m]
driver = d1,adpu160m.sys,aic7899
inf = d1,adpu160m.inf
catalog = d1,adpu160m.cat

[Files.scsi.cpqarry2]
driver = d1,cpqarry2.sys,cpqarry2
inf = d1,cpqarry2.inf
catalog = d1,cpqarry2.cat

[Files.scsi.B060]
driver = d1,cpqcissm.sys,cpqcissm
inf = d1,cpqcissm.inf
catalog = d1,cpqcissm.cat

[Files.scsi.B178]
driver = d1,cpqcissm.sys,cpqcissm
inf = d1,cpqcissm.inf
catalog = d1,cpqcissm.cat

[Files.scsi.0046]
driver = d1,cpqcissm.sys,cpqcissm
inf = d1,cpqcissm.inf
catalog = d1,cpqcissm.cat

[Files.scsi.megaide100_nt5]
driver = d1,lsicsb6.sys,lsicsb6
inf = d1,lsicsb6.inf
inf = d1,nodev.inf
catalog = d1,csb6win.cat

[Files.scsi.megaide100_nt5c]
driver = d1,megaide.sys,megaide
inf = d1,megaide.inf
catalog = d1,mega2k.cat

[Files.scsi.megaide100_nt5l]
driver = d1,megaide.sys,megaide
inf = d1,megaide.inf
catalog = d1,mega2k.cat

[Files.scsi.symmpi]
driver = d1,symmpi.sys,symmpi
inf = d1,symmpi.inf
catalog = d1,symmpi2k.cat


[Config.adpu160m]
value = "",tag,REG_DWORD,20

[Config.cpqarry2]
value = "",tag,REG_DWORD,102
value = Parameters\Device,NumberOfRequests,REG_DWORD,80
value = Parameters\PnpInterface,5,REG_DWORD,1

[Config.cpqcissm]
value = "",tag,REG_DWORD,103
value = Parameters\PnpInterface,5,REG_DWORD,1
value = Parameters\Device,NumberOfRequests,REG_DWORD,80

[Config.lsicsb6]
value = "",Tag,REG_DWORD,1

[Config.megaide]
value = "",Tag,REG_DWORD,1

[Config.symmpi]
value = Parameters,dummy,REG_DWORD,0
value = Parameters\PnpInterface,5,REG_DWORD,1


[HardwareIds.scsi.adpu160m]
id = "PCI\VEN_9005&DEV_00C0","adpu160m"
id = "PCI\VEN_9005&DEV_0080","adpu160m"

[HardwareIds.scsi.cpqarry2]
id = "PCI\VEN_1000&DEV_0010&SUBSYS_40400E11","cpqarry2"
id = "PCI\VEN_1011&DEV_0046&SUBSYS_40500E11","cpqarry2"
id = "PCI\VEN_1011&DEV_0046&SUBSYS_40510E11","cpqarry2"
id = "PCI\VEN_1011&DEV_0046&SUBSYS_40580E11","cpqarry2"

[HardwareIds.scsi.B060]
id = "PCI\VEN_0E11&DEV_B060","cpqcissm"

[HardwareIds.scsi.B178]
id = "PCI\VEN_0E11&DEV_B178","cpqcissm"

[HardwareIds.scsi.0046]
id = "PCI\VEN_0E11&DEV_0046","cpqcissm"

[HardwareIds.scsi.megaide100_nt5]
id = "PCI\VEN_1166&DEV_0213&SUBSYS_00E80E11","lsicsb6"

[HardwareIds.scsi.megaide100_nt5c]
id = "PCI\VEN_1095&DEV_0649&SUBSYS_005D0E11","megaide"

[HardwareIds.scsi.megaide100_nt5l]
id = "PCI\VEN_1095&DEV_0649&SUBSYS_007E0E11","megaide"

[HardwareIds.scsi.symmpi]
id = "PCI\VEN_1000&DEV_0030","symmpi"


Make sure this file is located at the root of the $OEM$ folder, as well as in the textmode folder.

Let me know if it works.

Jeff
Thomas Sords
Advisor

Re: Unattend.txt + DL380 G3

Well, it no longer blue screens. Turns out I didn't have an OemFilesPath variable in my unattended.txt file. So, that hurdle past. Out of curiousity, have you had it pause during the copying of files and error that it couldn't find banana.ani? I have a banana.an_ in my i386 dir, and even put a banana.ani in the dir, but to no avail.

Thanks for your help!
Jeff Mathews
Respected Contributor

Re: Unattend.txt + DL380 G3

Hi Thomas, does it regularly fail on the same file? I have had it hiccup the odd time, but it never does it consistently. The next server I would build would be fine. I have heard of problems with your i386 folder becoming "corrupt" so to speak. Something to do with extra files being present, or the compression of some files being wrong? If it continues to happen it may be worth putting a fresh copy of the i386 folder on your share or CD and re-slipstreaming.

Glad the blue screens are gone...they can be the most frustrating I find.

Jeff
Thomas Sords
Advisor

Re: Unattend.txt + DL380 G3

Oh, so close! I have gotten it to the last bit (I think), but I get a "The manufacturer provided file that setup is trying to use is corrupted or invalid: Line 1 contains a syntax error" and the forces you to exit setup

Any other ideas?
Jeff Mathews
Respected Contributor

Re: Unattend.txt + DL380 G3

Hi Thomas, do you have the following lines in your unattend file under the [unattend] heading?

OemPreinstall=Yes
OemSkipEula=Yes
OverwriteOemFilesOnUpgrade=No

Jeff
Jeff Mathews
Respected Contributor

Re: Unattend.txt + DL380 G3

Sorry for the mistake, but the above post should read "...[unattended] heading..."

Jef
Thomas Sords
Advisor

Re: Unattend.txt + DL380 G3

Didn't have the overwriteonupgrade set, but turns out that that wasn't it. I was looking at my floppy, and there was a Winnt.sif file on it. I removed it, and the install finally went thru! Thanks much for the help and advice. Never could get banana.ani to copy, for some reason :)


Anywho.... just out of curiousity... have you ever had WWW Publishing service error out with a "Unknown Authentication Service"?

Thanks again for your help!
Jeff Mathews
Respected Contributor

Re: Unattend.txt + DL380 G3

No, I haven't seen that error with the WWW Publishing service. Is this one of the components you have specified in your components section? It might be worth comparing what components you have installed. Here is a copy of what I typically install on an IIS enabled server.

[Components]
accessopt=off
cdplayer=off
certsrv=on
certsrv_client=on
deskpaper=off
dialer=off
fp_extensions=off
freecell=off
hypertrm=off
iis_common=on
iisdbg=off
iis_doc=off
iis_htmla=off
iis_inetmgr=on
iis_smtp=off
iis_smtp_docs=off
iis_www=on
indexsrv_system=off
chat=off
LicenseServer=off
media_clips=off
media_utopia=off
minesweeper=off
mplay=off
netcis=off
netoc=off
objectpkg=off
pinball=off
rec=off
solitare=off
templates=off
tsenable=on
vol=off
wms=off
wms_admin=off
WMS_SERVER=off

Jeff
Thomas Sords
Advisor

Re: Unattend.txt + DL380 G3

ach... disregard the last bit... turns out I didn't have the client for MS installed and that IIS requires that.

Thanks again!
Thomas Sords
Advisor

Re: Unattend.txt + DL380 G3

mine below.

What is the WMS stuff? that isn't documented. This W2003? or W2000


[Components]
cdplayer=off
charmap=off
chat=off
cluster=off
deskpaper=off
dialer=off
fp=off
freecell=off
iis_common=on
iisdbg=off
iis_doc=off
iis_ftp=off
iis_htmla=off
iis_inetmgr=on
iis_nntp=off
iis_nntp_docs=off
iis_smtp=off
iis_smtp_docs=off
indexsrv_system=off
LicenseServer=off
media_clips=off
minesweeper=off
mousepoint=off
mplay=off
netcis=off
netoc=off
pinball=off
rec=off
solitaire=off
templates=off
vol=off
Jeff Mathews
Respected Contributor

Re: Unattend.txt + DL380 G3

Hi Thomas, WMS is Windows Media Services (W2K).

WMS = Windows Media Services. Default is ON
WMS_Admin = Windows Media Services administratorive components. Default is ON.
WMS_Server = Server components. Deafult ON.

I guess those discriptions are pretty self explanitory, just taking the above from my doc. I grabbed it from the MS Windows 2000 Guide to Unattended Setup. Although mine is a bit old now, maybe they don't include the description in the newer ones :)

Jeff
Thomas Sords
Advisor

Re: Unattend.txt + DL380 G3

Wow... has the forum been screwed up for you, too? Thanks for everything. I have gotten the load scenario down pat for the G3, and am moving on to the G2 next. For what it is worth, you have saved me a ton of time and hair pulling with your help. Oh, btw, I have tried three different server disks, different folders on the local harddrive to prep, and every single time, I get the banana.ani missing error message. I give up on that one!

Thomas
Thomas Sords
Advisor

Re: Unattend.txt + DL380 G3

Ahh! Eureka! Turns out, the problem with banana.ani was that the CD-Rom drive that I was using (a generic one) was called banana. I switched to the compaq CD Driver for the heck of it, and it works!

Re: Unattend.txt + DL380 G3

Alright, so after reading this post, I have some issues. We are currently using the SmartStart deployment packs for our HP servers and seem to be having some significant issues with this. I have followed this article to the "T" and fixed several of our issues, but now it is failing at the OS install piece where it begins to copy driver files to the OS volume. the exact error during Windows textmode setup is "Setup was unable to copy the following file ADPU160M.SYS". Actually, it fails on every file in the [OEMBootFiles] section of the Unattend.txt file. I have ensured that the driver files are in all of these sections "I386, $oem$\Textmode, \$oem$\drivers\scsi". So idealy, it should be able to copy the files from any of these locations. You may notice in the attached file, the txtsetup.oem, file appears just as you stated it should. Please note, this is a 2000 SP4 install and the 2003 install using virtually the same files is working fine. Please help...

Re: Unattend.txt + DL380 G3

Okay, so here's an update. I started all over and began creating an entirely new unattended install. This time it appears everything is working fine and the install begins to copy files to the hard drive with no problem during textmode setup. However, now it gets all the way to 100% and stops. Interesting part is that the activity LED's on the hard disks flash intensively making me think activity is still there. But I left it overnight and still the same. Any idea why it would halt at 100%?
Thomas Sords
Advisor

Re: Unattend.txt + DL380 G3

Sound to me like the process is halted for either hardware issues (like a possible defective hard drive), or the settings are not quite correct. I will look at the settings on monday, and see if I see something odd (I am actually on vacation at the moment).

Re: Unattend.txt + DL380 G3

Thank you for you help. I have almost given up. I have tired nearly everything I can think of. Also, I know its not a hardware issue because I have tried this on 2 brand new out of the box 380 G4's.
Thomas Sords
Advisor

Re: Unattend.txt + DL380 G3

Where did you get your oem files from? Did you build fresh from the most recent Smart Start CD, or from another source? It really sounds like you are using out of date drivers, which could cause the problems you are facing. Two methods to ensure you are building the deploy image using the appropriate drivers --> download the most recent service pack from www.hp.com. Alternatively, you can build the image based on the smart script guide using the Smart Start deploy disks that were included with your servers.