你重新恢复了MASTER库么？我估计是MASTER有问题，你试试恢复看看！ 还有你可以试试重新安装SQL SERVER SP2.在SQL 查询分析器运行 DBCC CHECKDB （检查指定数据库中的所有对象的分配和结构完整性。）
BELOW MESSAGE FROM MSDN GOOD LUCK!Error 823 Severity Level 24 Message Text I/O error %ls detected during %S_MSG at offset %#016I64x in file '%ls'.Explanation Microsoft® SQL Server™ encountered an I/O error on a read or write request made to a device. This error usually indicates disk problems. However, additional kernel messages in the error log, recorded before error 823, should indicate which device is involved.Action Check the accessibility and condition of the device in question.Run hardware diagnostics and correct problems, if possible.Restore damaged files from the latest database backup. Restoring from a database backup should always be considered the primary means of fixing a damaged database. If you don't have a backup or if the errors detected are very isolated, the repair functionality of DBCC CHECKDB may be useful. However, using DBCC CHECKDB can be more time consuming than restoring the damaged files from a backup, and you may not be able to recover all your data .Caution If running DBCC CHECKDB with one of the repair clauses does not correct the problem or if you are unsure how this process may affect your data, contact your primary support provider
你最近有没有装什么软件？
还有你可以试试重新安装SQL SERVER SP2.在SQL 查询分析器运行
DBCC CHECKDB
（检查指定数据库中的所有对象的分配和结构完整性。）
GOOD LUCK!Error 823
Severity Level 24
Message Text
I/O error %ls detected during %S_MSG at offset %#016I64x in file '%ls'.Explanation
Microsoft® SQL Server™ encountered an I/O error on a read or write request made to a device. This error usually indicates disk problems. However, additional kernel messages in the error log, recorded before error 823, should indicate which device is involved.Action
Check the accessibility and condition of the device in question.Run hardware diagnostics and correct problems, if possible.Restore damaged files from the latest database backup. Restoring from a database backup should always be considered the primary means of fixing a damaged database. If you don't have a backup or if the errors detected are very isolated, the repair functionality of DBCC CHECKDB may be useful. However, using DBCC CHECKDB can be more time consuming than restoring the damaged files from a backup, and you may not be able to recover all your data .Caution If running DBCC CHECKDB with one of the repair clauses does not correct the problem or if you are unsure how this process may affect your data, contact your primary support provider