Problem with the resize (expanding) on a hard drive

[loutrage]

@Sebastian-Roth
Here is 2 screens about SDA2. Everything seems good I think.

[Quazz]

@loutrage Looks the resize test fails, which automatically marks the partition as fixed size.

Possibly the filesystem or disk is damaged causing the failure.

Try and fix the filesystem by running chkdsk C: /f on the windows client you want to capture. (you’ll then need to confirm to schedule on reboot and then ofc reboot)

[Sebastian Roth]

@loutrage See it says Not shrinking (/dev/sda2) trying fixed size in the pictures. So there is an issue with trying to shrink that filesystem. I’d suggest you do another debug capture task and step all the way to the point where you see that message. Now press Ctrl+c to stop the script and get back to the shell. Now run cat /tmp/tmpoutput.txt to see all the messages the last command (ntfsresize) produced. Take a picture and post here.

[loutrage]

@Quazz
@Sebastian-Roth

Thank you, you found the solution !

Here is the result of the tmpoutput.txt file

Indeed, the problem came from a problem with the filesystem of my “mother” image. After several chkdsk (I had reboot only once the first time), the expand works well.

Thank you guys ! The problem is so solve now.

[x23piracy]

Hi,

i currently have this Problem with (Windows 10 2004) i created a new image thats not expanding after deployment. I am on an older FOG Version 1.5.0 and older Images (1703) expand correctly.

Any idea?

Best Regards X23

[Quazz]

@x23piracy The newest W10 versions seem to create a partition after the Windows partition. This will be what’s blocking it.

There are some ideas on how to resolve such things in the future, but currently you have to manually move the partition before capture.

[x23piracy]

Hi Quazz,

thanks for your quick response after that deployment i could see the recovery partition is behind the system partition, if move this in front of the system partition and capture after that it works?

Btw. i found out howto still use copyprofile with newer Win10 Versions if someone is interested.

I was looking for my post and wondering with the post number has been extended but my post wasnt visible, forum changes to current post on top hehe

Best Regards X23

[Quazz]

@x23piracy Yes, that should work. Hopefully we have a better solution by 1.6.0

[x23piracy]

Hi,

i am currently trying to move partitions but it won’t let me:
https://i.imgur.com/9pKvxqY.png

The marked part is “move partition” it’s greyed out.

Regards X23

[Quazz]

@x23piracy Not sure what program you are using, but perhaps you need to shrink you windows partition first, move it to the right (into the unallocated space), then move the recovery partition in front of it, reallign and expand again.

[x23piracy]

Hi,

i thought the same but i can’t move the recovery partition in front of the system partition even if i shrink the beginning of the system partition…meh:

https://i.imgur.com/ZRjg6Tm.png

Best Regards X23

[Quazz]

@x23piracy It’s safe to delete if you don’t need that partition.

Alternatively, you could manually create the partitions in windows setup I suppose.

[x23piracy]

Hi,

i am not sure if it can simply deleted, It’s used in recovery cases and there are 12,5MB of data in it. I need to find out if Windows 10 is using it for what ever case.

Best Regards X23