4 Replies Latest reply on Mar 3, 2008 10:03 AM by Jared Barneck

    ERR_Fail Messages with OS Deployment



      Hey everyone!



      I am having some issues with a particular image deployment. No matter what I do or where I plug in the machine, the image will always fail and leave me hanging at a "Waiting For Command" screen. The machine (if it matters, not sure if it does) is a Dell XPS M1330, and an image was captured successfully from another M1330 earlier from the same network jack from which this one fails. A copy of the log file is pasted below:




      "0015C580D8C3","OK",0,0:00:00,3/3/2008 8:00:49 AM,3/3/2008 8:00:49 AM,"DOS"

      "0015C580D8C3","OK",0,0:00:01,3/3/2008 8:00:49 AM,3/3/2008 8:00:50 AM,"ldlogon.exe ka 102044A91617A1403E64F627A3B KA-NET, TIMEOUT=300"

      "0015C580D8C3","OK",458752,0:00:02,3/3/2008 8:00:50 AM,3/3/2008 8:00:52 AM,"net use i:
      kaldser\images, STATUS(85) FACILITY=7 TIMEOUT=300"

      "0015C580D8C3","OK",458752,0:00:03,3/3/2008 8:00:52 AM,3/3/2008 8:00:55 AM,"net use h:
      kaldser\ldmain, STATUS(85) FACILITY=7 TIMEOUT=300"

      "0015C580D8C3","OK",0,0:00:08,3/3/2008 8:00:55 AM,3/3/2008 8:01:03 AM,"r:\net\htget -o r:\sysprep.inf, STATUS"

      "0015C580D8C3","OK",0,0:00:02,3/3/2008 8:01:03 AM,3/3/2008 8:01:05 AM,"r:\net\htget -o r:\dos\tokrepl.exe, STATUS"

      "0015C580D8C3","OK",0,0:00:03,3/3/2008 8:01:05 AM,3/3/2008 8:01:08 AM,"r:\net\htget -o r:\dos\fworkcl.exe, STATUS"

      "0015C580D8C3","OK",0,0:00:03,3/3/2008 8:01:08 AM,3/3/2008 8:01:11 AM,"r:\net\htget -o r:\dos\pworkcl.exe, STATUS"

      "0015C580D8C3","OK",0,0:00:02,3/3/2008 8:01:11 AM,3/3/2008 8:01:13 AM,"r:\net\htget -o r:\ldsleep.exe, STATUS"

      "0015C580D8C3","OK",0,0:00:03,3/3/2008 8:01:13 AM,3/3/2008 8:01:16 AM,"r:\net\htget -o r:\dos\prtition.exe, STATUS"

      "0015C580D8C3","OK",458752,0:00:02,3/3/2008 8:01:16 AM,3/3/2008 8:01:18 AM,"r:\net\htget -a h:\osd\imaging\IMAGE.EXE, STATUS FACILITY=7"

      "0015C580D8C3","OK",0,0:00:03,3/3/2008 8:01:18 AM,3/3/2008 8:01:21 AM,"prtition wipe, STATUS"

      "0015C580D8C3","OK",0,0:00:02,3/3/2008 8:01:21 AM,3/3/2008 8:01:23 AM,"command.com /c h:"

      "0015C580D8C3","OK",0,0:00:02,3/3/2008 8:01:23 AM,3/3/2008 8:01:25 AM,"command.com /c cd \osd\imaging"

      "0015C580D8C3","OK",0,0:00:03,3/3/2008 8:01:25 AM,3/3/2008 8:01:28 AM,"echo Running OS Imaging tool. Please wait..."

      "0015C580D8C3","ERR_Fail",-1917452033,0:11:58,3/3/2008 8:01:28 AM,3/3/2008 8:13:26 AM,""command.com /c h:\osd\imaging\IMAGE.EXE /RN /O i:\80DF6F00.IMG", STATUS FACILITY=3510"

      ; "Job Complete","0 Done","1 Failed","0 Off","0 Unknown"



      The ","ERR_Fail",-1917452033 is the part that concerns me. Any ideas as to why this is happening and what I can do to resolve it is greatly appreciated!



      Also, I am currently running 8.61 SP3, will be upgrading to 8.7 in the near future.



        • 1. Re: ERR_Fail Messages with OS Deployment

          Does this XPS have raid or a sata controller? It may be possible you are getting a failure there because it can't mount a drive. Does this script work on the M1330?


          Try looking at this doc


          • 2. Re: ERR_Fail Messages with OS Deployment


            SATA. The M1330 can be set to run in either AHCI or SATA modes, and for the purposes of getting it to work (the M1330 comes with Vista only and you have to tweak a bit to ensure XP compatibility), it's set to SATA operation.



            I presume the scripts are in the linked document? I'll give 'em a try in just a couple of minutes.



            • 3. Re: ERR_Fail Messages with OS Deployment

              The attached doc gives you some troubleshooting steps to try, it looks like that error might be more related to NIC drivers. You could use the KB article referenced in that doc to try a vboot image deployment and see if that works. This is the big reason they've moved on to a WinPE environment is all the problems with DOS NIC drivers, best thing is probably to get yourself on 8.8 when you can and start using PE OSD scripts.

              • 4. Re: ERR_Fail Messages with OS Deployment
                Jared Barneck SupportEmployee


                Facility: 3510

                Error: 255


                255 = Image stream is corrupt.


                So either the image is corrupt where it is on the server (you can test

                by validating it with ImageW.exe).


                - or -


                The image is fine at the source and is being corrupted by the transfer.

                This is very common with the DOS drivers, which is one of the main

                reasons we moved off of DOS in 8.7.  It could be the TCP Checksum on the

                server side is not understood by the DOS driver, so you could turn that

                off on the server side, or it could just be the DOS driver and if there

                is not another better DOS driver, there is not a fix.