MD3000i Second Enclosure - No Path Redundancy?

I have an md3000i connected to a second md1000 chassis with two cables in a redundant fashion as shown in the admin guide. one cable from the md3000i controller 0 out port to the in port of controller 0 on the md1000 and same for controller 1 on the md3000i and md1000.

The recovery guru states 'virtual disk not on preferred path' with two volumes created. One on the md3000i and one on the md1000. Yet i re-created the volumes and let the array set them automatically.  I can manually move the referenced volume to the preferred path and the error goes away, but why would that not have been the preferred path to begin with? It makes sense that each new volume path is assigned to the opposite controller for successful load balancing. This brings me to my second issue which seems related.

The recovery guru is showing the following error: Physical path loss of redundancy. Its stating disk 14 on expansion enclosure 1.

Status is optimal,

component requiring service: 14

service action required (removal) allowed: No X

working channel: -1

The disk is not flashing orange as if it was bad, and there were no predictive failure reports through openmanage on this disk when the array was directly attached to a host yesterday where it lived for the past six months. So Im confused. Is it trying to tell me the drive is bad, or is is trying to say there is something wrong with the configuration for multi-path redundancy between array controllers due to a cable or configuration issue? If its a config issue in the cables or something, is that i have two cables connected between both chassis and i should have only one?

Thanks