1803 update Error 'Could not open inode 500174 through the library'
I found several topic about this problem but no one resolve my issue…
Fog 1.5.4 - Debian 9
I test kernel 4.15.2 - 4.16.6 - 4.17.0
I’ve just updated my win10 image to 1803, and when I try to capture image Fog return this error :
Important note : I test without sysprep and same problem. This error occurs when I delete windows.old folder ! I don’t understand why, but I can capture image after 1803 update before deleting windows.old folder. After deleting this folder (and it’s the only change) I can’t upload image, and when I restart computer boot partition (system reserved) is resized…
Very strange …
Thanks for your help
Ok all seems fine now, thanks you Quazz
Except than when I execute sysprep, all metro appx are gone after reboot, no more calculator or store…
Seems to be a Windows 10 1803 upgrade problem, one more thing I’m trying to resolve…
@quazz Thanks !
I have no time to test today and I’m out of office tomorrow but I continue test on wednesday
@matthieu-jacquart They are part of 1.5.4 I think, yes.
I just realised there’s a couple of scripts I always run, maybe they can help these situations as well.
I think one of the relevant things to run before sysprep is
dism /online /cleanup-image /startcomponentcleanup
In a Administrator cmd/powershell window.
I also run
dism /online /cleanup-image /restorehealth sfc /scannow chkdsk C: /f
afterwards to verify integrity before sysprep, though unsure how relevant any of this is of course.
The first one should do most of the heavy lifting and might resolve the issue at hand entirely.
@quazz Yes I found this topic and I’ll try Tom’ solution on monday.
wget --no-check-certificate -O /var/www/fog/service/ipxe/init.xz https://fogproject.org/inits/init.xz
wget --no-check-certificate -O /var/www/fog/service/ipxe/init_32.xz https://fogproject.org/inits/init_32.xz
But I suppose these modifications have been implemented in fog 1.5.4 since time ?
I thought this seemed familiar so I searched around a bit and found the following thread of a few months ago:
Yes I used windows cleanmgr to delete windows.old and run chkdsk after.
I’ll try to delete windows.old with ccleaner and defrag disk to test…
I know best way is to make fresh install but there’s so much software to install on this image…
File d1.fixed_size_partitions is empty in image folder
Do you use Windows own cleanmgr to remove Windows.old?
At any rate, it may be necessary to defrag and chkdsk after doing so.
I tend to just create new images at new version points to prevent the upgrade hassle.
As for the resizing of the System Reserved paritition, I believe this is a long standing problem to do with how FOG tries to detect it (regex that looks for System Reserved) which is not cross language compatible currently. Manually defining that partition in the fixed file of the image should be fine. (eg 1:3: probably in your case)