Thanks for the information. No other recordings were made once this was noticed, which is why I was confident with finding the data with recovery tools. Unfortunately I've had no luck with my XFS filesystem. Looks as though they recovered files that weren't even deleted for some reason, as well as some that were. But not the one I need.btidey wrote:I can't directly help with your immediate problem here but let me explain what may have happened and what I have done to maybe help in future.GammaScorpii wrote:I have a huge problem perhaps somebody out there can help me with. I've been using this great software to shoot lots of video clips and I have just lost a video file for some mysterious reason. The thumbnail jpg is still there in /var/media but the corresponding mp4/h264 file is nowhere to be found.
According to somebody who was watching the file grow as it was being shot, it disappeared most likely during the mp4 conversion process and never came back.
Any idea on what to do to recover it? It's an extremely important piece of footage and I'm worried now that I have tried using PhotoRec to recover any deleted files and haven't had any luck. PhotoRec did save the unknown data to a huge dd image but I have no idea on how to examine that.
My /var/media folder is an xfs partition if that helps.
Any advice on what to do next would be hugely appreciated and worth a credit on the film we're trying to make
Videos are first recorded to h264 format. When this completes a boxing command is queued up to convert to mp4 format and remove the original h264 file. The command is actually a MP4Box cmd followed by a rm command. The MP4Box cmd is very reliable, but if a problem occurred then the rm command would still execute removing the original h264 file.
To improve this I have made 2 enhancements in the latest version.
First the command line that is used for Boxing is now a configurable item in the /etc/raspimjpeg file so its behaviour may be changed.
Second I have added an extra step in this command line so that if the MP4Box process throws an error then the rest of the command line is NOT executed. This would mean that if this occurs again then the original h264 file will be left intact in the media folder.
That of course doesn't help with your immediate problem. The chance of recovering the video data from your unknown blob will depend on how quickly this was picked up. After the original file was 'rm' then the filing space becomes available for re-use. If there were a large number of recordings made after then the chance of the 'unused space' being overwritten becomes higher.
Do the temporary files ( *.mp4.h264 ) get saved to the same location?