However, depending on how the data was logged, it might not be possible to get anything back.
When growing WAV files, it is common for one chunk of WAV data to be written out, and then for the header to be updated to reflect how long it turned out to be. Unfortunately that is prone to problems if you try to store more than the maximum file size, or if something goes wrong during the writing. One approach that reduces the errors is to update the header after a bufffer-full, so that at any one time only the last buffer might go missing... provided that you do not write too much data.
Another approach when growing WAV files is to put bunches of samples into separate segments. If I recall correctly you can get around some of the header limitations by mostly ignoring them, and writing out chunks that each individually live within the size limits. The original WAV format was designed by Microsoft to be able to just copy one WAV file after another without having to update anything in the headers. If that is the approach taken by the software, you might be able to get a fair bit of the data back, perhaps.
But if the data happened to be logged to a filesystem that has a 2 gigabyte limit, then it becomes more difficult to predict what the file system would have done with the file when you tried to grow the file larger than that.
