mismatched drive sizes in win10 after incomplete capture with 1.5.5

[geardog]

So using 1.5.5 I tried to capture a win10 box. It failed at 85% (as shown by the bar in fog’s “active tasks”), but rebooted to windows. Fine, but the windows machine still has a minimized OS/system partition.

incongruencies-
Win10 drive list shows OS partition as 60GB and throws errors as it being full.
Admin tools>comp management>storage>disk management- shows the partition as the expected ~180GB size

Any advice on how to un-hose this drive without borking it further? Hopefully someone better versed in this kind of thing might understand the discrepancy.

I have updated to fog 1.5.6, but still hope to salvage the workstation.

[geardog]

@Sebastian-Roth
Gparted fixed it with the “check” command, running what appeared to be the same commands I entered at terminal.

I’ll try to capture it again after I’m more confident the box is ok.

thanks guys

[Sebastian Roth]

@geardog There are two things, partition size and the size of the actual filesystem within that partition. Seems like it resized the partition back to it’s original size but not the filesystem.

Can you please post a picture of the disk management view in Windows. Just to make süße my guess is right.

[geardog]

@Sebastian-Roth

I obscured it, but, in file explorer, the 59.8GB is total size.

[Sebastian Roth]

@geardog Please schedule a debug capture task on this host, boot it up and when you get to the shell run:

ntfsresize --no-action --expand --verbose /dev/sda2

Note that I am guessing the partition letter sda2 here. Might be different on your system. If you are not sure take a look at the partitions using parted -l /dev/sda first.

If the above command does not throw an error you might run it again but this time leave out the --no-action command line parameter and it should do its job.

[geardog]

@Sebastian-Roth

The sector and cluster ratios seem appropriate for the partition size. Will the error cause issue?

Any guidance is appreciated. I can google some commands and pretend I know what I’m doing, but I’d rather not botch the box further.

[Sebastian Roth]

@geardog Try the following: ntfsfix /dev/sda2

[geardog]

@Sebastian-Roth
ntfsfix processed, but the FS is still the same size. I guess now I try the previous command again to see if the bootsector error has been cleared to run the resize?

[Sebastian Roth]

@geardog said:

I guess now I try the previous command again to see if the bootsector error has been cleared to run the resize?

Exactly. Give it a try. Please take a picture again and post here.

[geardog]

@Sebastian-Roth

no apparent change

[Sebastian Roth]

@geardog Do you have a complete sector by sector image backup of the disk? If not I’d suggest taking one and then just go ahead and try: ntfsresize --expand --verbose --force /dev/sda2

[geardog]

@Sebastian-Roth

note: -v gave no further info

What now?

[Sebastian Roth]

@Tom-Elliott Do you have an idea?

[Tom Elliott]

@Sebastian-Roth No ideas really.

However, the fact that it’s referencing the “boot” sector as the issue, I’m guessing the Partition table is configured in GPT? Does it look similar to the other GPT threads where the last partition in the disk is also the boot partition?

[geardog]

@Tom-Elliott
I double checked. It is MBR and system is on the small 500MB partition.

[Sebastian Roth]

@geardog It’s not easy to give instructions as we don’t have your setup at hand to play with it ourselves. Anyhow as a next step I would try booting a gparted live boot CD and see what it looks like in there. Either it is able to expand the NTFS filesystem to the full size or you can try to first shrink it down to 60 GB and then expand again.

[geardog]

@Sebastian-Roth
Gparted fixed it with the “check” command, running what appeared to be the same commands I entered at terminal.

I’ll try to capture it again after I’m more confident the box is ok.

thanks guys