So Disk 4 is 2.0 GiB in size, this should mean that it *somehow* flies below the radar
of the Registry settings for alignment.
Check them, but they should be:http://reboot.pro/to...o-gpt/?p=186428
In theory, that MSR partition should have been aligned to 128 LBA or 65536 bytes.
The first partition is not aligned to the "old" standard (Cylinder/head), nor to the "new" one (multiple of 4096 bytes) and simply goes "as soon as it will fit", i.e. right after the 33 sectors *needed* for the GPT disk structure.
It is possible that for one of the usual reasons (mainly stupidity, laziness or sloppiness) the good MS guys that made the convert program didn't think to check the Registry.
And - seemingly - this non-alignment creates also the second partition not aligned, 67584*512=34603008 which is not any "normal" value.
However using the noerr paramter is not exactly smart, maybe if you try without it the tool will provide some feedback.
The fact that gdisk found an error in the MBR protective partition entry size might mean that there were actually some errors in the conversion.
BTW and JFYI the "16F1AC60-F15B-4EE0-8DF3-D274B6DD807D" is the DISK
GUID, it is not the volume/partition GUID, which is represented in gdisk as 0C01 (abbreviated) which is actually MSR or "E3C9E316-0B5C-4DB8-817D-F92DF00215AE". (I wanted to be sure it was actually a MSR as "Reserviert" might have been *any* "reserved" type, even if likely the good MS guys only consider "their own" ID to be actually "reserved" it is always better to make sure).