Filesystem check error after capturing W10 image.
-
After breaking my head for a couple of days, I was able to install a FOG Node on a Windows Server 2012 R2 and the Fog server redirecting to it. And having the option for it to boor using EFI.
But now I’m trying to capture a Windows 10 image I created on a Hyper-V. It captures everything but at the end of the last partition I get the error that shows in the image attached.
I’ve tried using sysprep as I always did before, tried a forced shutdown, turning hibernate off… nothing works. Always the same error.
For this image I created a GEN2 VM on Hyper-V, booted via EFI.
Can anybody help me? Thank you.
PS: I’m running the CHKDSK /F right now.
-
Most often, this happens because of what Microsoft has enabled to make rebooting much faster (or booting after a shutdown specifically.) This is called Fast boot in windows and basically flicks the “dirty bit” on the HDD which causes issues like this.
You can disable fast boot with:
powercfg /h offas an administrator of course. -
@Tom-Elliott said in Filesystem check error after capturing W10 image.:
Most often, this happens because of what Microsoft has enabled to make rebooting much faster (or booting after a shutdown specifically.) This is called Fast boot in windows and basically flicks the “dirty bit” on the HDD which causes issues like this.
You can disable fast boot with:
powercfg /h offas an administrator of course.I did that. no luck.
-
@luis-acacio Current Volume Size and New Volume Size are very close together. Is this correct? Is your Windows partition (sda4) only 12870 MB in the first place? I can imagine this being a problem. Wonder that shrinking it does even work!??!
Edit: Possibly the small size is just because there was another issue initially that prevented FOG from expanding the partition after capture and now you are kind of stuck with the small partition. Please boot up Windows 10 and try to expand that partition to it’s full size. Then try capture again.
-
@Sebastian-Roth said in Filesystem check error after capturing W10 image.:
@luis-acacio Current Volume Size and New Volume Size are very close together. Is this correct? Is your Windows partition (sda4) only 12870 MB in the first place? I can imagine this being a problem. Wonder that shrinking it does even work!??!
Edit: Possibly the small size is just because there was another issue initially that prevented FOG from expanding the partition after capture and now you are kind of stuck with the small partition. Please boot up Windows 10 and try to expand that partition to it’s full size. Then try capture again.
Well… That is the size. I did a basic Windows installation as a test drive, like I always did. There’s nothing there but windows. The installation creates 4 partitions like it’s shown in the picture bellow. It captures the first 3 partitions without a problem and then shows the error after capturing the 4th partition.
-
UPDATE:
Well, I changed the Image Type from Single Disk (Resizable) to Multiple Partition Image - Single Disk (Not Resizable) and got a different error as shown in the picture.
I’m starting to think that there’s something wrong with the Windows Storage Node, with it’s configuration or something. I’ve tried to follow these tutorials but they are missing a lot of information… they’re just awful. Specially the one in the wiki.https://wiki.fogproject.org/wiki/index.php/Windows_Storage_Node
https://forums.fogproject.org/topic/10097/setting-up-a-windows-2012-server-as-a-fog-storage-node -
@luis-acacio said in Filesystem check error after capturing W10 image.:
I’ve tried to follow these tutorials but they are missing a lot of information… they’re just awful. Specially the one in the wiki.
I feel as if I may need to clarify something for you. I understand you may be frustrated, but the FOG Project is an open source solution that is not only free and designed/maintained completely by a small group of very intelligent volunteers, but also has top notch support on these forums that rivals paid support contracts.
Admittedly, the wiki is outdated. This is because these few developers are working on continuously improving fog and running a full fledged helpdesk for free, so it is understandable that the knowledge base takes the back burner. I assure you that every issue I have ever posted about in these forums was solved in an appropriate time-frame.
I don’t speak for the project and the only way I am involved in it is solely as a user, but I hope you now have some insight into the reasons behind the shortcomings of the wiki and I hope your issue is resolved soon and to your liking.
