SAN Connectivity Issue

I have SQL 2000 SP3a EE on Compaq hardware. I have all user data and system
data on SAN Drives. I am noticing that even though SQL Server is set up as
automatic on start up still it doesn't stat the server automatically. I have
to manually start SQL Server service after the machine is booted up. In the
event log it shows that it had difficulties in finding SAN Drives though the
drives existed. After the boot up, I start SQL Server manually and see no
issues in starting up.
Has anyone sees this kind of issue and if so, what were the steps to resolve
this.
Thank you very much.
Hi
Looks like a Hardware/Driver issue. The fact that SQL Server can not find
the drives means that the OS has not presented them to SQL Server. Probably
it takes a bit long to find them, by then it is SQL Server's turn to be
started up as a service, and since the drives are not online, SQL Server
aborts.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:2A8660A3-6D8A-42E9-B13A-6DB3D38CDAB6@.microsoft.com...
> I have SQL 2000 SP3a EE on Compaq hardware. I have all user data and
system
> data on SAN Drives. I am noticing that even though SQL Server is set up as
> automatic on start up still it doesn't stat the server automatically. I
have
> to manually start SQL Server service after the machine is booted up. In
the
> event log it shows that it had difficulties in finding SAN Drives though
the
> drives existed. After the boot up, I start SQL Server manually and see no
> issues in starting up.
> Has anyone sees this kind of issue and if so, what were the steps to
resolve
> this.
> Thank you very much.
|||Hi Mike:
I don't think that it is a driver issue. If drivers are bad then drives
shouldn't come back at all. The fact is drives do come back after OS is fully
started and then when I start SQL Server manually, it works fine. I agree
that something is wrong with the Drives to be shown up during OS and since
drives are not present, SQL doesn't start. Problem is drives do come when I
look for them after OS is fully started so I am unsure as to what part of
software needs to be fixed.
-Mark
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> Looks like a Hardware/Driver issue. The fact that SQL Server can not find
> the drives means that the OS has not presented them to SQL Server. Probably
> it takes a bit long to find them, by then it is SQL Server's turn to be
> started up as a service, and since the drives are not online, SQL Server
> aborts.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:2A8660A3-6D8A-42E9-B13A-6DB3D38CDAB6@.microsoft.com...
> system
> have
> the
> the
> resolve
>
>
|||Hi
It is not SQL Server. Next time, do not log onto the box, but start the
services manually though services applet on another computer (right click on
the local service and select connect to another computer...). If it fails,
then there is some dependency on you having to log in to get the drive to be
available.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Mark" <Mark@.discussions.microsoft.com> wrote in message
news:DE24AD09-360F-418B-9C70-22F8968B89F0@.microsoft.com...
> Hi Mike:
> I don't think that it is a driver issue. If drivers are bad then drives
> shouldn't come back at all. The fact is drives do come back after OS is
fully
> started and then when I start SQL Server manually, it works fine. I agree
> that something is wrong with the Drives to be shown up during OS and since
> drives are not present, SQL doesn't start. Problem is drives do come when
I[vbcol=seagreen]
> look for them after OS is fully started so I am unsure as to what part of
> software needs to be fixed.
> -Mark
> "Mike Epprecht (SQL MVP)" wrote:
find[vbcol=seagreen]
Probably[vbcol=seagreen]
up as[vbcol=seagreen]
I[vbcol=seagreen]
In[vbcol=seagreen]
though[vbcol=seagreen]
no[vbcol=seagreen]
|||Go to Administrative Tools/Services and setup automatic recovery for
MSSQLSERVER. Set it to restart after the first failure. Have it wait for 1
minute. See if that temporarily fixes the issue while you get the SAN issue
fixed. What type of SAN and fiber cards are you using? What version of
drivers do you have for the fiber cards?
You have any errors in the system event log?
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:#RAM657MFHA.4028@.tk2msftngp13.phx.gbl...
> Hi
> It is not SQL Server. Next time, do not log onto the box, but start the
> services manually though services applet on another computer (right click
on
> the local service and select connect to another computer...). If it fails,
> then there is some dependency on you having to log in to get the drive to
be[vbcol=seagreen]
> available.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Mark" <Mark@.discussions.microsoft.com> wrote in message
> news:DE24AD09-360F-418B-9C70-22F8968B89F0@.microsoft.com...
> fully
agree[vbcol=seagreen]
since[vbcol=seagreen]
when[vbcol=seagreen]
> I
of[vbcol=seagreen]
> find
> Probably
be[vbcol=seagreen]
Server[vbcol=seagreen]
> up as
automatically.[vbcol=seagreen]
> I
> In
> though
see
> no
>