Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
Inspect the SQL Server error log and determine the cause of the error. If SQL Server has been restarted since the failed recovery, look at previous SQL Server error logs to see the reason why recovery failed.
If the recovery failed because of a persistent I/O error, a torn page, or other possible hardware problem, resolve the underlying hardware problem and restore the database by using a backup. If no backups are available, consider the repair options of DBCC CHECKDB.
If you are unable to resolve this problem, contact your primary support provider. Have the SQL Server error log available for review.