There are scripts and methods to verify the data consistency, but this is not a situation where you can apply a data fix. You need to recover the database and/or data files, potentially from backup. If there is a LSN discrepancy, SQL should roll back or roll forward the batches or transactions when you restart as long as there is space available in the database files. There are methods to use to perform a database recovery as well but this is in the SQL Server realm. In the event of a storage hardware failure, you need to make the decision of how you're going to recover the data. That might be a manual rebuild of the database and log files, restore of the database from backup, recovery from a snapshot, etc. Sage utilities can repair portions of the data and aggregations but they are not going to be able to repair data that contains significant discrepancies in the parent-child (header to detail) or linked data, like sales order to shipment to invoice, relationships.

There are scripts and methods to verify the data consistency, but this is not a situation where you can apply a data fix. You need to recover the database and/or data files, potentially from backup. If there is a LSN discrepancy, SQL should roll back or roll forward the batches or transactions when you restart as long as there is space available in the database files. There are methods to use to perform a database recovery as well but this is in the SQL Server realm. In the event of a storage hardware failure, you need to make the decision of how you're going to recover the data. That might be a manual rebuild of the database and log files, restore of the database from backup, recovery from a snapshot, etc. Sage utilities can repair portions of the data and aggregations but they are not going to be able to repair data that contains significant discrepancies in the parent-child (header to detail) or linked data, like sales order to shipment to invoice, relationships.