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

Could not open inode XXXXXX through the library..."

Scheduled Pinned Locked Moved
FOG Problems
4
7
2.3k
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
    John L Clark
    last edited by Apr 13, 2017, 3:31 PM

    I am getting this error on every machine I am trying to capture the image from. I have not changed my process at all. Not sure how to resolve this.

    Q 1 Reply Last reply Apr 13, 2017, 3:33 PM Reply Quote 0
    • Q
      Quazz Moderator @John L Clark
      last edited by Quazz Apr 13, 2017, 9:33 AM Apr 13, 2017, 3:33 PM

      @John-L-Clark Please provide more details such as:

      Types of machines
      Storage medium used
      OS installed/partition layout

      Perhaps a screenshot of the error would be helpful too.

      1 Reply Last reply Reply Quote 0
      • J
        John L Clark
        last edited by Apr 13, 2017, 3:39 PM

        @Quazz one was a lenovo E460 windows 10, Lenovo Yoga 11E.

        0_1492097969552_IMG_3223.JPG

        1 Reply Last reply Reply Quote 0
        • J
          John L Clark
          last edited by Apr 13, 2017, 3:41 PM

          I have run chkdsk /r and let the machine reboot and they tried to capture, but still get this error

          1 Reply Last reply Reply Quote 0
          • V
            Vasahond
            last edited by Apr 13, 2017, 10:54 PM

            I’ve had this problem as well. Windows 10 / SSD / Dell Optiplex 5040; no special partitioning (one system partition, one Windows partition). Also, I am running FOG 1.4.0 RC4. Same as the above user; checked for “dirty” bit in Windows, tried running chkdsk, and so forth, but all to no avail.

            1 Reply Last reply Reply Quote 1
            • X
              x23piracy
              last edited by Jun 21, 2017, 1:45 PM

              Hi,

              before you sysprep try to run chkdsk, if chkdsk was ok run sysprep but don’t use option /reboot or /shutdown just use /quit, then manually shutdown your machine with shutdown -s -t 0 -f, then try to image.

              Regards X23

              ║▌║█║▌│║▌║▌█

              X 1 Reply Last reply Jun 22, 2017, 8:08 AM Reply Quote 1
              • X
                x23piracy @x23piracy
                last edited by Jun 22, 2017, 8:08 AM

                @x23piracy said in Could not open inode XXXXXX through the library...":

                Hi,

                before you sysprep try to run chkdsk, if chkdsk was ok run sysprep but don’t use option /reboot or /shutdown just use /quit, then manually shutdown your machine with shutdown -s -t 0 -f, then try to image.

                Regards X23

                That has worked for the guy here: https://forums.fogproject.org/post/97015

                ║▌║█║▌│║▌║▌█

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

                185

                Online

                12.0k

                Users

                17.3k

                Topics

                155.2k

                Posts
                Copyright © 2012-2024 FOG Project