September 17, 2010 at 11:22 am
Hi,
We have 2 node cluster setup on Windows 2003 x64 with SP2 and we are ready to install SQL Server 2005.
Before starting the installation, I have rebooted both the nodes and I noticed the below ntfs error. Is it OK to continue with SQL Server installation? Because ntfs error is not occuring continuously but whenever I reboot the nodes, I'm seeing this error
Event Type:Error
Event Source:Ntfs
Event Category:Disk
Event ID:55
Date:9/14/2010
Time:11:34:43 AM
User:N/A
Computer:SQL1
Description:
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume
Thanks
September 17, 2010 at 11:28 am
I don't think it's a good idea to continue with the installation. It's only an invitation to problems. Please run the CHKDSK utility to possibly fix the problem before you move any further.
Thank You,
Best Regards,
SQLBuddy
December 13, 2012 at 6:55 am
I also posted this question under: Home » SQL Server 2005 » Data Corruption » CHKDSK on a SAN Volume
I know that this topic is a bit old, but I have a very similar question.
Every two weeks we perform server/database maintenance; altering indexes, Windows updates and a server reboot. My issue periodically appears between maintenance weeks with a System error Event ID 55 in the event viewer: "The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume XDATA."
This volume is on our SAN and I've determined that I need to perform a CHKDSK since the volume is marked as dirty.
I understand the differences between CHKDSK /F & CHKDSK /R. My question is since I'm not performing a CHKDSK /R should I be worried about database files on this volume if I perform a CHKDSK /F?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply