InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 25 May 2013 10:24:44 GMT20http://www.sqlservercentral.com/Forums/Topic1404454-1550-1.aspxalexandert680@gmail.com1/9/2013)[/b][hr]Post the exact errors from the SQL error log (all of them), then switch the DB into Emergency mode and run[code]DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS[/code]and post those errorsYou can't just reset the status on a suspect DB to normal. Suspect means damaged, has to be restored (prefered) or repaired (if there's no backup)If it's just the error 21, then a restart of SQL might fix it, and then you need to identify why the disks are disappearing underneath SQL.[/quote]One of my colleague reboot the server and it solved the issue. Anyway, I had contacted the windows/storage team to investigate further.Thanks for all your valuable inputs.SueTons.Wed, 09 Jan 2013 17:23:49 GMTSQLCrazyCertifiedhttp://www.sqlservercentral.com/Forums/Topic1404454-1550-1.aspxPost the exact errors from the SQL error log (all of them), then switch the DB into Emergency mode and run[code]DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS[/code]and post those errorsYou can't just reset the status on a suspect DB to normal. Suspect means damaged, has to be restored (prefered) or repaired (if there's no backup)If it's just the error 21, then a restart of SQL might fix it, and then you need to identify why the disks are disappearing underneath SQL.Wed, 09 Jan 2013 02:37:54 GMTGilaMonsterhttp://www.sqlservercentral.com/Forums/Topic1404454-1550-1.aspxThanks Jason. Will look into it.SueTons.Tue, 08 Jan 2013 16:21:59 GMTSQLCrazyCertifiedhttp://www.sqlservercentral.com/Forums/Topic1404454-1550-1.aspx[quote][b]SQLCrazyCertified (1/8/2013)[/b][hr]Thanks, I did that.I ran dbcc chekcdb(dbname)....and looked at the error, I see an error 'An error occurred in the service broker manager, error:823, state 2.I also see another error says 'The operating system returned error 21(the device is not ready.) to sql server during at offset 0x0000..........etc.I know we can reset the status to recovery.....but I am more looking at what exactly the cause for this so, it won't happen again.Thanks,SueTons.[/quote][quote]The operating system returned error 21(the device is not ready.)[/quote]This message is an operating system error. It is more of a generic message letting you know there is an issue with the disk subsystem. It can be caused by a number of things such as:LUNS not being available for the OSthe SAN was unpluggedTue, 08 Jan 2013 16:07:09 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic1404454-1550-1.aspxThanks, I did that.I ran dbcc chekcdb(dbname)....and looked at the error, I see an error 'An error occurred in the service broker manager, error:823, state 2.I also see another error says 'The operating system returned error 21(the device is not ready.) to sql server during at offset 0x0000..........etc.I know we can reset the status to recovery.....but I am more looking at what exactly the cause for this so, it won't happen again.Thanks,SueTons.Tue, 08 Jan 2013 15:29:32 GMTSQLCrazyCertifiedhttp://www.sqlservercentral.com/Forums/Topic1404454-1550-1.aspxfirstly check the SQL errorlog for error messages - next steps depend on the errors.Tue, 08 Jan 2013 15:23:07 GMTgeorge sibbaldhttp://www.sqlservercentral.com/Forums/Topic1404454-1550-1.aspxAll,I have couple of the databases are under suspect mode.What are some of the process you should follow under this circumstance. Please advise.Thanks,SueTons.Tue, 08 Jan 2013 14:38:59 GMTSQLCrazyCertified