Error 'Could not open inode 'XXXXXX" through the library'
-
@szeraax said in Error 'Could not open inode 'XXXXXX" through the library':
I decided to do your fix before checkdisk, defrag, or resize. Is now capturing an image!
Great to hear. Sounds like the fix actually is working! Awesome.
-
I don’t know what the problem was. All I did was patch the ntfs-3g files with the suggested fixes from Sebastian and rebuilt the inits with the changes.
-
@sebastian-roth I agree! Well done sir. Do you care to explain what was happening? Or is to too long that you don’t even want to sum up?
-
@Szeraax As I am not the developer of the ntfs-3g stuff I can only guess on what exactly was wrong. We try to resize the partition / filesystem to a size relativly close to the actual size of the data for capturing a resizable image and this seems to be a kind of peculiar case where things can go wrong more easily. I don’t know why this issue can be triggered by removing old Windows install data though.
-
@sebastian-roth Cool cool. thanks!
-
@Sebastian-Roth @Tom-Elliott Huge thanks for the fix. 1709 is uploading after updating init and init_32.
-
This post is deleted! -
Hi everybody,
With my new FOG 1.5.9, I have the same problem after removing the old windows installation (=> 20H2), exactly the same as described in this post ! Was the fix init.xz included in the latest version 1.5.9 ?
-
@scoude Yes, looks like we still have the patches mentioned in our inits (each and ever init since then, including 1.5.9): https://github.com/FOGProject/fos/blob/master/Buildroot/package/ntfs-3g/ntfs-mft-fixes.patch
Please make sure you have disabled fastboot, run chkdsk, and maybe even defrag before you capture.
-
Hi,
Same problem as Scoude here with Fog 1.5.9 on Debian 10.
I “defraged” (it’s a ssd), desactivated Fastboot, hibernate off, chkdsk…
Nothing fixed the problem.Any idea ?
Thanks