InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 06:09:04 GMT20http://www.sqlservercentral.com/Forums/Topic1103497-391-1.aspx"Device not ready" usually means the server lost a disk (if your disk is a SAN device), check with your SAN admin to see what happened.You can confirm it by looking in the windows system event log, you should see messages from the SAN vendor driver (i.e. EMC drivers complaining a path/port/device just died).Once you get your disk back (after a few seconds or after intervention) you can try: [code="sql"]ALTER DATABASE [MyDB] SET ONLINE[/code]If that fail, the error log will give you more info on what's going on.Thu, 30 May 2013 07:29:53 GMTOliiiihttp://www.sqlservercentral.com/Forums/Topic1103497-391-1.aspxHi,I just got the same error on one of my database and would like to share how I recovered from it. Troubleshooted by following (1)Take database offline (2) bring database online (3) change the database property to Auto Close = False(4) we need to run dbcc so we will require db in single mode. change the database property to single user mode. (5) run below dbcc command dbcc checkdb ('db', REPAIR_REBUILD)(6) now it should run fine and above log related error should not appear.(7) change database property to “Multi User mode”Note that we run dbcc every weekly and this error was not appeared at that time. I also have plenty of free disk space so I am still not clear why error appeared.In my case above method worked. If there is any better way to troubleshoot this, then let me know. Can someone let me know why this error appears? I mean what causes this ?Thu, 30 May 2013 06:56:33 GMTJatin Sonihttp://www.sqlservercentral.com/Forums/Topic1103497-391-1.aspxRestart the sql service, and it will start working.The same thing happened for me also. and i did the same..Now its working fine.Tue, 19 Mar 2013 01:53:02 GMTer.neelkamalhttp://www.sqlservercentral.com/Forums/Topic1103497-391-1.aspxHiI know this is an old post but I had the same problem and we run a SAN an VMware so I thought it's related to that but then I found another post telling me to bring the db offline and online again and that actually worked. Very simple in the end.Mon, 28 Jan 2013 22:03:01 GMTTerence Keyshttp://www.sqlservercentral.com/Forums/Topic1103497-391-1.aspx[quote][b]Greg Swanson (6/1/2011)[/b][hr]FYI: There is a VMWare issue that is associated with getting this error having to do with using the Paravirtual SCSI drivers. See the following KB: [url=http://support.microsoft.com/kb/2519834][/url]Greg[/quote]Not running WMWare on that system, but thanks for the info/update!Wed, 01 Jun 2011 11:53:13 GMTSkyBoxhttp://www.sqlservercentral.com/Forums/Topic1103497-391-1.aspxFYI: There is a VMWare issue that is associated with getting this error having to do with using the Paravirtual SCSI drivers. See the following KB: [url=http://support.microsoft.com/kb/2519834][/url]GregWed, 01 Jun 2011 10:56:11 GMTGreg Swansonhttp://www.sqlservercentral.com/Forums/Topic1103497-391-1.aspxI wouldn't say disk contention (but I'm not a SAN expert). Check the physical connections, switch, anything between the server and SAN. From the Windows error log, the OS can't see the disk at points.Moving the DB will help, but you still need to find the root cause.Wed, 04 May 2011 15:19:37 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1103497-391-1.aspxJust stumbled into a VERY similar thread on this site:http://www.sqlservercentral.com/Forums/Topic355924-5-1.aspx#bm482958Wed, 04 May 2011 15:02:13 GMTSkyBoxhttp://www.sqlservercentral.com/Forums/Topic1103497-391-1.aspxYes, SAN storage. Just found out the tempdb partition and translog partition share the same physical drive. I can move the tempdb file to the larger database drive immediately - well late tonight.Could this disk contention be causing the hardware error?It's been running this way for a while now, but being hit harder lately. FYI - I will schedule CHECKDB's weekly, maybe daily now.Wed, 04 May 2011 14:54:41 GMTSkyBoxhttp://www.sqlservercentral.com/Forums/Topic1103497-391-1.aspxp.s. If I were you, I'd be doing checkDB more often than once in 2 months.Wed, 04 May 2011 14:47:54 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1103497-391-1.aspxLooks like a hardware issue. Server is losing contact with the underlying drives.SAN storage?Wed, 04 May 2011 14:44:07 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1103497-391-1.aspxTesting and Production db's have lost connection to the translog 2 days in a row now. Today, my prod db was marked suspect after the issue - SCARY. The other db's did not lose connection. Possibly because there was no activity at that moment. No errors in SQL log, only windows. Server Resources were not necessarily be hammered. I will be scouring the web, but wanted to reach out to all of you as well. See info and errors below.Plenty of available drive space for Log, db, and tempdb partitions. 144gb RAMSQL Server 2008 SP1; Enterprise (64-bit)OS: Win Server 2008 R2 Enterprise[b]Win app logs:[/b]error1- LogWriter: Operating system error 21(The device is not ready.) encountered.error2 - The log for database (testing) is not available. Check the event log for related error messages. Resolve any errors and restart the database.info mess3- Database was shutdown due to error 9001 in routine 'XdesRMFull::Commit'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.[b]2 seconds later prod db goes down:[u][/u][/b]error4- The log for database is not available. Check the event log for related error messages. Resolve any errors and restart the database.error5 - During undoing of a logged operation in database, an error occurred at log record ID (86400:39070:17). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.error6 - fcb::close-flush: Operating system error (null) encountered.error7 - An error occurred during recovery, preventing the database (PRODUCTION :w00t:) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.info mess8 -CHECKDB for database finished without errors on 2011-03-14 12:12:41.503 (local time). This is an informational message only; no user action is required.Wed, 04 May 2011 14:39:28 GMTSkyBox