Hmpf, I'm a douche!

I forgot I still had the driver files in c:\pebuilder3110a\drivers\ -folder. I deleted them and changed the BartPE source to Windows 2003. After rebuilding I was now able to boot the server and see the hard drives.

Thank you!

And many thanks to DELL who forgot to enable RAID during the factory installations... It took a few days to get to the bottom of this, but at least I learned a great deal in the process. Hopefully I will remember at least some part of this later on.

Yet again, thank you OverFlow!

Thanks. I got it slipstreamed by editing the original driverpack. I added the driver folder L01 and the following lines to the .ini file:

[L01]
ms_count=1
ms_1_deviceName="Dell PERC H200 SAS HBA"
ms_1_tag="lsi_sas2"
ms_1_sysFile="lsi_sas2.sys"
ms_1_hwids="PCI\VEN_1000&DEV_0064,PCI\VEN_1000&DEV_0065,PCI\VEN_1000&DEV_0070,PCI\VEN_1000&DEV_0072,PCI\VEN_1000&DEV_0074,PCI\VEN_1000&DEV_0076,PCI\VEN_1000&DEV_0077"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k"


Then I repacked it and slipstreamed to my BartPE, no errors so far. I used pe2usb.cmd to get the build to a flash drive and booted the server from it. BartPE started to load up but after a while I get the following error:

The file lsi_sas2.SY_ could not be found


What am I doing wrong here?

If I look at folder:

C:\pebuilder3110a\plugin\driverpacks.net\MassStorage\wnt5

I can see that the LSI_SAS2.SY_ is there.

(It was a retorical question, sort of...)

Using 2003 as source didn't work as I suspected. Should I somehow create my own driverpack? If so, any advice how?

Using the HWID tool:

PCI\VEN_1000&DEV_0072&SUBSYS_1F1D1028&REV_02\4&2916D576&0&0028
    Name: Dell PERC H200 Adapter
    Hardware ID's:
        PCI\VEN_1000&DEV_0072&SUBSYS_1F1D1028&REV_02
        PCI\VEN_1000&DEV_0072&SUBSYS_1F1D1028
        PCI\VEN_1000&DEV_0072&CC_010700
        PCI\VEN_1000&DEV_0072&CC_0107
    Compatible ID's:
        PCI\VEN_1000&DEV_0072&REV_02
        PCI\VEN_1000&DEV_0072
        PCI\VEN_1000&CC_010700
        PCI\VEN_1000&CC_0107
        PCI\VEN_1000
        PCI\CC_010700&DT_0
        PCI\CC_010700
        PCI\CC_0107&DT_0
        PCI\CC_0107

XP. But I will try to use 2003 files today.

Interesting, the newest DriverPacks has one driver with the same HWIds but different name. It doesn't work though with my PowerEdge T110.

[HardwareIds.scsi.DELL_SAS2_32]

id = "PCI\VEN_1000&DEV_0064", "lsi_sas2"
id = "PCI\VEN_1000&DEV_0065", "lsi_sas2"
id = "PCI\VEN_1000&DEV_0070", "lsi_sas2"
id = "PCI\VEN_1000&DEV_0072", "lsi_sas2"
id = "PCI\VEN_1000&DEV_0074", "lsi_sas2"
id = "PCI\VEN_1000&DEV_0076", "lsi_sas2"
id = "PCI\VEN_1000&DEV_0077", "lsi_sas2"

I'm trying to add Dell PERC H200 driver into driverpacks and can't get it to work. The idea is to slipstream the driver into a BartPE build and then backup my Dell PowerEdge T110 server. If I copy the drivers into BartPE's "drivers" folder and rebuild, then boot up the server using the build it says "Cannot find lsi_sas2.sys".

Anyway back to DP:

In Settings of DriverPacks, the "3rd party DriverPack(s) option is always grayed out. "DPs_BASE.log" has the following line:

2011-01-07 15:24:46 : <INIT>     Detected 3rd Party DriverPack PERCH200!

So according to the log it should work. So why is the option still grayed out?

Thanks!

I also need to integrate the PERC H200 driver into my BartPE build. How can I find the HIWIDs if there is no txtsetup.oem -file provided with the driver?