October 30, 2006 at 3:01 am
I/O error 2(error not found) detected during write at offset 0x000000e99ce000 in file 'D:\database\BillCDR\FLGRP_INDEX\data_flgrp_index.NDF'..
Error: 823, Severity: 24, State: 3
I use MSSQL 2000 SP4 Database size : 80GB
My raid hardisk is crash one of them after that in SQL Server LOG got this error many time.
I/O error 2(error not found) detected during write at offset 0x000000e99ce000 in file 'xxxx.NDF'..
Error: 823, Severity: 24, State: 3
I didn't monitor it ontime just read after my database is suspect (This error occur manytime then it's go suspect status)
I try sp_resetstatus but didn't work cause above error then I decide to restore my backup.
Surely , I change one of fail harddisk at first before restore my backup.
Everything look well I can use my database (select/insert/update) without problem for few hours.
Then I continue got this error again.
I/O error 2(error not found) detected during write at offset 0x000000e99ce000 in file 'xxxx.NDF'..
Error: 823, Severity: 24, State: 3
This error message repeat everysecond and didn't stop. Even I didn't do anything to my database.
I try to backup my database but can't (have error message above too) then I decide to start/stop mssql.
That's work !! no more error event for now, I test backup database it's work.
But I don't sure this will happen again or not ? How I prevent this or fix this problem.
I want to move problem datafile to another drive but I don't know how to do cause I have many datafile.
(I read sp_attach manual it's limit 16 datafiles I have more)
I try to search about this error with myself but still can't find exactly answer.
Many question talk about backup problem (that I didn't do it that time) , disk problem (already fix it).
So I have to start topic with myself.
Sorry if my english is not good.
October 31, 2006 at 8:28 am
Hello!
Did you tried to check your database with DBCC CheckDB? Maybe the problem is still there and is waiting for SQL Server to read a bad sector or something. If you have a RAID array, it is possible that your array is corrupted. Sometimes the IDE/SCSI Controller may have some problems.
Stop SQL Server and run a scandisk or Stress your HDD with a Stress Tool and see if you get some errors.
If that doesn't help, maybe is something wrong with internal SQL Server Engine.
Good luck!
October 31, 2006 at 3:40 pm
maybe you should call ms and hardware vendor..?
October 31, 2006 at 7:02 pm
Thank you, I guess really raid problem that I lost my datafile.
Anyway, now I can restore my database from my backup but it's too old.
I backup all datafile (Except one that have problem can't copy).
I check that datafile, it's just only index not data.
Can I restore all of them by reject that index ?
I try offline database and replace after crash datafile but can't online.
It's error about index datafile not match.
I try again restore full , delete index then replace after crash datafile.
Then I can online, but I can't recreate index, it's still error file id (still point to old one)
even I recreate that problem datafile with old name (and same file_id in sysfiles)
One more thing, how can I re-attach if I have more than 16 datafiles.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply