"Could not open inode XXXXXX through the library..." Windows 10 1803
-
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 -
@jeffj Did you try defragging the disk a couple of times before capturing?
-
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!
-
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.
-
@george1421 Actually as long as you update the init.xz and init_32.xz it appears to work in 1803!
-
@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?
-
@george1421 Correct
-
@jeffj Sweet!! thank you for the feed back. The FOG developers will like this info.
-
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.
