Ah. This looks like it is not caused by a routing issue. Do you have a policy from untrust to dmz that references the VIP?
[ Dest] 95.route 1.1.1.2->2.2.2.1, to ethernet0/0
self check, not for us
The above indicates it has found route ID 95, but the packet is not matching the VIP. This could be due to the VIP not being configured correctly.