January 25, 2012 at 7:19 pm
I encountered the following DB tables inconsistency error whenever I do a cluster 'move' over from Server-A to Server-B and then do a DBCC CHECKDB on the database in Server-B:
SQL Server detected a logical consistency-based I/O error:incorrect checksum. It occurs during read of page(1:142) in dtabase ID 4 at offset 0x0000000011c))) in file 'X:\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\MSDB.mdf.
Sometimes, the above DB error may vary and occurred to other DB tables 🙁
The two servers (A & B) are using Window Server 2008 R2 Enterprise Edition (SP1). Each server has its own NAS (SUN Storage 7410), and using Double-Take Availability to create a single copy of the database across the servers. Also, each server has 2 iSCSI connectors (redundancy purpose) connected to the NAS.
The peculiar thing is the DB inconsistency error did NOT happen when I change either one of the following configuration:
1. Move from Server-B to Server-A (no DB error on Server-A using DBCC)
2. Software disable one of the 2 iSCSI connectors on Server-B
3. Use internal local harddisk, instead of NAS in Server-B (Server-A still using NAS)
Could it because the hardware I/O error on the NAS?
Anyone can help to advise me what else can I do to diagnose the problem to Server-B.
Thank you!!
January 26, 2012 at 4:25 am
hwat were the results of your cluster verification report when you first deployed the windows cluster. try running it again to see if it pinpoints any issues
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 26, 2012 at 9:01 pm
Hi Perry,
The validation test passed successfully during the initial setup. After the problem occurred weeks back, we run the validation test again and encounter the this error
List Cluster Volumes
An error occurred while executing the test.
The given key was not present in the directory.
Regards,
Ken
January 27, 2012 at 12:05 am
Hi
With the local hard disk, we also encounter the same List Volume error in Cluster validation.
Regards,
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply