Failed to close inode
-
FOG 1.5.0 RC-9
Client: 0.11.12Please see the below picture. Trying to capture a Windows 10 LTSB image from a HP EliteBook 8460p. Debug capture fails at this point. Already ran chkdsk and sfc on it.
-
@tom-elliott I pulled the latest working and it got past that point to partclone. I’m not sure what fixes were implemented, but they seemed to have worked. If you need any additional info that I can provide in order to pinpoint this issue, please let me know.
-
@fry_p Please read through this thread: https://forums.fogproject.org/topic/10861/error-when-capturing-image
-
@sebastian-roth I will try some of the things in the thread tomorrow, but it looks like the final result was having to re-create the image from scratch? I am also sysprepping the same as the other thread and I encounter 0 errors when it does the OOBE stuff coming out of sysprep after the task fails to upload.
-
@fry_p We still have not found the root cause of this I’m afraid. To me it kind of looks like this is happening more and more often since we have the latest Windows build around. But I am not sure.
The inode numbers in your screenshot are very high and kind of look like being way beyond the disk. That way I’d understand the “Input/output error” message, as it can’t read beyond the disk’s capacity…
Keep trying and let us know. Hopefully we’ll figure it out at some point.
-
Some questions come up.
How big is this hard drive? Is this in GPT or MBR format? Is the disk an Advanced Format (4k) disk?
-
@tom-elliott It is a WD2500BEKT 250 GB Notebook Drive. It is a standard MBR format and I don’t know how to identify if this is Advanced format. I included the model just in case you can glean that info from it.
-
@fry_p said in Failed to close inode:
WD2500BEKT
According to the spec sheet, this is a normal drive (non Advanced Format Disk, those are labeled WD####BPKT). However, would you mind trying working branch? I’m guessing you’re running into this issue on capture, I’m just wondering if the fixes in the working branch might be helpful for what you’re seeing (though I kind of doubt it at this point.)
-
@tom-elliott I pulled the latest working and it got past that point to partclone. I’m not sure what fixes were implemented, but they seemed to have worked. If you need any additional info that I can provide in order to pinpoint this issue, please let me know.
-
@fry_p Great to hear that working is doing the job for you. Which FOG version exactly did you use before?
-
@sebastian-roth I should have checked that before updating
My bad, is there a way to look at the previous git pulls? I was on RC-9, but had not updated for quite a period of time until now. -
@fry_p If the “version” stated 1.5.0-RC-9 in the top, then you were likely on
dev-branchfrom git, so you’d have been on that particular version. -
@fry_p said in Failed to close inode:
My bad, is there a way to look at the previous git pulls?
Nut the pulls but the
git checkouts you can. Just run this:git checkout - Switched to branch '....'You should see the name of the previous branch you were on. Just be careful to not run the installer again being on that “older” branch. Note it down/post here and then switch back to working:
git checkout working
