Thanks to both of you for your help. We seem to have a resolution. Unfortunately, we made two changes so we don't know which one did the trick or if...

The SAS has hardware disk caching. What was your concern?

MSDTC is in its own cluster group. I could live on any of the Nodes at any given time.

That is just one instance of that error though. It also happened...

Back to your Full Text indexing question. This DB does not but the other three (including the one that went and stayed suspect) do.

It is a regular failover cluster, with a quorum drive.

Here are some of the errors found in the cluster.log

thanks

They are the same Drive letter/name on all four nodes. It is all on the drive in the cluster group. So it moves from node to node as the drive...

Thanks for the quick reply.

The log file for the DB which always works (DB1) is on the same drive as the one which doesn't so I would think the drive...