When there is a checksum mismatch we have two messages in __wt_block_read_off. One, if there is a checksum mismatch in the header and another if there is a checksum mismatch in the rest of the block. The header mismatch message includes the calculated checksum and the expected checksum. We should do the same for other message (shown below) regarding the rest of the block to better understand what has occurred when we encounter a blocksum mismatch.

            __wt_errx(session,
              "%s: potential hardware corruption, read checksum error for %" PRIu32
              "B block at offset %" PRIuMAX
              ": calculated block checksum doesn't match expected checksum",
              block->name, size, (uintmax_t)offset);