Win2k3 SBS Catalog corruption causing server to hang...

Tom · Guest

Windows 2003 SBS SP2
RAID 1 configuration
Exchange 2003 SP3
3GB RAM
250 GB Sata drive (C @ 40GB; D is DVD drive, E @ 200GB)
Server is also FTP server
Only one server in domain

After running the above configuration fine for a number of months, we're
receiving a message during the Indexing Service processing (CISVC.EXE) that
"Windows was unable to save all the data for the file E:\System Volume
Information\catalog.wci\00010008.ci. The data has been lost. This error may
be caused by a failure of your computer hardware or network connection.
Please try to save the file elsewher" (last 'e' is not displayed or dropped).
We've done a complete physical verify of the SATA drives with absolutely no
errors showing. Whenever the Win2K3 Indexing Service is stopped/disabled we
can run fine. We can also run fine in Win2K3 Safe Mode with or without
Networking. When we start the Indexing Service, within 3-5 minutes the
system hangs forcing hard reboot (turn off/unplug) and restart. We generally
can see a message similar to the one above.
Our first approach was to rename the Catalog.wci file off of C:\inetpub\ but
we got the same result. [This info came from the MS website]. However, our
FTP server points to E:\inetpub\ though.
Hence we're able to keep the server UP when NOT running the Indexing
Service. Now, however, when we saved a PDF file to drive E we hung the
system. The PDF was downloaded from a website and then subsequently saved to
drive E:. We then rebooted and went to the same website and downloaded
another PDF. THis time we saved it to drive H (USB external drive) and we're
still running fine on the Win2K3. Hence, the issue is Indexing Service
and/or the physical RAID drives and maybe drive C and/or drive E as these are
logical drives on the physical 250GB RAID 1 configuration.
Does any one have any ideas of what could be the issue? IIS?
How can we fix it....?
We've spent about 16+hours on just isolating the Indexing Service as the
culprit.
TIA!!!