Device Not Ready Error 21
Contents |
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On operating system error 21 error not found Home » SQL Server 2005 » Administering » The operating system returned goodsync error 21 error 21. The... 11 posts,Page 1 of 212»» The operating system returned error 21. The device is error 21 the device is not ready server service not ready Rate Topic Display Mode Topic Options Author Message na1774na1774 Posted Thursday, February 16, 2012 1:29 AM SSC Journeyman Group: General Forum Members Last Login: Wednesday, September 9,
Error 21 The Device Is Not Ready Starting Service
2015 1:51 PM Points: 93, Visits: 273 Hello Guys,One of our prod servers went offline and I received a Ticket mentioning the below error.ftwp1lqrbgd01 - SQL EventID 823. The operating system returned error 21. The device is not readyCan any body help me to interpret this error. The first part(ftwp1lqrbgd01) in the above error is the server error 21 the device is not ready sql server name. So I rebooted the server and then looked in Event Viewer. I did not see any event with EvenID 823.I just dont understad why my server went offline what caused the above error to come up.Any Ideas? Post #1252913 na1774na1774 Posted Thursday, February 16, 2012 1:46 AM SSC Journeyman Group: General Forum Members Last Login: Wednesday, September 9, 2015 1:51 PM Points: 93, Visits: 273 I went into the event log and observed the below errorThe operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000000012000 in file 'E:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\IP_SDMP.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.can any one explain me whats going on? Post #1252917 anthony.greenanthony.green Posted Thursday, February 16, 2
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums error 21 iphone Answered by: The operating system returned error 21(The device is
Failed With The Operating System Error 21 The Device Is Not Ready
not ready.) SQL Server > SQL Server Database Engine Question 0 Sign in to
Device Not Ready Error Initializing Disk
vote Dear DBAs, A database backup job has failed for the last couple of days with below error. I see that there is no P http://www.sqlservercentral.com/Forums/Topic1252913-146-1.aspx drive for PP1DATA. When I tried to bring drives online to find P drive and bring it up I couldn't bring them online. Is the absence of P drive related to this error? Thank you, ." failed with the following error: "The operating system returned error 21(The device https://social.msdn.microsoft.com/Forums/sqlserver/en-US/27ef2342-d8d0-42f0-807a-41a15dd1856f/the-operating-system-returned-error-21the-device-is-not-ready?forum=sqldatabaseengine is not ready.) to SQL Server during a write at offset 0x0000005ec32000 in file 'P:\PP1DATA1\PP1DATA1.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. BACKUP DATABASE is terminating abnormally." Wednesday, September 08, 2010 5:52 PM Reply | Quote Answers 0 Sign in to vote Junior, Sort of. I misunderstood what the P drive was, sorry about that. It seems that the backup failed because it could not find the MDF for the database it was trying to back up. I am actually surprised that your instance was running at all. Are your system databases on a different dri
Job history It was failing due to compression error. I checked the version etc and everything was fine. I decide to take http://accidentalsqldba.blogspot.com/2016/04/error-21the-device-is-not-ready-in-sql.html a differential backup with script. It also got failed with error "BACKUP DATABASE is terminating abnormally" Although this was not related to space issue but still i checked for disk space and there http://buildingcareerforu.blogspot.com/2011/02/dbcc-checkdb-operating-system-returned.html was plenty of free space. I decide to check the error log file and there it was.... "The operating system returned error 21(The device is not ready.) to SQL Server during a read error 21 at offset 0x00000000e56000 in file 'H:\MSSQL\Data\XXX.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online." Since the error message error 21 the says that the drive on which data file resided was not ready, it was too obvious that there was some storage problem. I checked the system event log but did not found any error related to disk. The database was online and accessible. But when I tried to access the Properties of the databases, the same error was thrown. I was not able to see the user tables under the databases. But the other queries like sp_helpfile and select * from sysobjects were executing successfully. When I tried to access a user table by script it was failing with the same error. I sent an email to storage team and they confirmed that everything was fine from there side. There were two options with me to fix this issue at that time. 1:Take the database offline and bring it online. 2: Another was restart the SQL server. There were more than one databases on my SQL server instance so I restarted the SQL server service. The database came online and the *device not ready* error message disappeared. The next action you can take is to run DBCC on your database. Thanks!! Posted by Vimal Kumar Prajapat
CheckDB The operating system returned error 21(The device is not ready.)" Please follow following steps carefully. 1. run xp_readerrorlog and find the recent errors. 2. run xp_fixeddrives to see if all the drives can be read from sql server. 3. Look for the eventviewer. The issue can be some RAID controller or other h\w sources. 4. Don't detach the DB. 5. Look for restoring the latest backup if the problem is still a panic. 6. Do NOT restart neither your m\c nor your sql service. Regards, Online MSSQL Classes @ http://tuitionaffordable.webstarts.com Posted by BuildingCareerForU at 10:14 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe Now: Posts Atom Posts Comments Atom Comments Blog Archive ▼ 2011 (13) ► April (1) ▼ February (3) MSSql Error 1088 - Cannot find the object "tuition... MSSQL Server Error: "Cannot generate SSPI context"... DBCC CheckDB The operating system returned error 2... ► January (9) About Me BuildingCareerForU View my complete profile There was an error in this gadget Popular Posts MSSQL Interview Question Clustering- Part1 Will Indian Rupee Cross 55?? Cluster environment is prevalent not only in big organizations but also medium and small. This is observed t... MSSQL Interview Question Clustering- Part2 Will Indian Rupee Cross 55?? Q: What will happen if you try to start the SQL service on the passive node? Ans: This will start because e... Understand Query Execution Plan- Index Scan, Index Seek And Key Lookup Will Indian Rupee Cross 55?? It is always recomended to use either Clustered or NonClustered Index on a table for better performance of q... MSSQL Interview Question Clustering- Part4 Q: What is the standard setting of Lookslive, IsAlive and Pending Timeout? Ans: LooksAlive - 5 sec IsAlive - 30 sec Pending Timeout - 180... MSSQL Interview Question Clustering- Part3 Q6 - Why is this needed to manage the max memory on failover cluster? Ans: So if you have a two-node cluster, each currently configured wit... DBCC CheckDB The operating system returned error 21(The device is not ready.) Will Indian Rupee Cross 55?? Following error can be very difficult to deal with this error if not dealt properly. "DB