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

    "Could not open inode XXXXXX through the library..." Windows 10 1803

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    3
    9
    878
    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.
    • J
      jeffj
      last edited by

      So I am trying to update my image of a machine I updated to Winodws 10 Version 1803 (Spring update 2018) and I am getting the “Error Could Not Open inode XXXXXXX Through Library”

      I visited the (https://forums.fogproject.org/topic/11207/error-could-not-open-inode-xxxxxx-through-the-library) and updated the init.xz and the init_32.xz files and tried to re-run the capture task but am still having the same error occur.

      I will note I ran disk cleanup and removed previous windows installations before trying to update this image to reduce the size of the image as much as possible.

      Server Info
      FOG Version 1.5.2
      Ubuntu 16.04 LTS

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by

        @jeffj Did you try defragging the disk a couple of times before capturing?

        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
        • J
          jeffj
          last edited by

          No I hadn’t.

          Since you suggested it I did and it appears to be working now. Glad it was such an easy fix! Thanks!

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

            I’m going to suspect that MS tweaked the disk image format yet again (as with 1709). With 1803 being very new, the opensource community hasn’t had a chance to create yet another patch for this new configuration. It may take the developer of ntfs-3g code a while to fix this one too.

            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!

            J 1 Reply Last reply Reply Quote 0
            • J
              jeffj @george1421
              last edited by jeffj

              @george1421 Actually as long as you update the init.xz and init_32.xz it appears to work in 1803!

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

                @jeffj Sorry I was writing and researching at the same time. I missed your previous post.

                So just to be clear the 1.5.3 (unreleased as of now) inits plus defragmenting your hard drive fixed the issue?

                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!

                J 1 Reply Last reply Reply Quote 0
                • J
                  jeffj @george1421
                  last edited by

                  @george1421 Correct

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

                    @jeffj Sweet!! thank you for the feed back. The FOG developers will like this info.

                    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!

                    J 1 Reply Last reply Reply Quote 0
                    • J
                      jeffj @george1421
                      last edited by

                      @george1421

                      Also, something to note, I had another machine I was testing this on and if you do not do the disk cleanup and remove the old windows installations the new inits work just fine. It appears the cleanup messes something up for some reason.

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

                      238

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project