On 7.2.15 one of our 2 member DAG servers lost 1 drive. We have not replaced it as of yet. The other DAG member was just updated with exchange updates and i logged into the ECP to just check that everything reported ok and saw this error. If i click on Resume in the ECP->servers-DB's i get:

warning

Are you sure you want to resume replication?Suspend comments: The database copy was automatically suspended due to failure item processing. At '7/2/2015 4:44:34 PM' the Exchange store database 'Mailbox Database' copy on this server experienced a serious I/O error. For more details about the failure, consult the Event log on the server for other storage and "ExchangeStoreDb" events. The passive database copy has been suspended.

With the option to click yes or no. I wouldn't think that losing 1 drive would cause this type of problem? Am i ok to click yes or not?

Also, are we running a risk by having 1 DAG updated and the other not updated?

http://exchangeserverpro.com/how-to-reseed-a-failed-database-copy-in-exchange-server-2013/

says to first resolve the root cause then reseed the DB. This is the correct way to handle this issue?

So, i replaced the faulty drive. Now what do i do to restore the DB? Should i follow the above link?

So i went ahead and clicked "update" and then received this:

error

The seeding operation failed. Error: An error occurred while performing the seed operation. Error: The request could not be performed because of an I/O device error.
 [Database: Mailbox Database, Server: host.server.tld]

All the lights on the drives are green (none are blinking amber). Should i reboot the server? Starting to get a little worried now :)

• Edited by forgiven 9 hours 2 minutes ago

So, our exchange DB in on a physically separate drive from the OS. So we have C: and D:. D: is where exchange DB is located (D:\Exchange\Mailbox\DB). When i login to the exchange server, i can access the D: but get an error about an I/O problem when accessing D:\Exchange\Mailbox\DB. Should i run a chkdsk on that drive in the hopes that will make D:\Exchange\Mailbox\DB accessible again?

So, i replaced the faulty drive. Now what do i do to restore the DB? Should i follow the above link?

So i went ahead and clicked "update" and then received this:

error

The seeding operation failed. Error: An error occurred while performing the seed operation. Error: The request could not be performed because of an I/O device error.
 [Database: Mailbox Database, Server: host.server.tld]

All the lights on the drives are green (none are blinking amber). Should i reboot the server? Starting to get a little worried now :)

• Edited by forgiven Monday, July 06, 2015 10:23 PM

Hi,

For your question, the drive might be damaged.

If the copy with the error is the active copy, use the Move-ActiveMailboxDatabase cmdlet to perform a database switchover and specify a Mailbox server host for the active copy of a mailbox database.
Besides, please run diagnostics test on the hard disk on which the database copy is stored to determine whether the issue was caused by a hardware failure. Replace the hard disk if necessary.

Thanks

So, our exchange DB in on a physically separate drive from the OS. So we have C: and D:. D: is where exchange DB is located (D:\Exchange\Mailbox\DB). When i login to the exchange server, i can access the D: but get an error about an I/O problem when accessing D:\Exchange\Mailbox\DB. Should i run a chkdsk on that drive in the hopes that will make D:\Exchange\Mailbox\DB accessible again?

Check the Windows Event logs and see if you have NTFS errors.  If this is SAN Storage check to see if there are any errors on the SAN.  Also, run checkdsk and see if that finds any errors.