Error: 823, Severity: 24, State: 2

• sqlquery-101401

  SSCarpal Tunnel

  Points: 4951

  More actions

  September 14, 2004 at 4:51 am

  #89359

  hi all

  while accessing my database in EM i am getting error in all user databases (not in system DB)even i am not able to run dbcc checkdb (it is running and running for userdb's)

   in the application log file on the server.

  Error: 823, Severity: 24, State: 2

  I/O error 1117(The request could not be performed because of an I/O device error.) detected during read at offset 0x000001a14ba000 in file 'I:\msSQL\DATA\Trans_data1.ndf'.              

  if i try to look the property of any db it throws error of database mdf

  I/O error 1117(The request could not be performed because of an I/O device error.) detected during read at offset 0x000001a14ba000 in file 'I:\msSQL\DATA\Trans_data1.mdf'

  is it related to H/W  but i am able to access that drive on which these DB's resides.

  i checked the space also but that is also not an issue .

  Please suggest.

• Alok thanvi

  SSC Enthusiast

  Points: 161

  More actions

  September 14, 2004 at 11:13 pm

  #523098

  Hi,

  This is the clear problem of I/O Hardware. I have the same problem with one of my production server from past few months. You could try to run the DBCC CHECKDB with physical_only option to confirm the scale of damage to your user database.

  Only way to come out to the situation is either restore the database from the fresh good backup or run the DBCC CHECKDB with repair_allow_data_loss option. But be sure that by using this command will cost you un-identified data loss, you could not figure out how much and which  data you loose.

  If you could manage to find some downtime, you can run the IO stess utility which will report any potential/existing hardware problem to you.

  Keep the post updated cause I am also working towards the solution of the same problem and your feedback would add some value to me also.

   

• Richard L. Dawson

  Ten Centuries

  Points: 1062

  More actions

  September 15, 2004 at 6:15 am

  #523132

  Hi,

      Alok is correct. This is a sign of hardware problems. Before you try to restore your databases you REALLY should get some technical help for the hardware. Sql Server does not perform direct writes or reads of the hardware. It relies on API calls to the OS for this. Additionally, it is not designed to work correctly when there is a problem with the hardware or corruption in the databases. If you have a vendor agreement for the drives your user databases are on you should engage them.

   

  Many times vendors will perform some diagnostics on a system and tell you that there is nothing wrong with the hardware. Running SqlIOStress after they have told you this will sometimes point out issues that they did not test for. Once the hardware is stable you can restore your backups. If you do not have backups you should call in to the Microsoft Support line for assistance in recovering what you can from the databases.

   

  Here is a link to the article that discusses SqlIOStress and how to use it.

  231619 How to use the SQLIOStress utility to stress a disk subsystem....

  http://support.microsoft.com/?id=231619

   

   

  HTH

  Richard L. Dawson
  Microsoft Sql Server DBA/Data Architect

  I can like a person. People are arrogant, ignorant, idiotic, irritating and mostly just plain annoying.