Microsoft iSCSI Initiator & SQL Server services

Hello all,
I have Microsoft iSCSI Initiator (SAN) installed on a SQL Server machine and has this drive acting as a local drive. All the database's data files are residing on this drive, attached with SAN.
It runs as a service "Microsoft iSCSI Initiator" on the SQL Server machine.

Now the question is, when we restart the SQL Server all the databases change their status to "Suspect" and we have to stop all the sqlserver services (all the SQL instances) and start them all up. This is the only temporary solution we came up with.
Could any one has any real solution or had encounter such a problem before?

Any help is appreciated.

Thanks bunch!
imransi.Looks like your SQL Service starts before your SAN is available.|||Originally posted by rdjabarov
Looks like your SQL Service starts before your SAN is available.

You are 100% right. So thats why we are restarting SQL services.
We can manually start sql services but thats not what we wnat and really thsi should not be the solutuion ;)|||See if you can "impose" a dependency on MSSQLSERVER service in regards to this SAN service.