Error: fcb::close-flush: Operating system error 21(The device is not ready.) encountered

We are using sql server 2005 Enterprise Edition with service pack1

I got the following error messages in the SQL log

The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000000090000 in file '....mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. fcb::close-flush: Operating system error 21(The device is not ready.) encountered.

I got these errors for about 2 hrs and after that I see these messages in the sql log

Starting up database ' ' 1 transactions rolled forward in database '' (). This is an informational message only. No user action is required. 0 transactions rolled back in database ' ' (). This is an informational message only. No user action is required. Recovery is writing a checkpoint in database ' ' ( ). This is an informational message only. No user action is required. CHECKDB for database '' finished without errors on (local time). This is an informational message only; no user action is required.

Can anyone please help me in troubleshooting this issue. Why this migh have happened.

any help would be appreciated.

Thanks

This sounds like an IO subsystem issue, i.e. SQL Server is having difficulty talking to one of your drives. Are you using direct attached storage or a SAN?|||

Thanks for the reply. We have Netapp SCSI disk storage. Could you please tell me how do I troubleshoot this so that I wont get such errors in future.

Thanks

|||Based on this and what you describe in your other post, you really ought to give Microsoft PSS a call.|||

Do read this kb before contacting PSS. You might be running on an unsupported device.

http://support.microsoft.com/kb/304261

Error: 66030

Hi,
On one of our SQL 2000 cluster servers we have been
getting a lot of error messages in our SQL Server log ile.
Error: 66030, Severity: 15, State: 1
Occasionally it also reports
Error: 66040, Severity: 15, State: 1.
I have been unable to find any information on these error
messages. I would be grateful if someone could shed some
light on what these messages actually mean. Thanks.The fact that the error number is > 50000 suggests that this actually an
application specific error message rather than a generic SQL message. Have a
look in master..sysmessages to see the text of the message, it might give
you a clue
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"PaulaC" <anonymous@.discussions.microsoft.com> wrote in message
news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
> Hi,
> On one of our SQL 2000 cluster servers we have been
> getting a lot of error messages in our SQL Server log ile.
> Error: 66030, Severity: 15, State: 1
> Occasionally it also reports
> Error: 66040, Severity: 15, State: 1.
> I have been unable to find any information on these error
> messages. I would be grateful if someone could shed some
> light on what these messages actually mean. Thanks.
>|||Thanks for the suggestion. Unfortunately, I cannot find
anything like my error messages in sysmessages.
Paula.
>--Original Message--
>The fact that the error number is > 50000 suggests that
this actually an
>application specific error message rather than a generic
SQL message. Have a
>look in master..sysmessages to see the text of the
message, it might give
>you a clue
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"PaulaC" <anonymous@.discussions.microsoft.com> wrote in
message
>news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
>> Hi,
>> On one of our SQL 2000 cluster servers we have been
>> getting a lot of error messages in our SQL Server log
ile.
>> Error: 66030, Severity: 15, State: 1
>> Occasionally it also reports
>> Error: 66040, Severity: 15, State: 1.
>> I have been unable to find any information on these
error
>> messages. I would be grateful if someone could shed
some
>> light on what these messages actually mean. Thanks.
>
>.
>sql

Error: 66030

Hi,
On one of our SQL 2000 cluster servers we have been
getting a lot of error messages in our SQL Server log ile.
Error: 66030, Severity: 15, State: 1
Occasionally it also reports
Error: 66040, Severity: 15, State: 1.
I have been unable to find any information on these error
messages. I would be grateful if someone could shed some
light on what these messages actually mean. Thanks.The fact that the error number is > 50000 suggests that this actually an
application specific error message rather than a generic SQL message. Have a
look in master..sysmessages to see the text of the message, it might give
you a clue
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"PaulaC" <anonymous@.discussions.microsoft.com> wrote in message
news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
> Hi,
> On one of our SQL 2000 cluster servers we have been
> getting a lot of error messages in our SQL Server log ile.
> Error: 66030, Severity: 15, State: 1
> Occasionally it also reports
> Error: 66040, Severity: 15, State: 1.
> I have been unable to find any information on these error
> messages. I would be grateful if someone could shed some
> light on what these messages actually mean. Thanks.
>|||Thanks for the suggestion. Unfortunately, I cannot find
anything like my error messages in sysmessages.
Paula.

>--Original Message--
>The fact that the error number is > 50000 suggests that
this actually an
>application specific error message rather than a generic
SQL message. Have a
>look in master..sysmessages to see the text of the
message, it might give
>you a clue
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"PaulaC" <anonymous@.discussions.microsoft.com> wrote in
message
>news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
ile.[vbcol=seagreen]
error[vbcol=seagreen]
some[vbcol=seagreen]
>
>.
>

Error: 66030

