mismatched drive sizes in win10 after incomplete capture with 1.5.5

[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