(The device is not ready.) to SQL Server during a read at offset 0x00001573c00000 in file

Question

(The device is not ready.) to SQL Server during a read at offset 0x00001573c00000 in file

coolchaitu

SSChampion

Points: 10332
More actions
July 23, 2017 at 10:40 pm

#338475

Good morning Experts,
Today morning when i came to office, i saw that a job failed because a database went to "Recovery Pending" Status. I ran alter database <dbname> set online and the database came online. I re-ran the dependent job and it threw the below error:
"The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00001573c00000 in file 'D:\Program Files\Delphix\DelphixConnector\4225171c-a26b-ce4b-9659-447c7b7df6cf-vdb-1\DATA\db\SBX_11_data.ndf'.
I ran DBCC Checkdb on the database and it is clean. Please advise on how to proceed further

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Sue_H SSC Guru Points: 90860 More actions · Answer 1

coolchaitu - Sunday, July 23, 2017 10:40 PM
Good morning Experts,
Today morning when i came to office, i saw that a job failed because a database went to "Recovery Pending" Status. I ran alter database <dbname> set online and the database came online. I re-ran the dependent job and it threw the below error:
"The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00001573c00000 in file 'D:\Program Files\Delphix\DelphixConnector\4225171c-a26b-ce4b-9659-447c7b7df6cf-vdb-1\DATA\db\SBX_11_data.ndf'.
I ran DBCC Checkdb on the database and it is clean. Please advise on how to proceed further

It's not a SQL Server error - it is an error from the OS for the D:\ disk - "is not ready" - which can mean different things. The disk wasn't reachable, disk offline, the disk or a sector wasn't readable, etc. You would want to check the SQL Server error log for additional errors as well as the Windows event logs for disk related issues or errors.

Sue

coolchaitu SSChampion Points: 10332 More actions · Answer 2

Sue_H - Tuesday, July 25, 2017 8:21 AM
coolchaitu - Sunday, July 23, 2017 10:40 PM
Good morning Experts,
Today morning when i came to office, i saw that a job failed because a database went to "Recovery Pending" Status. I ran alter database <dbname> set online and the database came online. I re-ran the dependent job and it threw the below error:
"The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00001573c00000 in file 'D:\Program Files\Delphix\DelphixConnector\4225171c-a26b-ce4b-9659-447c7b7df6cf-vdb-1\DATA\db\SBX_11_data.ndf'.
I ran DBCC Checkdb on the database and it is clean. Please advise on how to proceed further
It's not a SQL Server error - it is an error from the OS for the D:\ disk - "is not ready" - which can mean different things. The disk wasn't reachable, disk offline, the disk or a sector wasn't readable, etc. You would want to check the SQL Server error log for additional errors as well as the Windows event logs for disk related issues or errors.
Sue

I checked the error logs and found same error messages. What could be the reson for disk wasn't reachable or a sector wasn't readable

Ed Wagner SSC Guru Points: 287024 More actions · Answer 3

Is there something else in plan at the OS level that's taking the volume offline for a brief period? I'm thinking along the lines of SAN snapshot or Backup Exec with the SQL Server module. You may need to check with your network or SAN administrator if that's the case.

Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions

coolchaitu SSChampion Points: 10332 More actions · Answer 4

Ed Wagner - Monday, July 31, 2017 7:18 PM
Is there something else in plan at the OS level that's taking the volume offline for a brief period? I'm thinking along the lines of SAN snapshot or Backup Exec with the SQL Server module. You may need to check with your network or SAN administrator if that's the case.

The data files of all databases are kept in same volume. I am curious to know, if volume goes offline for a brief period, it must affect all databases, however its only affecting one database

Arsh SSCertifiable Points: 6345 More actions · Answer 5

coolchaitu - Monday, July 31, 2017 7:22 PM
Ed Wagner - Monday, July 31, 2017 7:18 PM
Is there something else in plan at the OS level that's taking the volume offline for a brief period? I'm thinking along the lines of SAN snapshot or Backup Exec with the SQL Server module. You may need to check with your network or SAN administrator if that's the case.
The data files of all databases are kept in same volume. I am curious to know, if volume goes offline for a brief period, it must affect all databases, however its only affecting one database

Probably this database and this data file in particular , is hit more than others . Do check for any anti viruses, or any other such application used generally by infrastructure teams, running on this server .