Re: SysprepMassStorage Problem on Compaq servers

From: John John (audetweld_at_nbnet.nb.ca)
Date: 01/19/05 

Date: Wed, 19 Jan 2005 10:17:35 -0400

You're welcome. I sort of had my doubts that the article would be a fix
because of IDE vs Mass Storage, however being that the new chips cause
problems with storage controllers I figured it could be a chance that it
would also cause problems with Mass Storage devices. I'm glad to see
that the syntax in the article led you to the right fix. Very nice of
you to post your working .inf files here, I'm sure they will be very
helpful to others with this problem.

Regards;

John

Joe wrote:

> Finally figured it out! Phew!
>
> Ok, I mainly had to alter the entries in the SysprepMassStorage. Originally
> I had the following syntax:
> PCI\VEN_0E11&DEV_B060&SUBSYS_40700E11 =
> "C:\drivers\hpcpq\cpqcissm\cpqcissm.inf",\,"Smart Array 5x and 6x Driver
> Diskette", "\cpqcissm.sys", which was the same syntax in the txtsetup.oem
> file. And after seeing this format all over the web I just knew I had the
> correct format.
>
> The link from John John wasn't exactly the fix; although, it did lead me in
> the right direction. To fix the problem I basically removed the [\,"Smart
> Array 5x and 6x Driver Diskette", "\cpqcissm.sys"] from the device line. So,
> the format PCI\VEN_0E11&DEV_B060&SUBSYS_40700E11 =
> "C:\drivers\hpcpq\cpqcissm\cpqcissm.inf" worked! Way too simple right!!!
>
> Originally once I executed Sysprep, it immediately restarted the server. I
> knew it worked because after the change because the box did not immediately
> bounce AND I received an error (for misspelling something). I was on my way
> at least! Corrected the error, uploaded and brought down the image on 5
> different servers and it worked. The server models were Dell PowerEdge 2650,
> CPQ DL580, CPQ DL380, CPQ ML570 and will be testing an IBM 346 tomorrow
> (yeah, were a mixed bag of tricks here).
>
> Thanks for your help John John. Now I can continue my Disaster Recovery
> testing!
>
> Here goes a copy of the sysprep.inf (watch for wrapping):
>
> --- Begin sysprep.inf ---
> [Unattended]
> OemSkipEula = Yes
> TargetPath = \WINNT
> InstallFilesPath = "C:\sysprep\i386"
>
> ;This key is valid only when performing a SYSPREP-based installation.
> ;This key should be specified only when installing an image created
> ;from a uniprocessor master system to a multiprocessor target system.
> ;This key notifies Setup to use the Multiprocessor (MP) HAL rather than
> ;the Uniprocessor (UP) HAL present when the system was imaged.
> ;You should not reapply this image to a Uniprocessor machine,
> ;or there will be a noticeable hit to performance
> ;Enable next line ONLY if building master on UP to apply to MP.
> ;UpdateHAL = "ACPIAPIC_MP,%windir%\inf\hal.inf"
>
> ;This key is valid only when performing a SYSPREP-based installation.
> ;This key should be specified only when installing an image created from
> ;a multiprocessor master system using the ACPI APIC HAL to an APIC-compatible
> ;uniprocessor or multiprocessor target system. This key notifies Setup to
> ;redetect the proper kernel based on the number of processors.
> ;Enable next line if building master image on MP machine to apply the image
> ;to either MP or UP machines.
> UpdateUPHAL = "ACPIAPIC_UP,%SystemDrive%\Sysprep\i386\Uniproc\Mp2up.inf"
>
> [GuiUnattended]
> Timezone=020
> OemSkipRegional = 1
> OemSkipWelcome = 1
> Adminpassword=*
>
> [UserData]
> Fullname="xxxxxxxxxx"
> Orgname="xxxxxxxxxxx"
> Computername="xxxxxxxxxx"
> Productid="xxxxxxxxxxxxxxxxxxxxx"
>
> [LicenseFilePrintData]
> AutoMode = "PerSeat"
>
> [Networking]
>
> [Identification]
> Joinworkgroup=Workgroup
>
> ;The following key is only supported by Sysprep v1.1.
> ;This section allows a SYSPREP image to install on a machine
> ;with any of the drive controller types matching the
> ;plug and play IDs of the lines below.
> ;
> ;Format of this section is:
> ; <PlugAndPlayID> = "<path to device inf>" or
> ; <PlugAndPlayID> = "<path to device inf>", "<disk directory>", "<disk
> description>", "<disk tag>"
> ;
> ;Any lines ending in MSHDC.INF are for IDE drive support.
> ;Any lines ending in SCSI.INF are for SCSI drive support.
>
> [SysprepMassStorage]
> ; *******************************
> ; HP/Compaq SCSI and RAID Drivers
> ; *******************************
>
> ;COMPAQ 32-BIT Fast/Wide/Ultra/Ultra2/64 Bit Ultra2/SCSI3/Int. Wide Ultra2
> Device Driver
> PCI\VEN_1000&DEV_0003 = "C:\drivers\hpcpq\cpq32fs2\cpq32fs2.inf"
> PCI\VEN_1000&DEV_000f = "C:\drivers\hpcpq\cpq32fs2\cpq32fs2.inf"
> PCI\VEN_1000&DEV_000b = "C:\drivers\hpcpq\cpq32fs2\cpq32fs2.inf"
> PCI\VEN_1000&DEV_000c = "C:\drivers\hpcpq\cpq32fs2\cpq32fs2.inf"
> PCI\VEN_1000&DEV_0001 = "C:\drivers\hpcpq\cpq32fs2\cpq32fs2.inf"
> PCI\VEN_1000&DEV_000a = "C:\drivers\hpcpq\cpq32fs2\cpq32fs2.inf"
> PCI\VEN_1000&DEV_0012 = "C:\drivers\hpcpq\cpq32fs2\cpq32fs2.inf"
> NCRC710_SCSI = "C:\drivers\hpcpq\cpq32fs2\cpq32fs2.inf"
> CPQFWS2E_SCSI = "C:\drivers\hpcpq\cpq32fs2\cpq32fs2.inf"
> ;COMPAQ 2/P, 2DH, 2SL, 221, 3200 CONTROLLERS
> PCI\VEN_0E11&DEV_AE10&SUBSYS_40300E11 =
> "C:\drivers\hpcpq\cpqarray\cpqarray.inf"
> PCI\VEN_0E11&DEV_AE10&SUBSYS_40310E11 =
> "C:\drivers\hpcpq\cpqarray\cpqarray.inf"
> PCI\VEN_0E11&DEV_AE10&SUBSYS_40320E11 =
> "C:\drivers\hpcpq\cpqarray\cpqarray.inf"
> PCI\VEN_0E11&DEV_AE10&SUBSYS_40330E11 =
> "C:\drivers\hpcpq\cpqarray\cpqarray.inf"
> PCI\VEN_0E11&DEV_AE10&SUBSYS_40340E11 =
> "C:\drivers\hpcpq\cpqarray\cpqarray.inf"
> CPQARRAY_SCSI = "C:\drivers\hpcpq\cpqarray\cpqarray.inf"
> DETECTED\cpqarray = "C:\drivers\hpcpq\cpqarray\cpqarray.inf"
> ;COMPAQ SMART ARRAY-2 CONTROLLERS
> PCI\VEN_1000&DEV_0010&SUBSYS_40400E11 =
> "C:\drivers\hpcpq\cpqarry2\cpqarry2.inf"
> PCI\VEN_1000&DEV_0010&SUBSYS_40480E11 =
> "C:\drivers\hpcpq\cpqarry2\cpqarry2.inf"
> PCI\VEN_1011&DEV_0046&SUBSYS_40500E11 =
> "C:\drivers\hpcpq\cpqarry2\cpqarry2.inf"
> PCI\VEN_1011&DEV_0046&SUBSYS_40510E11 =
> "C:\drivers\hpcpq\cpqarry2\cpqarry2.inf"
> PCI\VEN_1011&DEV_0046&SUBSYS_40580E11 =
> "C:\drivers\hpcpq\cpqarry2\cpqarry2.inf"
> ;COMPAQ SMART ARRAY 5X AND 6X CONTROLLERS
> SCSI\OtherCOMPAQ__SCSI_COMMUNICATECISS =
> "C:\drivers\hpcpq\cpqcissm\cpqcissm.inf"
> PCI\VEN_0E11&DEV_B060&SUBSYS_40700E11 =
> "C:\drivers\hpcpq\cpqcissm\cpqcissm.inf"
> PCI\VEN_0E11&DEV_B178&SUBSYS_40800E11 =
> "C:\drivers\hpcpq\cpqcissm\cpqcissm.inf"
> PCI\VEN_0E11&DEV_B178&SUBSYS_40820E11 =
> "C:\drivers\hpcpq\cpqcissm\cpqcissm.inf"
> PCI\VEN_0E11&DEV_B178&SUBSYS_40830E11 =
> "C:\drivers\hpcpq\cpqcissm\cpqcissm.inf"
> ;ADAPTEC ULTRA160 SCSI CONTROLLERS
> PCI\VEN_9005&DEV_00C0 = "C:\drivers\hpcpq\adpu160m\adpu160m.inf"
> PCI\VEN_9005&DEV_00C0&SUBSYS_F6209005 =
> "C:\drivers\hpcpq\adpu160m\adpu160m.inf"
> PCI\VEN_9005&DEV_00C0&SUBSYS_F6200E11 =
> "C:\drivers\hpcpq\adpu160m\adpu160m.inf"
> PCI\VEN_9005&DEV_0080 = "C:\drivers\hpcpq\adpu160m\adpu160m.inf"
> PCI\VEN_9005&DEV_0080&SUBSYS_E2A09005 =
> "C:\drivers\hpcpq\adpu160m\adpu160m.inf"
> PCI\VEN_9005&DEV_0080&SUBSYS_E2A00E11 =
> "C:\drivers\hpcpq\adpu160m\adpu160m.inf"
> PCI\VEN_9005&DEV_0080&SUBSYS_62A09005 =
> "C:\drivers\hpcpq\adpu160m\adpu160m.inf"
> PCI\VEN_9005&DEV_0080&SUBSYS_E2209005 =
> "C:\drivers\hpcpq\adpu160m\adpu160m.inf"
> PCI\VEN_9005&DEV_008F = "C:\drivers\hpcpq\adpu160m\adpu160m.inf"
> PCI\VEN_9005&DEV_00CF = "C:\drivers\hpcpq\adpu160m\adpu160m.inf"
>
> ; ******************************
> ; IBM RAID AND SCSI CONTROLLERS
> ; ******************************
>
> ;IBM x-Series 360 AIC7892
> PCI\VEN_9005&DEV_008F = %WINDIR%\INF\SCSI.INF
>
> ;Adaptec HostRAID U320 Driver
> PCI\VEN_9005&DEV_00c4 = "C:\drivers\ibm\u320\oemsetup.inf"
> PCI\VEN_9005&DEV_8011 = "C:\drivers\ibm\u320\oemsetup.inf"
>
> ;IBM ServeRAID 4M/4L/4Mx/4Lx/5i/6M/6i/7k Device Driver
> PCI\VEN_1014&DEV_01BD&SUBSYS_01BE1014 = "C:\drivers\ibm\ivdrvr\oemsetup.inf"
> PCI\VEN_1014&DEV_01BD&SUBSYS_01BF1014 = "C:\drivers\ibm\ivdrvr\oemsetup.inf"
> PCI\VEN_1014&DEV_01BD&SUBSYS_02081014 = "C:\drivers\ibm\ivdrvr\oemsetup.inf"
> PCI\VEN_1014&DEV_01BD&SUBSYS_020E1014 = "C:\drivers\ibm\ivdrvr\oemsetup.inf"
> PCI\VEN_1014&DEV_01BD&SUBSYS_02591014 = "C:\drivers\ibm\ivdrvr\oemsetup.inf"
> PCI\VEN_9005&DEV_0250&SUBSYS_02791014 = "C:\drivers\ibm\ivdrvr\oemsetup.inf"
> PCI\VEN_9005&DEV_0250&SUBSYS_028C1014 = "C:\drivers\ibm\ivdrvr\oemsetup.inf"
> PCI\VEN_9005&DEV_0250&SUBSYS_028E1014 = "C:\drivers\ibm\ivdrvr\oemsetup.inf"
>
> ;IBM II/3H/3L/4H/PC/Integrated Device Driver
> PCI\VEN_1014&DEV_002E&SUBSYS_022E1014&REV_10 =
> "C:\drivers\ibm\ppcdrvr\oemsetup.inf"
> PCI\VEN_1014&DEV_002E&SUBSYS_002E1014&REV_0D =
> "C:\drivers\ibm\ppcdrvr\oemsetup.inf"
> PCI\VEN_1014&DEV_002E&SUBSYS_00000000&REV_04 =
> "C:\drivers\ibm\ppcdrvr\oemsetup.inf"
> PCI\VEN_1014&DEV_002E&SUBSYS_00000000&REV_03 =
> "C:\drivers\ibm\ppcdrvr\oemsetup.inf"
> PCI\VEN_1014&DEV_002E&SUBSYS_00000000&REV_02 =
> "C:\drivers\ibm\ppcdrvr\oemsetup.inf"
>
> ; ******************************
> ; DELL RAID AND SCSI CONTROLLERS
> ; ******************************
>
> ;DELL PowerEdge 1400 AIC7899
> PCI\VEN_9005&DEV_00CF = %WINDIR%\INF\SCSI.INF
>
> ; AdvancedRAID devices
> PCI\VEN_1011&DEV_0046&SUBSYS_13649005 = "C:\drivers\dell\perc2\Perc2.inf"
>
> ; RAIDpoint devices
> PCI\VEN_1028&DEV_0001&SUBSYS_00011028 = "C:\drivers\dell\perc2\Perc2.inf"
>
> ; RAIDpoint devices using Gatling technology
> PCI\VEN_1028&DEV_0002&SUBSYS_00021028 = "C:\drivers\dell\perc2\Perc2.inf"
> PCI\VEN_1028&DEV_0003&SUBSYS_00031028 = "C:\drivers\dell\perc2\Perc2.inf"
> PCI\VEN_1028&DEV_0002&SUBSYS_00D11028 = "C:\drivers\dell\perc2\Perc2.inf"
> PCI\VEN_1028&DEV_0002&SUBSYS_00D91028 = "C:\drivers\dell\perc2\Perc2.inf"
> PCI\VEN_1028&DEV_000A&SUBSYS_01061028 = "C:\drivers\dell\perc2\Perc2.inf"
> PCI\VEN_1028&DEV_000A&SUBSYS_011B1028 = "C:\drivers\dell\perc2\Perc2.inf"
> PCI\VEN_1028&DEV_000A&SUBSYS_01211028 = "C:\drivers\dell\perc2\Perc2.inf"
>
> --- End Sysprep.inf ---
>
> "chad.maupin@rogerscorporation.com" wrote:
>
>
>>I too am getting the Inaccessable Boot Device error message. I looked
>>at the website below and incorporated the changes but I am still
>>getting the error. Any other ideas that could possibly help me out?
>>
>>
>>John John wrote:
>>
>>>Hmmmm... you might see something that applies here:
>>>
>>>
>>
>>http://h18000.www1.hp.com/pcn/images/ICH2%20to%20MCH_final.pdf#search='compaq%20SysprepMassStorage'
>>
>>

Relevant Pages

  • Re: SysprepMassStorage Problem on Compaq servers
    ... would also cause problems with Mass Storage devices. ... that the syntax in the article led you to the right fix. ... > The link from John John wasn't exactly the fix; although, ... DELL RAID AND SCSI CONTROLLERS ...
    (microsoft.public.win2000.setup_deployment)
  • Re: SysprepMassStorage Problem on Compaq servers
    ... would also cause problems with Mass Storage devices. ... that the syntax in the article led you to the right fix. ... > The link from John John wasn't exactly the fix; although, ... DELL RAID AND SCSI CONTROLLERS ...
    (microsoft.public.win2000.general)
  • Re: [PATCH][INCOMPLETE] sata_nv: merge ADMA support
    ... That will fix ... My workaround has been to just use John Stultz's new timekeeping ... Our PostgreSQL servers now maintain ... and require an NTP restart every day or so. ...
    (Linux-Kernel)
  • Re: Walt Disney Biography
    ... Certainly will let you know if I come across a fix and appreciate your ... Mine is with Motion Pixels Codec, ... > John Sisker ... but the video will not display. ...
    (rec.arts.disney.parks)