An error occurred during the Detach database today. Run dbcc checkdb to view the following information from the SQL Server error log:
Error: 17053, Severity: 16, State: 1.
LogWriter: Operating system error 21 (The device is not ready.) encountered.
Write error during log flush.
Error: 9001, Severity: 21, State: 4.
The log for database ''is not available. Check the event log for related error messages. Resolve any errors and restartthe database.
Error: 823, Severity: 24, State: 2.
The operating system returned error 21 (The device is not ready .) to SQLServer during a read at offset 0x000000000de000 in file 'xx. mdf '. additional messages in the SQL Server error log and system eventlog may provide more detail. this is a severe system-level error condition thatthreatens database integrity and must be corrected immediately. complete a fulldatabase consistency check (dbcc checkdb ). this error can be caused by manyfactors; for more information, see SQL Server Books Online.
According to error 21, this should be a disk problem, but many other databases on the disk can work normally, and there is no problem with the newly created files.
Then we can see the 823 error, which should be caused by a hardware error. Microsoft recommends running dbcc checkdb. But it cannot run at all.
The following error is still reported when you try to run dbcc checkdb with tablock.
Then I tried to restart the service and the database was ready. No error was found when running dbcc checkdb.
It seems that this problem is a monster. If there is no problem with hardware disks, a disk error is reported.
This article is from the "follow SQL Server Technology" blog, please be sure to keep this source http://lzf328.blog.51cto.com/1196996/1294871