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

RAMDISK: incomplete write (-28 !=4096)

Scheduled Pinned Locked Moved Solved
FOG Problems
2
6
973
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.
  • K
    kwisher
    last edited by Dec 10, 2019, 1:13 PM

    Hello All,

    Upgraded to Trunk this morning and now receiving the ramdisk error in the topic on a client trying to deploy an image. Any suggestions for a fix?

    TIA

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by george1421 Dec 10, 2019, 7:58 AM Dec 10, 2019, 1:58 PM

      First thing, the upgrade to trunk is an old, old process (pre 1.4.4). If you are on the 1.5.7 dev branch then that is the right location to be.

      The error is because the ram disk minimum size was changed in 1.5.6 or 1.5.7 (I don’t remember which). You need to update a FOG Configuration->Fog Settings parameter->TFTP Server->KERNEL RAMDISK SIZE set it to 275000 from the original value of 127000

      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!

      K 2 Replies Last reply Dec 10, 2019, 3:00 PM Reply Quote 0
      • K
        kwisher @george1421
        last edited by Dec 10, 2019, 3:00 PM

        @george1421 said in RAMDISK: incomplete write (-28 !=4096):

        275000

        Thank you. Changing that setting solved the problem. Now, can you provide a link to the proper instructions on how to update to the latest stable branch?

        G 1 Reply Last reply Dec 10, 2019, 3:07 PM Reply Quote 0
        • G
          george1421 Moderator @kwisher
          last edited by Dec 10, 2019, 3:07 PM

          @kwisher So you used the git method (if you followed the upgrade to trunk instructions)?

          If so what version does fog say its at in the fog configuration? 1.5.7.55 or later?

          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!

          1 Reply Last reply Reply Quote 0
          • K
            kwisher @george1421
            last edited by Dec 10, 2019, 4:59 PM

            @george1421 Found the instructions to get on the master branch. Life is good again.

            Thanks for the quick response 🙂

            G 1 Reply Last reply Dec 10, 2019, 6:04 PM Reply Quote 0
            • G
              george1421 Moderator @kwisher
              last edited by Dec 10, 2019, 6:04 PM

              @kwisher Well life may be better on the dev branch. Why I asked if you were on 1.5.7.55 or later, stay there. FOG 1.5.8 is almost release. 1.5.7 had a few bugs where 1.5.7.55+ in the dev branch fixed.

              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!

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

              139

              Online

              12.0k

              Users

              17.3k

              Topics

              155.2k

              Posts
              Copyright © 2012-2024 FOG Project