• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    No such file or directory after successful cloning

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    5
    327
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      ArtemZ
      last edited by ArtemZ

      Hello, I am having trouble creating an image of my Latitude E7450. After creating an image I get the “Cloning successful” message, after which it gives me an error at “Updating Database” which says “Failed to open steam: no such file or directory”. Thank you in advance
      20220714_091618.jpg
      20220714_091658.jpg

      Edit: here is the screenshot of images I have. Will it work?
      2d034351-85b8-4bd8-83c1-10a0aaa3c216-image.png

      Update: I tried uploading the image to a new device, it didn’t work:
      20220714_095211.jpg

      A 2 Replies Last reply Reply Quote 0
      • A
        ArtemZ @ArtemZ
        last edited by

        Ubuntu version: 22.04
        FOG version 1.5.9.154

        1 Reply Last reply Reply Quote 0
        • A
          ArtemZ @ArtemZ
          last edited by

          Also, here is the error I am getting after the “no such file or directory” while creating an image.20220714_091711.jpg

          george1421G 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator @ArtemZ
            last edited by george1421

            @artemz Ok the thing that jumps out at me is that in the path just before the failed to open stream there is a preceding t that shouldn’t be there. I’m not sure if it is an artifact of the error message or someone accidentally put a t at the beginning of the storage node path in the default definition. t/images is surely an incorrect answer.

            The step where it is failing is that the image has been uploaded to the FOG server in /images/dev/<mac address> The FOS Engine connects to the FOG server using FTP and issues a move command from /images/dev/<mac_address> to the protected /images/<image_name> directory. The error is saying its unable to find the /images/dev/<mac_address> directory to move it.

            Once you find where that extra t is coming from then you should delete that /images/dev/<mac_address> or just manually move the directory to where FOG would have stored it and named correctly. The upload was complete just the FOS Engine could complete all of the steps. There should be no directories in /images/dev that look like mac address unless you are actively uploading an image. If they exist with no active uploads going on, you can delete just those directories because they are botched uploads and are just taking up space.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            A 1 Reply Last reply Reply Quote 1
            • A
              ArtemZ @george1421
              last edited by

              @george1421 removing the t/ from web gui fixed the problem. Thanks a lot!

              1 Reply Last reply Reply Quote 1
              • 1 / 1
              • First post
                Last post

              151

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project