UNSOLVED

Jaldip

updated

8 days ago

J

Jaldip

6 Posts

0

8576

October 17th, 2006 09:00

Perc5i SAS Driver Errors

Hey guys,

I'm using DTK2.2 to roll out installations to PE 2850/2950 Servers.

The scripts are fine and i have created a WinPE CD.
i have also created a CD with 2950 & 2850 drivers intergrated using nlite and that works fine when installing from the win2003 unattended CD. i copied the i386 directory to my share.
The problem:-
when windows comes to the blue screen during setup i get the following error messages:-
Txtsetup.oem is invalid, once i have edited this file to what dell & Microsoft have specified i get the error cannot copy percsas.sys and other files.

i have downloaded the latest drivers from dell and unzipped the to :- \\dell\toolkit\systems\pe2950\$oem$\textmode, it gives the following error txtsetup.oem is invalid.

So i went onto the Microsoft site and checked there made some edits to txtsetup.oem, now i get the error txtsetup.oem is invalid.

Now when i use the dtk2.2 massstorage drivers i get the error message cannot find txtsetup.oem as it does not exist within that folder.

Even thought the i386 folder has all drivers intergrated, it still doesn't pick them up and i have also edited the unnattend.txt file and still i get the same errors.

i have copied an original 2003 CD to the share and still get the error.

Can someone shed some light on this as i am stuck and like to become unstuck from this problem the 2850 installs fine from the network share but the 2950 is kicking al sorts of errors out!

Thanks in advance
  • 678

    0

    Posted October 18th, 2006 22:00

    having same problems with the SAS drivers. posting here incase somebody responds so I get emailed as well...
  • jboswell

    13 Posts

    678

    0

    Posted November 9th, 2006 22:00

    Yeah, I am here at a client site and getting similar problems, there are 2 sites that have separate info on the topic that I have used to make a full go at it but now I am getting an error "Cant find file percsas.sys"...
     
    I am going to try MS's site and see what comes of it, there doesn't seem to be one place that all the info is compiled in, I have done this sorta thing a few times already and just about everytime it requires a GREAT deal of tweaking...
     
    There are (seemingly) only 2 critical things to the process, 1.  You need to compress the percsas.sys to your i386 folder as percsas.sy_ and then 2.  You must make sure you don't nuke the EOF character at the end of TXTSETUP.SIF...  I am pretty sure I have both those in good working order but the windows install STILL says it can't find the percsas.sys which is driving me nuts, I am thinking I will find the answer in MS's site.
     
    Anyway, just thoughts...
     
    The sites I am referencing:
     
     
    This second one has the most info about that specific topic...
     

    http://www.pcstats.com/articleview.cfm?articleid=1703&page=5

    Anyway, yeah, have fun guys!

    Joe

     
  • Jaldip

    6 Posts

    678

    0

    Posted November 10th, 2006 07:00

    Guys,
     
    i managed to resolve this. this is how:-
     
    When copying the files across make sure the txtsetup.oem file is in the same folder, so if you are using dtk, copy all massstorage drivers and replace the txtsetup.oem from the percsas.sys extract as this holds alll the info for the installation of the driver, another factor in this if you are using dtk to rollout o/s's, in the winbom.ini you start the mkserv... service as this is what starts the raid/sas drives and always you to install the drivers.
  • jboswell

    13 Posts

    678

    0

    Posted November 10th, 2006 16:00

    Jal, you are going to have to be a LOT more clear on what you are saying, I really have no way of telling what you are doing here...
     


    When copying the files across make sure the txtsetup.oem file is in the same folder,

    Copying files across?  To where?  From where?  Which TXTSETUP.OEM are you talking about?
     


    ...so if you are using dtk, copy all massstorage drivers and replace the txtsetup.oem from the percsas.sys extract as this holds alll the info for the installation of the driver...

    Nope, I am using a CD based installation, no RIS, no DTK, no time to use them and not enough resources at the moment even if I wanted to...  I only have 10 machines I need to install, but I needed them done yesterday!
     
    My last method to try before calling Dell and throwing a fit on the phone is going to be booting to a BartPE and loading the drivers/partitioning the disk there, and then restarting and installing XP on that partition, its messy, but that is really at this point the last resort.  I know a LOT of companies that use these machines as Render Nodes and we aren't going to waste a HUGE amount of money needlessly installing Windows Server on these things just to get them to work.  Dell needs to get their heads straight and make sure you can install any OS on these machines, this problem is FAR beyond absurd.
     
    Quality Control seems to be really taking a dive over there in the last few years, definitely a reason for me to start recommending HP to most of my clients, even to the point of speccing the systems out and putting in plans to phase out Dell at my existing clients sites.
     
    /rant
     
    Anyway, going back to the grind of trying to get this problem resolved.
     
    Joe

  • Jaldip

    6 Posts

    678

    0

    Posted November 13th, 2006 07:00

    Sorry mate,
     
    ok so you are doing a CD Installation.
     
    I used nlite to slipstream the driver into the windows os cd, and have not had a problem with the package, how ever i did have the same problem with bartpe and decided to use nlite to recreate and modify the installation. This package also alows you to add drivers to the installation and create a unattended install an iso.
    Try this link and program, if worse comes to worse, unzip the drivers to a diskette.
     
     
    Sorry the previous reply, comments are for DTK or RIS only.
  • jboswell

    13 Posts

    678

    0

    Posted November 13th, 2006 17:00


    @Jaldip wrote:
    Sorry mate,
    ok so you are doing a CD Installation.
    I used nlite to slipstream the driver into the windows os cd
    Sorry the previous reply, comments are for DTK or RIS only.





    Yeah I did that one, same error came up... nlite did what it was supposed to do, the driver still didn't load.

    Tried BArtPE, still didn't work, this driver must be hardcoded to Windows2003 or something, it absolutely refuses to load when I am trying to install WinXP, no matter what method I have used it will not load.

    Joe
  • Jaldip

    6 Posts

    678

    0

    Posted November 14th, 2006 07:00

    Joe,
     
    it seems like that nlite is having a problem with the txtsetup.oem,i managed to resolve this by manually copying the file to the windows folder.
    Try the following:-
     
    Create a Folder Called $oem$
    then create a sub folder called textmode
    copy your drivers to this folder.
    now create a folder called $1
    Create a subfolder called Drivers
    now create a sub folder massstorage dropt the same drivers in the folder
     
    now open unattended.txt or winnt.sif
     
    add the follwing sections
     
    OemFilesPath="x:\i386\$oem$"
       OemPnPDriversPath="\drivers;\textmode;\hapi;\broadcom;\r117179;\r120343;\r120343\ris_inf;\r120960;\r122665;\r122758;\r122758\b_29093;\r122802;\r122802\sp;\r125879;\r126220;\r99849;\r99970;\massstorage;\rac4"
     
    [OEMBootFiles]
       percsas.sys
       nodev.inf
       percsas.cat
       Txtsetup.oem
     
    x is the cd drive which it installs from.
     
    this worked for me so if it doesnt pick it up from the system folder it can always pick it up from the $oem$ folder