April 19, 2011 at 8:50 pm
I got a series alert about one of our sql servers:
DESCRIPTION:The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x000000095ba000 in file 'f:\mssql\data\mydbname.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.
What does this mean, how to fix it?
Thanks
April 19, 2011 at 9:19 pm
SQLMyFriend (4/19/2011)
I got a series alert about one of our sql servers:DESCRIPTION:The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x000000095ba000 in file 'f:\mssql\data\mydbname.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.
What does this mean, how to fix it?
Thanks
Sounds like you are having problems with the IO subsystem. I would validate that is online and functioning appropriately as well as starting to look in the other logs; SQL Server and Windows logs. Hopefully you can find more details there. It would also be good to run the DBCC check as stated.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
April 19, 2011 at 11:00 pm
We found out there are san and switch issues with our network.
April 19, 2011 at 11:21 pm
Once those have been fixed, run a checkDB and post any results.
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
April 20, 2011 at 12:27 am
After network guys fix switch, I did a dbcc checkdb like above.
it returns Command(s) completed successfully.
I guess the file is OK.
Thanks
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply