I've seen it before where the drive reports the wrong size for the track and so it runs out of data to compare to the image file and just sits there.

It was a condition I'd not really planned for (as I've never run into it before now!).

Needless to say it has already been sorted for the next version.