Hi Plamen, thanks for your post.
I am using 5.5.3 by the way, so, I am in a good shape with that.
I found that the problem was with LVM in destination. When it start to try creating LVM group in destination, it gets that error showed before.
The strange is, that same LVM set exists on source (physical) , so, there is no misconfiguration. I guess the problem is with Converter trying to set same LVM configuration on destination including that big partition (3TB). If I remove that partition, it works...but it will input me a effort to create it manually later. So, the solution was create the same LVM set but put the big partition (3TB) as a single disk, not include it in LVM. After that, no space error happened.
In my case there is no difference, but, have you ever seen this before?? If a replica of LVM was necessary on destination, that would be a problem.
The job did not finish yet, it has at least more 12 hours to complete. I will update the status to check if everything worked fine when it get done.
Regards.