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

    Can't read the following volume file: /stdin001

    Scheduled Pinned Locked Moved
    FOG Problems
    2
    4
    945
    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.
    • S
      sysadmininstalls
      last edited by

      We are on fog 1.2.0 and attempting to restore images made back with fog 0.32 is giving the message "Can’t read the following volume file: /stdin001 ".

      They are set to partimage since they are so old.

      The /images directory contains the correct files and they all have 777 perms.

      1 Reply Last reply Reply Quote 0
      • S
        sysadmininstalls
        last edited by

        this is the result of someone changing the image type to raw when it is not.
        This was solved by switching the image type back to the correct option.

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

          If you’ve still got your .32 build, I’d say use that to deploy this image, then upload a new image using 1.2.0.

          However, others may have a better solution so keep an eye on this thread.

          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
          • Wayne WorkmanW
            Wayne Workman
            last edited by

            [quote=“sysadmininstalls, post: 47327, member: 28544”]this is the result of someone changing the image type to raw when it is not.
            This was solved by switching the image type back to the correct option.[/quote]

            Good deal.

            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
            • 1 / 1
            • First post
              Last post

            229

            Online

            12.0k

            Users

            17.3k

            Topics

            155.2k

            Posts
            Copyright © 2012-2024 FOG Project