If when using the traditional recording method (i.e. File Server is the Primary Recording Target), you cannot access the recordings for a specific camera then it is possible that the .erdinfo file has become corrupted. In this case you will need to conduct a forced rebuild of the file to rectify the issue. The .erdinfo file is the cameras index of events and sequences of the stored data. As a result when it becomes corrupted the order of events can not be defined, causing the camera and / or the viewing software to crash.
- Disable Recording and Reboot
- Go into the share folder for the specific camera
- example /mobotix/10_0_117_27
- Find & remove the .erdinfo file in that folder
- Enable Recording and Reboot
- The camera will then rebuild the .erdinfo file.
- During the boot the camera looks for this file and will search the entire storage medium for its files and rebuild the .erdinfo file.
- This may take some time depending on how large the storage medium is. You can check to see if the camera is still initializing by checking the camera status page for INIT in the External Storage section.
Please note that during the re-build process the camera will not be able to record. Hence, proceed only if you can afford to miss some footage!
Factors that could cause the corruption of the .erdinfo file
Possible causes of a corrupted .erdinfo file may include:
- Problems delivering images through the network to the NAS
- The NAS not being able to cope with throughput
- Somebody moving already registered files from the storage
The .erdinfo file is the cameras index of events and sequences of the stored data. As a result when it becomes corrupted the order of events can not be defined, causing the camera and / or the viewing software to crash. The remedy to this issue is to conduct a forced rebuild of the file, as outlined in this document.