Bad checksum errors can occur when saving the extracted 2D channels and during data acquisition - WKB72973

SYMPTOMS

• Bad Checksum
• Data file Checksum error, possible data corruption
• Data Incomplete
• Error: Failed to read good raw data file with ID ####

ENVIRONMENT

• Empower
• Acquisition
• Saving extracted 2D channels
• Occurs when review is also open on the same node on which you are performing background processing.

CAUSE

Bad Checksum error can occur when acquisition is interrupted or the data file is not closed properly. This is usually due to intermittent network issues. Because they are intermittent, buffering does not start, but still causes a problem with the .dat file. Acquisition is not interrupted and continues to the next injection. 

Typically, this data can be brought into Review and a privileged user can Verify it as Complete.

The ability to diagnose this problem was improved in E3 SR3. In this scenario, it is expected that the Channel Status is Being Acquired and the Injection Status is Incomplete.  The user can then verify the data as complete.

The Bad Checksum error can also be caused by a failure to properly close that saved extracted 2D channel.

As with the Bad Checksum error that occurs during acquisition, this is usually due to intermittent network issues and the data can be brought into Review and a privileged user can Verify it as Complete.

FIX or WORKAROUND

1. Do not to have review open on the same node when background processing.
2. Do not save extracted 2D channels when processing 3D data.
3. If Bad Checksum occurs when 1 and 2 are not employed or also occurs during acquisition, investigate the network performance.
4. Customer should utilize the "Verify incomplete data" function to inspect data that reports Bad Checksum.

ADDITIONAL INFORMATION

Note: When data is "Verified as Complete", the Checksum is recalculated.

CRI-703 and CRI-800 were raised for this.