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

    Problem while deploying image

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    4
    1.4k
    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.
    • G
      gsmith
      last edited by gsmith

      Server
      • FOG Version: 1.3.0
      • OS: Ubuntu 14.04
      Client
      • Service Version:
      • OS:
      Description

      Have updated from 0.32 to 1.20 in summer. Then recently. I’ve updated again to 1.3.0. installation went fine with no issues. Uploaded the image files (using ftp) to home/fog/images and tried to deploy. Mid-image, I get:

      … volume file
      /stdin.001

      : corrupted – invalid deflate data (invalid block type)
      pigz: bort: internal … s error

      Will upload picture soon.

      Thanks

      EDIT:

      Images worked fine on 1.2.0 with no issues

      1 Reply Last reply Reply Quote 0
      • G
        gsmith
        last edited by

        Hi guys,

        First of all, thanks for your support and patience.

        Fortunately, I found what was wrong with the images.

        Unfortunately, I had to put the server down and start a new on a slightly newer server which had been collecting dust.

        The issue here was that the hard drives were failing and a number of sectors were found with errors. The server was from 2006 and I’m pretty sure the hard drives were the same age…

        The image I had was transferred from 0.32, to 1.20 then to 1.30 using part image and moved using FTP. I’ve recaptured the original images using part clone on 1.3.0 with the newer server and decided to start from scratch.

        Thanks again for your help. It’s very much appreciated.

        1 Reply Last reply Reply Quote 0
        • Tom ElliottT
          Tom Elliott
          last edited by

          Typically, This would indicate a problem with the image. The scripts managing imaging may have changed, but the way the data is stored/used (while a bit of compatibility was needed first) hasn’t changed when it comes to handling deployments.

          Seeing as you stated you uploaded the images how did you go about this? Did they properly upload? If you still have the original, if you do a checksum comparison between the original the uploaded file (on the new server) do they match?

          Where is /stdin.001 coming in? FOG now uses /tmp/pigz1 as the location in memory via a FIFO system to handle the incoming data flow.

          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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          1 Reply Last reply Reply Quote 0
          • Wayne WorkmanW
            Wayne Workman
            last edited by Wayne Workman

            What version of fog was used to capture this particular image?

            Also, is the problem with all images, or just this one?

            Please post a photo of the error so we can see the entire monitor and other information it’s displaying.

            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!
            Daily Clean Installation Results:
            https://fogtesting.fogproject.us/
            FOG Reporting:
            https://fog-external-reporting-results.fogproject.us/

            1 Reply Last reply Reply Quote 0
            • G
              gsmith
              last edited by

              Hi guys,

              First of all, thanks for your support and patience.

              Fortunately, I found what was wrong with the images.

              Unfortunately, I had to put the server down and start a new on a slightly newer server which had been collecting dust.

              The issue here was that the hard drives were failing and a number of sectors were found with errors. The server was from 2006 and I’m pretty sure the hard drives were the same age…

              The image I had was transferred from 0.32, to 1.20 then to 1.30 using part image and moved using FTP. I’ve recaptured the original images using part clone on 1.3.0 with the newer server and decided to start from scratch.

              Thanks again for your help. It’s very much appreciated.

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

              197

              Online

              12.1k

              Users

              17.3k

              Topics

              155.3k

              Posts
              Copyright © 2012-2024 FOG Project