May 17, 2011 at 3:04 pm
Hi Folks,
We have been recieving the error below in one of our server during restoring a database. Has anyone experienced the same problem? If yes can you please share how you fixed it?
The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x000001f3400000 in file 'H:\Data\XXXX_data.mdf:MSSQL_DBCC17'. 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.
May 17, 2011 at 3:09 pm
restore or recovery?
yes. This is a severe HW error likely only fixable by restore. EOF is not where SQL expects it to be.
In our case it was caused by a disk defrag tool (diskeeper) truncating the file. Do you use diskkeeper?
either way get the drive checked out.
---------------------------------------------------------------------
May 18, 2011 at 3:15 am
This was removed by the editor as SPAM
May 18, 2011 at 3:20 am
prettsons (5/18/2011)
Check this article it will help you to resolve this error: http://ezinearticles.com/?Assertion-Or-MDF-Corruption-When-You-Import-Data-in-SQL---Server-2000&id=2228557
Advertising disguised as a technical article. Completely irrelevant here. Full of errors.
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
May 18, 2011 at 3:31 am
ananthtecho (5/17/2011)
We have been recieving the error below in one of our server during restoring a database. Has anyone experienced the same problem? If yes can you please share how you fixed it?
During restore? Or during CheckDB? I ask because the filename refers to the hidden snapshot that CheckDB uses.
Are you running DiskKeeper on that server?
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 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply