1 2 Previous Next 23 Replies Latest reply on May 26, 2014 2:31 PM by Davorin Stevanovic Branched to a new discussion.

    path error in tftp file request

    Matt Kreger

      I'm getting errors in the path the target server is using to request files from the tftpserver:

       

      [21 Jan 2010 09:40:59,829] [Thread-0] [INFO] Received read request from /20.5.205.137
      [21 Jan 2010 09:40:59,830] [Thread-0] [INFO] Requested filename : X86PC/pxelinux/pxelinux.0
      [21 Jan 2010 09:40:59,832] [Thread-35] [INFO] Sending file : /opt/bmc/bcas/provisioning/tftproot/X86PC/pxelinux/pxelinux.0
      [21 Jan 2010 09:41:16,086] [Thread-0] [INFO] Received read request from /20.5.205.137
      [21 Jan 2010 09:41:16,087] [Thread-0] [INFO] Requested filename : X86PC/pxelinux/pxelinux.0
      [21 Jan 2010 09:41:16,088] [Thread-36] [INFO] Sending file : /opt/bmc/bcas/provisioning/tftproot/X86PC/pxelinux/pxelinux.0
      [21 Jan 2010 09:41:16,133] [Thread-36] [INFO] Completed read request from /20.5.205.137. File name : /opt/bmc/bcas/provisioning/tftproot/X86PC/pxelinux/pxelinux.0
      [21 Jan 2010 09:41:16,179] [Thread-0] [INFO] Received read request from /20.5.205.137
      [21 Jan 2010 09:41:16,180] [Thread-0] [INFO] Requested filename : bootmgr.exe
      [21 Jan 2010 09:41:16,181] [Thread-37] [INFO] Sending file : /opt/bmc/bcas/provisioning/tftproot/bootmgr.exe
      [21 Jan 2010 09:41:17,118] [Thread-37] [INFO] Completed read request from /20.5.205.137. File name : /opt/bmc/bcas/provisioning/tftproot/bootmgr.exe
      [21 Jan 2010 09:41:17,267] [Thread-0] [INFO] Received read request from /20.5.205.137
      [21 Jan 2010 09:41:17,268] [Thread-0] [INFO] Requested filename : \Boot\Fonts\wgl4_boot.ttf
      [21 Jan 2010 09:41:17,269] [Thread-38] [ERROR] File not found : /opt/bmc/bcas/provisioning/tftproot//Boot/Fonts/wgl4_boot.ttf
      [21 Jan 2010 09:41:17,276] [Thread-0] [INFO] Received read request from /20.5.205.137
      [21 Jan 2010 09:41:17,276] [Thread-0] [INFO] Requested filename : \boot.ini
      [21 Jan 2010 09:41:17,277] [Thread-39] [ERROR] File not found : /opt/bmc/bcas/provisioning/tftproot//boot.ini

       

      The target server returns:

      PXE-E78:Could not locate boot server

      PXE-M0F: Exiting Intel PXE ROM


      Any suggestions?

        • 1. Re: path error in tftp file request
          Bill Robinson

          when you generated the winpe image, what did you use as your path to put the image in?  and what is in your tftproot directory right now?

          • 2. Re: path error in tftp file request
            Matt Kreger

            I followed the instructions in the README file in 760-115-provision-files.zip.

             

            CreateWinPe2_0.bat amd64 c:\BladeLogic\winpe c:\temp\x64 WinPE2_0_x64

             

            Copied the resulting files into /opt/bmc/bcas/provisioning/tftproot/WinPE2_0_x64

             

            ran extractpxeboot and copied pxeboot.0 to tftproot/X86PC/pxelinux and bootmgr.exe to tftproot

             

            Neither batch file returned any errors.

            • 3. Re: path error in tftp file request
              Matt Kreger

              This is interesting too. The server requests \Boot\Fonts\wgl4_boot.ttf, tftp server can't find tftproot//Boot/Fonts/wgl4_boot.ttf

              There is no tftproot/Boot directory, so that's no surprise.

               

              Then the server requests \Boot\BCD and the tftp server can't find tftproot//null/BCD.  What's with that?


              [22 Jan 2010 06:56:15,089] [Thread-0] [INFO] Requested filename : \Boot\Fonts\wgl4_boot.ttf
              [22 Jan 2010 06:56:15,090] [Thread-69] [ERROR] File not found : /opt/bmc/bcas/provisioning/tftproot//Boot/Fonts/wgl4_boot.ttf

               

              [22 Jan 2010 06:56:30,879] [Thread-0] [INFO] Requested filename : \Boot\BCD
              [22 Jan 2010 06:56:30,880] [Thread-71] [ERROR] File not found : /opt/bmc/bcas/provisioning/tftproot//null/BCD

              • 4. Re: path error in tftp file request
                Matt Kreger

                There are three files in tftproot/WinPE2_0_x64 (created by CreateWinPE2_0.bat):

                BCD

                boot.sdi

                WinPE.wim

                 

                How is this supposed to work?  Should the server be requesting the wim file, mounting it somewhere, and booting from there?

                 

                • PXE server is saying boot image location is WinPE2_0_x64\pxeboot.0 (which doesn't seem right, but I went ahead and copied pxeboot.0 from X86PC/pxelinux to this location)

                 

                • Client server is requesting from TFTP server the following files (and getting them)

                X86PC/pxelinux/pxelinux.0

                bootmgr.exe

                 

                • Then client requests the following and doesn't get them

                \Boot\Fonts\wgl4_boot.ttf

                \boot.ini

                 

                • Then client quits trying to PXE boot with the error PXE-E32: TFTP open timeout

                 

                Anything obvious I'm doing wrong in Provisioning Manager?

                syspkgtype.JPG

                imgfile.JPG

                adddevice.JPG

                provisiondevice.JPG

                 

                pxe.log

                [22 Jan 2010 07:30:52,188] [Thread-7] [INFO] [::] [] DatagramSocket received
                [22 Jan 2010 07:30:52,190] [Thread-14] [INFO] [::] [] RPacketProcessor Thread id= 54 started
                [22 Jan 2010 07:30:52,190] [Thread-14] [INFO] [::] [] It is a boot server request packet from /20.5.205.140:4011
                [22 Jan 2010 07:30:52,190] [Thread-14] [INFO] [::] [] Will create light weight prov device object
                [22 Jan 2010 07:30:52,217] [Thread-14] [INFO] [::] [] Provision device 00-50-56-B0-79-DD exists in the system
                [22 Jan 2010 07:30:52,217] [Thread-14] [INFO] [::] [] Provision device object active
                [22 Jan 2010 07:30:52,218] [Thread-14] [INFO] [::] [] IP address of the device :N/A Architecture is x64
                [22 Jan 2010 07:30:52,218] [Thread-14] [INFO] [::] [] Packet type is DHCP Request setting up DHCP ACK packet for reply
                [22 Jan 2010 07:30:52,218] [Thread-14] [INFO] [::] [] makeBootMenu : type 2
                [22 Jan 2010 07:30:52,234] [Thread-14] [INFO] [::] [] State of the device before PXE configuration file:Check State
                [22 Jan 2010 07:30:52,234] [Thread-14] [INFO] [::] [] State of the device after PXE boot :Switch Boot Image
                [22 Jan 2010 07:30:52,261] [Thread-14] [INFO] [::] []  Boot Image Type is WinPE 2.x
                [22 Jan 2010 07:30:52,263] [Thread-14] [INFO] [::] [] Image Location :WinPE2_0_x64\pxeboot.0
                [22 Jan 2010 07:30:52,263] [Thread-14] [INFO] [::] [] Replying to /20.5.205.140:68
                [22 Jan 2010 07:30:52,263] [Thread-14] [INFO] [::] [] RPacketProcessor Thread id= 54 Finished
                [22 Jan 2010 07:30:52,264] [Thread-7] [INFO] [::] [] (U)FD:20
                [22 Jan 2010 07:30:52,264] [Thread-7] [INFO] [::] [] (U)FD:21
                [22 Jan 2010 07:30:52,264] [Thread-7] [INFO] [::] [] (M)FD:22
                [22 Jan 2010 07:30:52,264] [Thread-7] [INFO] [::] [] (M)FD:23

                 

                 

                 

                tftpsvr log:

                [22 Jan 2010 07:30:53,234] [Thread-0] [INFO] Received read request from /20.5.205.140
                [22 Jan 2010 07:30:53,234] [Thread-0] [INFO] Requested filename : X86PC/pxelinux/pxelinux.0
                [22 Jan 2010 07:30:53,236] [Thread-73] [INFO] Sending file : /opt/bmc/bcas/provisioning/tftproot/X86PC/pxelinux/pxelinux.0
                [22 Jan 2010 07:31:09,490] [Thread-0] [INFO] Received read request from /20.5.205.140
                [22 Jan 2010 07:31:09,490] [Thread-0] [INFO] Requested filename : X86PC/pxelinux/pxelinux.0
                [22 Jan 2010 07:31:09,492] [Thread-74] [INFO] Sending file : /opt/bmc/bcas/provisioning/tftproot/X86PC/pxelinux/pxelinux.0
                [22 Jan 2010 07:31:09,529] [Thread-74] [INFO] Completed read request from /20.5.205.140. File name : /opt/bmc/bcas/provisioning/tftproot/X86PC/pxelinux/pxelinux.0
                [22 Jan 2010 07:31:09,583] [Thread-0] [INFO] Received read request from /20.5.205.140
                [22 Jan 2010 07:31:09,584] [Thread-0] [INFO] Requested filename : bootmgr.exe
                [22 Jan 2010 07:31:09,586] [Thread-75] [INFO] Sending file : /opt/bmc/bcas/provisioning/tftproot/bootmgr.exe
                [22 Jan 2010 07:31:10,402] [Thread-75] [INFO] Completed read request from /20.5.205.140. File name : /opt/bmc/bcas/provisioning/tftproot/bootmgr.exe
                [22 Jan 2010 07:31:10,558] [Thread-0] [INFO] Received read request from /20.5.205.140
                [22 Jan 2010 07:31:10,559] [Thread-0] [INFO] Requested filename : \Boot\Fonts\wgl4_boot.ttf
                [22 Jan 2010 07:31:10,561] [Thread-76] [ERROR] File not found : /opt/bmc/bcas/provisioning/tftproot//Boot/Fonts/wgl4_boot.ttf
                [22 Jan 2010 07:31:10,567] [Thread-0] [INFO] Received read request from /20.5.205.140
                [22 Jan 2010 07:31:10,568] [Thread-0] [INFO] Requested filename : \boot.ini
                [22 Jan 2010 07:31:10,569] [Thread-77] [ERROR] File not found : /opt/bmc/bcas/provisioning/tftproot//boot.ini

                • 5. Re: path error in tftp file request
                  Bill Robinson

                  Below is a log of a successful winpe boot from a 7.6 install and I get tons of file not found errors.  On the target, where is it failing?  is it getting past the black screen w/ the progress bar and ip at the bottom?

                   

                   

                   

                   

                  [22 Jan 2010 08:51:22,973] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:22,974] [Thread-0] [INFO] Requested filename : X86PC/pxelinux/pxelinux.0
                  [22 Jan 2010 08:51:22,975] [Thread-58] [INFO] Sending file : /usr/nsh/tftproot/X86PC/pxelinux/pxelinux.0
                  [22 Jan 2010 08:51:39,220] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:39,221] [Thread-0] [INFO] Requested filename : X86PC/pxelinux/pxelinux.0
                  [22 Jan 2010 08:51:39,221] [Thread-59] [INFO] Sending file : /usr/nsh/tftproot/X86PC/pxelinux/pxelinux.0
                  [22 Jan 2010 08:51:39,243] [Thread-59] [INFO] Completed read request from /192.168.65.240. File name : /usr/nsh/tftproot/X86PC/pxelinux/pxelinux.0
                  [22 Jan 2010 08:51:39,298] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:39,298] [Thread-0] [INFO] Requested filename : X86PC/pxelinux/pxelinux.cfg/01-00-0c-29-02-8b-38
                  [22 Jan 2010 08:51:39,298] [Thread-60] [ERROR] File not found : /usr/nsh/tftproot/X86PC/pxelinux/pxelinux.cfg/01-00-0c-29-02-8b-38
                  [22 Jan 2010 08:51:39,301] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:39,301] [Thread-0] [INFO] Requested filename : X86PC/pxelinux/pxelinux.cfg/C0A841F0
                  [22 Jan 2010 08:51:39,302] [Thread-61] [INFO] Sending file : /usr/nsh/tftproot/X86PC/pxelinux/pxelinux.cfg/C0A841F0
                  [22 Jan 2010 08:51:39,303] [Thread-61] [INFO] Completed read request from /192.168.65.240. File name : /usr/nsh/tftproot/X86PC/pxelinux/pxelinux.cfg/C0A841F0
                  [22 Jan 2010 08:51:39,303] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:39,303] [Thread-0] [INFO] Requested filename : X86PC/pxelinux/pxeboot.msg
                  [22 Jan 2010 08:51:39,304] [Thread-62] [INFO] Sending file : /usr/nsh/tftproot/X86PC/pxelinux/pxeboot.msg
                  [22 Jan 2010 08:51:39,373] [Thread-62] [INFO] Completed read request from /192.168.65.240. File name : /usr/nsh/tftproot/X86PC/pxelinux/pxeboot.msg
                  [22 Jan 2010 08:51:39,464] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:39,464] [Thread-0] [INFO] Requested filename : X86PC/pxelinux/boot_2_0\pxeboot.0
                  [22 Jan 2010 08:51:39,464] [Thread-0] [INFO] TFTP will push WinPE files from location boot_2_0
                  [22 Jan 2010 08:51:39,465] [Thread-63] [INFO] Sending file : /usr/nsh/tftproot/X86PC/pxelinux/pxeboot.0
                  [22 Jan 2010 08:51:39,570] [Thread-63] [INFO] Completed read request from /192.168.65.240. File name : /usr/nsh/tftproot/X86PC/pxelinux/pxeboot.0
                  [22 Jan 2010 08:51:39,607] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:39,607] [Thread-0] [INFO] Requested filename : bootmgr.exe
                  [22 Jan 2010 08:51:39,607] [Thread-64] [INFO] Sending file : /usr/nsh/tftproot/bootmgr.exe
                  [22 Jan 2010 08:51:40,289] [Thread-64] [INFO] Completed read request from /192.168.65.240. File name : /usr/nsh/tftproot/bootmgr.exe
                  [22 Jan 2010 08:51:40,790] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:40,791] [Thread-0] [INFO] Requested filename : \Boot\Fonts\wgl4_boot.ttf
                  [22 Jan 2010 08:51:40,795] [Thread-65] [ERROR] File not found : /usr/nsh/tftproot//Boot/Fonts/wgl4_boot.ttf
                  [22 Jan 2010 08:51:40,802] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:40,802] [Thread-0] [INFO] Requested filename : \boot.ini
                  [22 Jan 2010 08:51:40,803] [Thread-66] [ERROR] File not found : /usr/nsh/tftproot//boot.ini
                  [22 Jan 2010 08:51:56,691] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:56,692] [Thread-0] [INFO] Requested filename : \Boot\BCD
                  [22 Jan 2010 08:51:56,718] [Thread-67] [INFO] Sending file : /usr/nsh/tftproot//boot_2_0/BCD
                  [22 Jan 2010 08:51:56,721] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:56,722] [Thread-0] [INFO] Requested filename : \Boot\BCD
                  [22 Jan 2010 08:51:56,724] [Thread-68] [INFO] Sending file : /usr/nsh/tftproot//boot_2_0/BCD
                  [22 Jan 2010 08:51:56,942] [Thread-68] [INFO] Completed read request from /192.168.65.240. File name : /usr/nsh/tftproot//boot_2_0/BCD
                  [22 Jan 2010 08:51:56,943] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:56,943] [Thread-0] [INFO] Requested filename : \Boot\Fonts\wgl4_boot.ttf
                  [22 Jan 2010 08:51:56,944] [Thread-69] [ERROR] File not found : /usr/nsh/tftproot//Boot/Fonts/wgl4_boot.ttf
                  [22 Jan 2010 08:51:56,953] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:56,953] [Thread-0] [INFO] Requested filename : \hiberfil.sys
                  [22 Jan 2010 08:51:56,953] [Thread-70] [ERROR] File not found : /usr/nsh/tftproot//hiberfil.sys
                  [22 Jan 2010 08:51:56,955] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:56,955] [Thread-0] [INFO] Requested filename : \boot_2_0\WinPE.wim
                  [22 Jan 2010 08:51:56,956] [Thread-71] [INFO] Sending file : /usr/nsh/tftproot//boot_2_0/WinPE.wim
                  [22 Jan 2010 08:51:56,958] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:56,958] [Thread-0] [INFO] Requested filename : \boot_2_0\boot.sdi
                  [22 Jan 2010 08:51:56,958] [Thread-72] [INFO] Sending file : /usr/nsh/tftproot//boot_2_0/boot.sdi
                  [22 Jan 2010 08:51:56,960] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:56,960] [Thread-0] [INFO] Requested filename : \boot_2_0\boot.sdi
                  [22 Jan 2010 08:51:56,960] [Thread-73] [INFO] Sending file : /usr/nsh/tftproot//boot_2_0/boot.sdi
                  [22 Jan 2010 08:51:58,908] [Thread-73] [INFO] Completed read request from /192.168.65.240. File name : /usr/nsh/tftproot//boot_2_0/boot.sdi
                  [22 Jan 2010 08:51:59,001] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:51:59,001] [Thread-0] [INFO] Requested filename : \boot_2_0\WinPE.wim
                  [22 Jan 2010 08:51:59,002] [Thread-74] [INFO] Sending file : /usr/nsh/tftproot//boot_2_0/WinPE.wim
                  [22 Jan 2010 08:53:46,612] [Thread-74] [INFO] Completed read request from /192.168.65.240. File name : /usr/nsh/tftproot//boot_2_0/WinPE.wim
                  [22 Jan 2010 08:53:48,359] [Thread-0] [INFO] Received read request from /192.168.65.240
                  [22 Jan 2010 08:53:48,359] [Thread-0] [INFO] Requested filename : \Boot\Fonts\wgl4_boot.ttf
                  [22 Jan 2010 08:53:48,361] [Thread-75] [ERROR] File not found : /usr/nsh/tftproot//Boot/Fonts/wgl4_boot.ttf

                   

                  In my tftproot I've got:

                  tftproot/:
                  X86PC  boot_2_0  bootmgr.exe

                   

                  tftproot/X86PC:
                  pxelinux

                   

                  tftproot/X86PC/pxelinux:
                  pxelinux.cfg  gentoo64  pxeboot.err  pxeboot.msg  pxelinux.0  gentoo32  pxeboot.0

                   

                  tftproot/X86PC/pxelinux/pxelinux.cfg:

                  tftproot/X86PC/pxelinux/gentoo64:
                  gentoo  gentoord.gz

                   

                  tftproot/X86PC/pxelinux/gentoo32:
                  gentoo  gentoord.gz

                   

                  tftproot/boot_2_0:
                  WinPE.wim  BCD  boot.sdi

                  • 6. Re: path error in tftp file request
                    Matt Kreger

                    The client boots, I see Welcome to BladeLogic PXE boot, then I see

                     

                    Boot Server IP <IP address of PXE/TFTPServer>

                    MTFTP.....

                     

                    And it gives TFTP Server timeout and tries to boot from the hard disk.

                     

                    From "welcome" to trying to boot the disk, it takes about 10 seconds.

                    • 7. Re: path error in tftp file request
                      Bill Robinson

                      Do you have the ip address of the tftp server configured in the provision manager 'configuration' area?  and tftp is running?  it seems like it's not even getting to the tftp server.

                      • 8. Re: path error in tftp file request
                        Matt Kreger

                        Yes, and according to the tftpsvr.log it seems to be successfully sending the first couple of files

                         

                        [22 Jan 2010 07:31:09,490] [Thread-0] [INFO] Received read request from /20.5.205.140
                        [22 Jan 2010 07:31:09,490] [Thread-0] [INFO] Requested filename : X86PC/pxelinux/pxelinux.0
                        [22 Jan 2010 07:31:09,492] [Thread-74] [INFO] Sending file : /opt/bmc/bcas/provisioning/tftproot/X86PC/pxelinux/pxelinux.0
                        [22 Jan 2010 07:31:09,529] [Thread-74] [INFO] Completed read request from /20.5.205.140. File name : /opt/bmc/bcas/provisioning/tftproot/X86PC/pxelinux/pxelinux.0
                        [22 Jan 2010 07:31:09,583] [Thread-0] [INFO] Received read request from /20.5.205.140
                        [22 Jan 2010 07:31:09,584] [Thread-0] [INFO] Requested filename : bootmgr.exe
                        [22 Jan 2010 07:31:09,586] [Thread-75] [INFO] Sending file : /opt/bmc/bcas/provisioning/tftproot/bootmgr.exe
                        [22 Jan 2010 07:31:10,402] [Thread-75] [INFO] Completed read request from /20.5.205.140. File name : /opt/bmc/bcas/provisioning/tftproot/bootmgr.exe

                        • 9. Re: path error in tftp file request
                          Bill Robinson

                          if it's getting the bootmgr.exe i think it would get past that tftp timeout error and fail w/ a file not found o the target's screen. (the error would come from bootmgr/winpe, not the pxe loader...but who knows)

                           

                          Can you wipe the log (maybe make a copy first), in the tftpsvr.cf file on one of the first lines change INFO to DEBUG and restart the tftp server.

                           

                          also, can you look in /usr/nsh/tftproot/X86PC/pxelinux/pxelinux.cfg for files and see if they are using the right ip for the tftp server?  (there are a bunch in hex)  you could also try wiping those out before you try this again.

                          • 10. Re: path error in tftp file request
                            Matt Kreger

                            OK. Not really getting anywhere, but it turns out I was misreading what's happening on the client computer, it's not trying to boot from disk, it's just trying (unsuccessfully) to get BCD.

                             

                            noBCD.JPG

                             

                            I found another thread (http://communities.bmc.com/communities/message/107291#107291) where someone was having what looks like the same problem (client is requesting boot/BCD instead of <folder specified in configuration image>/BCD) and they seemed to have found a fix:

                             

                            I checked logs and found the rootcause of the problem. In "Configuring Images" in Provisioning Manager two images were selected as default in which one was of 64 bit. I removed that option and it started reading BCD.

                             

                            This doesn't solve my issue.  I originally only had a 64-bit image, and it was the only one marked default.  This is because I built only one System Package (for Win2K8x64) and apparently because it's a 64-bit OS, I can only choose a 64-bit configuration image.  Anyway, I went ahead and ran CreateWinPE2.bat again and created a 32-bit image and copied it up to the TFTP server, set that configuration image as the only default, and nothing changes.  Still have the same problem where the client is requesting "/boot/BCD" and the TFTP server log says File not found ..tftproot//null/BCD.

                             

                            Where is the client getting the path /Boot/BCD?  Is it in a file I can edit manually?

                             

                            Failing that, why is the TFTP server getting a request for /Boot/BCD and then looking for //null/BCD?  Setting debug in the TFTP server config added only one line to that part of the log, which doesn't shed any light (for me anyway). It addes LOTS of lines to the sections where it successfully sends pxelinux.0 and bootmanager.exe.

                             

                            [25 Jan 2010 07:46:38,050] [Thread-0] [INFO] Received read request from /20.5.205.140
                            [25 Jan 2010 07:46:38,050] [Thread-0] [INFO] Requested filename : \Boot\BCD
                            [25 Jan 2010 07:46:38,055] [Thread-0] [DEBUG] m_ipArchMap = {}
                            [25 Jan 2010 07:46:38,071] [Thread-7] [ERROR] File not found : /opt/bmc/bcas/provisioning/tftproot//null/BCD
                            [25 Jan 2010 07:46:38,071] [Thread-7] [DEBUG] Error on request from /20.5.205.140: File not found

                            • 11. Re: path error in tftp file request
                              Bill Robinson

                              you can have 2 default images, 1 for 64 bit, 1 for 32.  when the box starts booting it tries to figure out what arch it is, and then choosed the appropriate image.  if you don't have one of the images and the box is auto-detected as the missing image arch, they you get the error from the other post...

                               

                              do you have logs of the createwinpe_2.0.bat run?  maybe the image is not generated properly?  to me it looks like there is a problem w/ the image from that screenshot.

                               

                              also, what's in the 'boot images' configuration tab in the PM gui?  what are the paths to the boot images configured to?

                              • 12. Re: path error in tftp file request
                                Matt Kreger

                                OK, I'm going to delete everything and start over, sticking to the 64-bit version for now, since that's what I need to provision.  Here's the whole shebang, maybe you can tell me where I'm screwing it up.

                                 

                                I ran createwinpe2_0.bat as follows (assume amd64 is the choice I need to make, since there is no x64):

                                 

                                C:\Program Files\Windows AIK\Tools\PETools>CreateWinPE2_0 amd64 c:\BladeLogic\provisioning\winpe c:\temp\x64 WinPE2_0_x64
                                Copying amd64 specific Winpe Image to Temp folder c:\temp\x64
                                Mounting amd64 Winpe Image to c:\temp\x64\mount
                                Copying Bladelogic Tools and BMI from c:\BladeLogic\provisioning\winpe to c:\temp\x64\mount\windows\system32
                                Copying Windows AIK PETools and BMI from c:\BladeLogic\provisioning\winpe to c:\temp\x64\mount\windows\system32
                                Starting BCD Creation.
                                  Checking for driver files.
                                Generating Driver Injection code...
                                Reading Driver info into environment...
                                Preinstallation Environment Image Setup Tool for Windows
                                Copyright (C) Microsoft Corporation. All rights reserved.

                                 

                                Installing INF package: C:\drivers\vmware\audio\vmaudio.inf

                                 

                                PEIMG completed the operation successfully.
                                Preinstallation Environment Image Setup Tool for Windows
                                Copyright (C) Microsoft Corporation. All rights reserved.

                                 

                                Installing INF package: C:\drivers\vmware\mouse\vmmouse.inf

                                 

                                PEIMG completed the operation successfully.
                                Preinstallation Environment Image Setup Tool for Windows
                                Copyright (C) Microsoft Corporation. All rights reserved.

                                 

                                Installing INF package: C:\drivers\vmware\video\vmx_svga.inf

                                 

                                PEIMG completed the operation successfully.
                                Preinstallation Environment Image Setup Tool for Windows
                                Copyright (C) Microsoft Corporation. All rights reserved.

                                 

                                Installing INF package: C:\drivers\vmware\vmxnet\vmxnet.inf

                                 

                                PEIMG completed the operation successfully.
                                All done.
                                Checking for Custom Script...
                                Preinstallation Environment Image Setup Tool for Windows
                                Copyright (C) Microsoft Corporation. All rights reserved.

                                 


                                Lang  | Version       | Ins | Name
                                ------+---------------+-----+-----------------------------------------------
                                en-US |6.0.6000.16386 |  +  | WinPE-WMI-Package
                                ------+---------------+-----+-----------------------------------------------
                                      |6.0.6000.16386 |  +  | WinPE-WMI-Package
                                ------+---------------+-----+-----------------------------------------------

                                 

                                Installed 2 package(s).

                                 

                                PEIMG completed the operation successfully.
                                Preinstallation Environment Image Setup Tool for Windows
                                Copyright (C) Microsoft Corporation. All rights reserved.

                                 


                                Lang  | Version       | Ins | Name
                                ------+---------------+-----+-----------------------------------------------
                                en-US |6.0.6000.16386 |  +  | WinPE-Scripting-Package
                                ------+---------------+-----+-----------------------------------------------
                                      |6.0.6000.16386 |  +  | WinPE-Scripting-Package
                                ------+---------------+-----+-----------------------------------------------

                                 

                                Installed 2 package(s).

                                 

                                PEIMG completed the operation successfully.
                                Committing changes to modified amd64 WinPE image.
                                --------------------------------------------------------------------------
                                Summary of operation:
                                > Bladelogic amd64 WinPE image created successfully.
                                --------------------------------------------------------------------------
                                TODO:
                                Please copy c:\temp\x64\WinPE2_0_x64 to tftproot\WinPE2_0_x64 of TFTP server.
                                C:\Temp\x64>

                                 

                                Next, I delete the old stuff in tftproot and recopy:

                                 

                                MKREGER-1% cd //emda-nbp-uea22/opt/bmc/bcas/provisioning/tftproot
                                emda-nbp-uea22% ls -al
                                total 857
                                drwxrwxr-x   5 nobody   nobody       4096 Jan 25 08:15 .
                                drwxrwxr-x   7 root     root         4096 Jan 15 14:28 ..
                                drw-rw-r--   2 root     root         4096 Jan 22 07:26 WinPE2_0_x64
                                drw-r--r--   2 root     root         4096 Jan 25 08:15 WinPE2_0_x86
                                drwxrwxr-x   3 root     root         4096 Jan 19 11:52 X86PC
                                -rwxrw-r--   1 root     root       417896 Jan 21 13:23 bootmgr.exe
                                emda-nbp-uea22% rm -rf WinPE*
                                emda-nbp-uea22% cp -R //@/c/temp/x64/WinPE2_0_x64 .
                                emda-nbp-uea22% chmod -R 644 WinPE2_0_x64
                                emda-nbp-uea22% ls -al
                                total 849
                                drwxrwxr-x   4 nobody   nobody       4096 Jan 25 09:50 .
                                drwxrwxr-x   7 root     root         4096 Jan 15 14:28 ..
                                drw-r--r--   2 root     root         4096 Jan 25 09:50 WinPE2_0_x64
                                drwxrwxr-x   3 root     root         4096 Jan 19 11:52 X86PC
                                -rwxrw-r--   1 root     root       417896 Jan 21 13:23 bootmgr.exe
                                emda-nbp-uea22%

                                emda-nbp-uea22% ls -al WinPE2_0_x64
                                total 367201
                                drw-r--r--   2 root     root         4096 Jan 25 09:50 .
                                drwxrwxr-x   4 nobody   nobody       4096 Jan 25 09:50 ..
                                -rw-r--r--   1 root     root       262144 Jan 25 09:50 BCD
                                -rw-r--r--   1 root     root     184565987 Jan 25 09:51 WinPE.wim
                                -rw-r--r--   1 root     root      3170304 Jan 25 09:50 boot.sdi

                                 

                                  I set up the Image file as follows:

                                 

                                64-bit boot image.JPG

                                 

                                I add the device in Provisioning Manager Console:

                                add_device.JPG

                                I provision the device:

                                provision_device.JPG

                                prov_prog.JPG


                                I power on the device, same thing happens.  Device asks for \Boot\BCD, TFTP server can't find //null/BCD

                                • 13. Re: path error in tftp file request

                                  When you setup the boot image did you specify "boot"

                                  as the image path/kernal name??. Since I see "null" in the path it seems to not be picking up the value. When you build the WinPE image make sure you specify "boot" as the folder. This cannot be renamed as "boot" is embedded in the image as a relative path.

                                   

                                  Also, on Linux the paths will be case sensitive so make sure the filenames are the same case as the path being doled out. You can validate case issues by matching the requested paths in the PXE/TFTP log with the names on the filesystem.

                                   

                                  Based on the screenshots I viewed in the thread I would expect ..../tftproot/Boot/BCD

                                   

                                  So... validate

                                   

                                  1. Your folder is called "Boot".

                                  2. BCD is all caps

                                  3. the Image Path in the image setup should be "Boot" and not "WinPE2_0_x64"

                                  4. If you want to keep "WinPE2_0_x64" as the image path you will need to regenerate the WinPE image and use "WinPE2_0_x64 as the target image folder name.

                                  • 14. Re: path error in tftp file request
                                    Matt Kreger

                                    When you setup the boot image did you specify "boot" as the image path/kernal name?

                                     

                                    Based on what I've read from the documentation, the image path/kernal name is set from a parameter passed to CreateWinPE2_0.bat.  This is what I ran:

                                     

                                    CreateWinPE2_0 amd64 c:\BladeLogic\provisioning\winpe c:\temp\x64 WinPE2_0_x64

                                     

                                    Is there somewhere else where that is done? I've never specified "Boot" in any of the steps I've followed.

                                    1 2 Previous Next