September 29, 2002 at 3:26 pm
I've been getting this error on one of the databases on the server. I've tried to track down info about it, but I can't seem to find out what it is or what's causing it (or how to fix it). Does anyone have any knowledge of this?
Error: 823, Severity: 24, State: 1
I/O error 38(Reached end of file.) detected during read of BUF pointer = 0x142cf0c0, page ptr = 0x1a2b6000, pageid = (0x1:0x805b9), dbid = 17, status = 0x801, file = e:\MSSQL\data\RNPartners_Data.MDF.
September 29, 2002 at 4:03 pm
The following applies to tempdb only:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q313702
Have you tried dbcc checkdb?
Andy
September 29, 2002 at 5:32 pm
Well, I hadn't tried checkdb, so I gave that a try. Nothing worked accept repair_allow_data_loss, which scares me to hell. Is there any way to find out what happened? Anyway, it seemed to work - thanks.
Oblio
September 29, 2002 at 5:58 pm
Unfortunately there is no way to find the exact cause unless you were looking at the time it occurred. Could have been anyone of a number of factors. One thing thou, I would run a chkdisk to verify if there are any bad sectors on the machine which can be one of the major potential causes.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
September 29, 2002 at 8:12 pm
Yeah, I already did that, and it turned up nothing.
March 24, 2010 at 9:10 am
I have received this error twice in the last couple months. I also could never track down a root cause. The only thing I noticed is my server guys have installed a product called "disk keeper" which is supposed to be able to do ONLINE defrags of SAN disks in relation to Sql Server. They are big on saying that it's aware and works well with SQL Server but I have only started getting these errors after they installed. Anybody else happen to have any type of Disk Management or Defrag tool on their server. Just looking for a common connection.
My Error:
The Operation System Returned Error 38(Reached the endof the file) to the SQL Server druing a read at offset ............
March 24, 2010 at 9:22 am
Diskeeper may well be the cause of the problem.
http://sqlblog.com/blogs/jonathan_kehayias/archive/2009/12/29/diskeeper-2010-update.aspx
p.s. Please in future post new questions in a new thread rather than resurrecting an 8 year old thread.
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
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply