B

BxRyce2014

Member

Last active last week

  1. last week
    Mon Oct 16 15:51:49 2017

    Having same issue.

    I had two CF-53's hooked up. Both laptop are identical as far as hardware goes. Both completed the cloning process without error but one is going into Automatic Recovery while the other is working just fine.

    All have same HD's and RAM. I went ahead and replaced both, and the HD cable just to check, but am getting the same error.
    Did not do sysprep and all BIOS are matching from the machines that did clone properly compared to these.

    I can easily do this PC manually but my last batch did the same thing and I had to manually do the last 6 I had.

    Any ideas?

  2. 2 weeks ago
    Wed Oct 4 19:16:42 2017
    B BxRyce2014 posted in No Such File Or Directory.

    You are now my best friend. Thank you!

  3. Wed Oct 4 19:10:02 2017
    B BxRyce2014 posted in No Such File Or Directory.

    From tftpd32
    C:\inetpub\wwwroot\cruciblewds\tftpboot

    From Boot Menu
    C:\Program Files (x86)\clonedeploy\tftpboot\pxelinux.cfg\default.ipxe

  4. Wed Oct 4 18:54:42 2017
    B BxRyce2014 posted in No Such File Or Directory.

    Connection received from 192.168.1.102 on port 1210 [04/10 14:54:32.528]
    Read request for file <pxeboot.0>. Mode octet [04/10 14:54:32.528]
    OACK: <tsize=882048,> [04/10 14:54:32.528]
    Using local port 50319 [04/10 14:54:32.528]
    Peer returns ERROR <User aborted the transfer> -> aborting transfer [04/10 14:54:32.528]
    Connection received from 192.168.1.102 on port 1211 [04/10 14:54:32.544]
    Read request for file <pxeboot.0>. Mode octet [04/10 14:54:32.544]
    Using local port 50320 [04/10 14:54:32.544]
    <pxeboot.0>: sent 1723 blks, 882048 bytes in 3 s. 0 blk resent [04/10 14:54:35.048]
    Connection received from 192.168.1.102 on port 53311 [04/10 14:54:38.885]
    Read request for file <pxelinux.cfg/default.ipxe>. Mode octet [04/10 14:54:38.885]
    OACK: <tsize=1920,> [04/10 14:54:38.885]
    Using local port 50321 [04/10 14:54:38.885]
    <pxelinux.cfg\default.ipxe>: sent 4 blks, 1920 bytes in 0 s. 0 blk resent [04/10 14:54:38.901]
    Connection received from 192.168.1.102 on port 7714 [04/10 14:54:38.901]
    Read request for file <pxelinux.cfg/01-a8-13-74-3f-dc-d3.ipxe>. Mode octet [04/10 14:54:38.901]
    File <pxelinux.cfg\01-a8-13-74-3f-dc-d3.ipxe> : error 2 in system call CreateFile The system cannot find the file specified. [04/10 14:54:38.901]
    Connection received from 192.168.1.102 on port 16635 [04/10 14:54:38.901]
    Read request for file <pxelinux.cfg/01-.ipxe>. Mode octet [04/10 14:54:38.901]
    File <pxelinux.cfg\01-.ipxe> : error 2 in system call CreateFile The system cannot find the file specified. [04/10 14:54:38.901]

    I noticed the "User aborted the transfer" error message. That popped up during the Downloading NPB file. Before the menu options even appeared.

  5. Wed Oct 4 18:40:19 2017
    B BxRyce2014 posted in No Such File Or Directory.

    Not using Proxy DHCP and file path is set to
    "C:\Program Files (x86)\clonedeploy\tftpboot\" inside of the config.

    Worse comes to worst I can just reinstall everything over again but not sure if I'll run into the same issue doing so.
    Trying now too see if I can get anything else to log.

  6. Wed Oct 4 18:25:34 2017
    B BxRyce2014 posted in No Such File Or Directory.

    ***Couldn't get ScreenShot but this is verbatim whats in Editor***

    #!ipxe

    chain 01-${net0/mac:hexhyp}.ipxe || chain 01-${net1/mac:hexhyp}.ipxe || goto Menu

    :Menu

    menu Boot Menu

    item bootLocal Boot To Local Machine

    item clonedeploy CloneDeploy

    item console Client Console

    choose --default bootLocal --timeout 5000 target && goto ${target}

    :bootLocal

    exit

    :

    clonedeploy

    kernel http://192.168.1.100/clonedeploy/api/ClientImaging/IpxeBoot?filename=4.5x64&type=kernel initrd=initrd.xz root
    =/dev/ram0 rw ramdisk_size=156000 web=http://192.168.1.100/clonedeploy/api/ClientImaging/ USER_TOKEN= consoleblank=0
    imgfetch --name initrd.xz http://192.168.1.100/clonedeploy/api/ClientImaging/IpxeBoot?filename=initrd.xz&type=bootimage

    boot

    :console

    kernel http://192.168.1.100/clonedeploy/api/ClientImaging/IpxeBoot?filename=4.5x64&type=kernel initrd=initrd.xz root=/dev/ram0 rw ramdisk_size=156000 web=http://192.168.1.100/clonedeploy/api/ClientImaging/ USER_TOKEN= task=debug consoleblank=0
    imgfetch --name initrd.xz http://192.168.1.100/clonedeploy/api/ClientImaging/IpxeBoot?filename=initrd.xz&type=bootimage

    boot

  7. Wed Oct 4 18:06:06 2017
    B BxRyce2014 posted in No Such File Or Directory.

    Only logs I've gotten since the update. These are from CloneDeployFE.log

    2017-10-04 13:01:24,353 [56] ERROR CloneDeploy_ApiCalls.ApiRequest Response Data Was Null For Resource: api/ImageProfile/Get/0
    2017-10-04 13:57:30,026 [58] ERROR CloneDeploy_ApiCalls.ApiRequest Response Data Was Null For Resource: api/ActiveImagingTask/RecreatePermanentTasks/

  8. Wed Oct 4 17:57:06 2017
    B BxRyce2014 posted in No Such File Or Directory.

    Default Boot Menu was recreated several times. Even selecting new PXE Modes and trying different Kernels it gives the same "Directory Not Found" error because that directory doesn't exist.

  9. Wed Oct 4 17:47:46 2017
    B BxRyce2014 started the conversation No Such File Or Directory.

    Trying to Clone a bunch of new Panasonic CF-33 Toughbooks but I'm now stuck and not quite sure what to do next. We recently upgraded to 1.3.0 today and everything on the web is now up and running. I made a new Image for the Toughbook, did a restart to boot into LAN, then my options come up so I go scroll down to On Demand. After selecting On Demand I now get the following...

    http://192.168.x.x/clonedeploy/service/client.asmx/IpxeBoot?filename-4.5x648type-kernal...No such file or directory
    Could not boot

    There looks to be no "service" folder in place which is the issue here but not quite sure how to fix it.
    My Base URL is set directly to "http:\\192.168.x.x\clonedeploy\"

  10. Wed Oct 4 17:36:19 2017
    B BxRyce2014 joined the forum.