I thought that the trace flag was for SQL to the netapp via cifs, not iscsi.

The dependency thing is the fix for the boot-up suspect db problem.  Makes sense, if iSCSI isn't up and started when SQL Server starts, the db's won't be there!  So you must create a dependency.  Would be nice for the iSCSI initiator install program to ask if you're using SQL  or Exchange over iSCSI and do it all for you.

To the person saying that if you want your job, etc., time to freshen up on your infrastructure knowledge and experience.  I've put in dozens of Exchange/SQL over iSCSI now, even with clustering, and if something goes wrong it's almost always a config or design error, not the technology. 

Cheers,

Glenn