I have once seen this behaviour when a transaction log has filled the hard disk on which the SQL databases are stored.. could this be the case here?