Client capture issue (lenovo laptop)
-
Lenovo B50-30 Touch laptop. I was able to load a base Windows 7 Pro image on it, then loaded the rest of the programs & apps needed for this touch version of this laptop, then wanted to capture to a new image. Download worked fast and perfectly. Capture keeps failing with "ERROR(5): could not open inode 182234 through the library: Input/output error (shirnkPartition) Args Passed: /dev/sda3 /images/f896334549d/d1.original.fstypes :1:2
Anyone have any idea what’s going on here?
-J
-
No one? Buehler?
-
@jim-holcomb said in Client capture issue (lenovo laptop):
ERROR(5): could not open inode 182234 through the library
We have seen this error a couple of times lately. Read this if you sysprep: https://forums.fogproject.org/topic/10313/error-capture-windows-10-creator-update-sysprep-could-not-open-inode-xxxxxx-through-the-library
Which version of FOG do you run? See in the blue cloud on the web interface.
-
Estimated FOG Sites: 4086
Latest Version: 1.4.4
Latest Development Version: 1.5.0-RC-9
Latest SVN Version:Running Version 24
SVN Revision: 6079
Oct 16, 2017 14:51 pmI do not sysprep. This is a straight-forward image capture. I can capture same laptop with single disk - not resizeable, but who wants a 1tb image?
-
@jim-holcomb Please try turning off Bitlocker.
-
Of course this is just a guess. I’d also follow the instructions as @Sebastian-Roth Suggested, though as you’re not sysprepping, you may look at turning off Fast Boot.
-
@tom-elliott Neither are enabled. Fast Boot was not an option in this Bios version, and this is a fresh OS that I created manually. BitLocker most certainly was not an option I installed. So why then does the Single Disk - not resizeable work, and nothing else?
-
@jim-holcomb Fast Boot is normally an OS thing.
The reason Single Disk - Resizable is likely having a problem is because it shifts around the partition end points to actually capture the data. From the sounds of things, it’s missing one part.
Mind re-updating to the latest working. Version 24 is fairly outdated now. We’re up to Version 67 on the working branch now iirc.
-
OP is using Windows 7 as capture image, so Fast Boot won’t be able to cause issues here (since it doesn’t have that option anyway).
I recommend running a chkdsk /f on the Windows partition to start with. Might also want to do a SMART check as some sectors may be defective.
-
@quazz You’re right. Must have been a bad spot or something. One thing we all know Windows does is to add a minimum of two partitions on a clean install. Mine had 3 (ms system reserved, empty) partition. Did lots of research, found I don’t need three, just setup GPT with single partition, did base install, and now FOG imaging upload works.
Thanks for pointing me in the right direction.
