An error occurred while Detach database was running today, DBCC CHECKDB saw 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, there should be a disk problem, but this disk has a lot of other databases on it that will work, and the newly created files will be fine.
Then I saw the error of 823, which should be caused by a hardware error. Microsoft’s recommendation is to run DBCC CHECKDB. But it doesn’t work at all.
Trying to run DBCC CHECKDB WITH TABLOCK still reports an error.
Then I tried to restart the service once, and the database worked. Running DBCC CHECKDB found no errors.
Feel this problem is very bogey, in the hardware disk is no problem even reported disk error.
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, there should be a disk problem, but this disk has a lot of other databases on it that will work, and the newly created files will be fine.
Then I saw the error of 823, which should be caused by a hardware error. Microsoft’s recommendation is to run DBCC CHECKDB. But it doesn’t work at all.
Trying to run DBCC CHECKDB WITH TABLOCK still reports an error.
Then I tried to restart the service once, and the database worked. Running DBCC CHECKDB found no errors.
Feel this problem is very bogey, in the hardware disk is no problem even reported disk error.
Read More:
- Unable to open the physical file “d:\***.mdf”. Operating system error 5: “5(Access is denied.)”.
- Error messages of copying files to Linux system by PSCP in Windows operating system
- Solve the problem of non system disk or disk error, replace and strike any key when ready
- Solution to prompt “system group policy forbids installation of this device” in win10 system
- Windows 10 startup item repair an operating system was’t found solution
- SQL Server import MDF and LDF files appear: unable to open physical file “D:\ XX.mdf “。 Operating system error 5: “5 (access denied. )”Solutions
- Lenovo-win7 system computer boot prompt error 1962: no operating
- Windows 10 startup item repair an operating system wasn’t found
- error 1962:no operating system found.boot sequence will automatically repeat.
- Error report of xv6 operating system make Makefile:192 : * * solutions to receive comments before first target. Stop
- MySQL error: InnoDB: operating system error number 13 in a file operation
- Openproj reported error errno = 193 in 64 bit operating system
- Mac: how to show hidden files under Apple Mac operating system
- U disk installation Linux system could not boot, / dev / root does not exist and the identified hard disk space is not available
- Tensorflow 2.1.0 error resolution: failed call to cuinit: CUDA_ ERROR_ NO_ DEVICE: no CUDA-capable device is detected
- When react dynamically prunes components by operating arrays, the state of the remaining components is not preserved. Solution to the problem (method of dynamically setting unique key value)
- Ubuntu cannot access USB device, failed to create a proxy device for the USB device
- Virtual environment: error: virtualenv is not compatible with this system or executable
- 2021 / 06 / 28 error – because the script PowerShell is not allowed to run on this system
- Configuration: error:!! OpenSSL is not properly installed on your system