Typically when I see data_out_start errors I find a miss match setting from the initiator side in comparison with the iSCSI daemon settings on our side, this is where you made the modifications.
But in the case of a VM environment I found this link below that talks about this error and why it happens. See if this will help and it does not matter if you are using our Volume Replication or not that causes the errors.
They state that it can be caused by the guest Linux kernel and to change the kernel or at least patch its mptscsih driver module.
So what you see on the target side is the errors you have disclosed.
From what they state, it is not a problem "per se, just the target logging warnings about
unexpected actions received from the initiator...
Reply With Quote