Hi,
On one of our SQL 2000 cluster servers we have been
getting a lot of error messages in our SQL Server log ile.
Error: 66030, Severity: 15, State: 1
Occasionally it also reports
Error: 66040, Severity: 15, State: 1.
I have been unable to find any information on these error
messages. I would be grateful if someone could shed some
light on what these messages actually mean. Thanks.
The fact that the error number is > 50000 suggests that this actually an
application specific error message rather than a generic SQL message. Have a
look in master..sysmessages to see the text of the message, it might give
you a clue
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"PaulaC" <anonymous@.discussions.microsoft.com> wrote in message
news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
> Hi,
> On one of our SQL 2000 cluster servers we have been
> getting a lot of error messages in our SQL Server log ile.
> Error: 66030, Severity: 15, State: 1
> Occasionally it also reports
> Error: 66040, Severity: 15, State: 1.
> I have been unable to find any information on these error
> messages. I would be grateful if someone could shed some
> light on what these messages actually mean. Thanks.
>
|||Thanks for the suggestion. Unfortunately, I cannot find
anything like my error messages in sysmessages.
Paula.

>--Original Message--
>The fact that the error number is > 50000 suggests that
this actually an
>application specific error message rather than a generic
SQL message. Have a
>look in master..sysmessages to see the text of the
message, it might give
>you a clue
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"PaulaC" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
ile.[vbcol=seagreen]
error[vbcol=seagreen]
some
>
>.
>

Error: 17805, Severity: 20, State: 3

We are getting the following messages sporadically in the Event Viewer:
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
without AWE enabled; however, we do have the -g256 startup parameter.
Any help would be greatly appreciated,
James
Have a look here:
http://support.microsoft.com/kb/891719
Andrew J. Kelly SQL MVP
"James" <James@.discussions.microsoft.com> wrote in message
news:75855665-46E4-4429-9B11-0B5C92773451@.microsoft.com...
> We are getting the following messages sporadically in the Event Viewer:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available.
> We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
> without AWE enabled; however, we do have the -g256 startup parameter.
> Any help would be greatly appreciated,
> James
|||Refer
http://support.microsoft.com/default...b;en-us;896373
http://support.microsoft.com/kb/891719
Thanks & Rate the Postings.
-Ravi-
"James" wrote:

> We are getting the following messages sporadically in the Event Viewer:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available.
> We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
> without AWE enabled; however, we do have the -g256 startup parameter.
> Any help would be greatly appreciated,
> James

Error: 17805, Severity: 20, State: 3

We are getting the following messages sporadically in the Event Viewer:
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
without AWE enabled; however, we do have the -g256 startup parameter.
Any help would be greatly appreciated,
JamesHave a look here:
http://support.microsoft.com/kb/891719
Andrew J. Kelly SQL MVP
"James" <James@.discussions.microsoft.com> wrote in message
news:75855665-46E4-4429-9B11-0B5C92773451@.microsoft.com...
> We are getting the following messages sporadically in the Event Viewer:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available.
> We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
> without AWE enabled; however, we do have the -g256 startup parameter.
> Any help would be greatly appreciated,
> James|||Refer
http://support.microsoft.com/defaul...kb;en-us;896373
http://support.microsoft.com/kb/891719
Thanks & Rate the Postings.
-Ravi-
"James" wrote:

> We are getting the following messages sporadically in the Event Viewer:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available.
> We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
> without AWE enabled; however, we do have the -g256 startup parameter.
> Any help would be greatly appreciated,
> James

Error: 17805, Severity: 20, State: 3

We are getting the following messages sporadically in the Event Viewer:
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
without AWE enabled; however, we do have the -g256 startup parameter.
Any help would be greatly appreciated,
JamesHave a look here:
http://support.microsoft.com/kb/891719
Andrew J. Kelly SQL MVP
"James" <James@.discussions.microsoft.com> wrote in message
news:75855665-46E4-4429-9B11-0B5C92773451@.microsoft.com...
> We are getting the following messages sporadically in the Event Viewer:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available.
> We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
> without AWE enabled; however, we do have the -g256 startup parameter.
> Any help would be greatly appreciated,
> James|||Refer
http://support.microsoft.com/default.aspx?scid=kb;en-us;896373
http://support.microsoft.com/kb/891719
--
Thanks & Rate the Postings.
-Ravi-
"James" wrote:
> We are getting the following messages sporadically in the Event Viewer:
> Error: 17805, Severity: 20, State: 3
> Invalid buffer received from client.
> Error: 17803, Severity: 20, State: 12
> Insufficient memory available.
> We are running SQL Server 2000 SP4 on Windows Server 2003 SP1 with 4Gb RAM
> without AWE enabled; however, we do have the -g256 startup parameter.
> Any help would be greatly appreciated,
> James