This short guide covers most common Storage-related errors User might met while utilizing the Nx Witness Software. Here they are called "Storage Failure" in the event log.
- "System disk is almost full".
Such error appears if Server detects that free space of the system partition drops under 1 GB for ARM devices and 5 GB for Desktop devices.
Nx team considers it as an issue which should be resolved because both OS and Nx System might suffer significantly due to that. Although it is understandable why OS needs a lot of free space, Nx Witness needs it because it keeps many important data at the system partition. E.g. system database, motion detection data indexes, audit log, etc.
- "Not enough HDD/SSD speed for recording to %drive_name%".
During the regular recording process server keeps all video frames received from every camera stream in separate buffers. The other part of the server later on tries to write frames from such buffers to the physical drive.
These buffers have certain reasonable limits, independently in megabytes and number of frames.
When due to some reason the storage drive write speed can not match the rate of incoming video packets/frames these buffers might overflow. When this happens server has to drop the oldest packages. After that the error is generated with number of the dropped frames. User might find which camera feed specifically suffered from main media server log.
If user receives such messages randomly, from time to time with low number of packets dropped -- there's nothing to worry about right now. Basically it signals that system is near its limits. So if user is planning to expand the system he should expect that number of dropped packages will drastically increase and resolve it in advance. Options are to decrease incoming bitrate by playing with fps/image quality, replacing drives with more fast ones or simply adding more drives.
If user receives such messages all the time it is something to worry about since significant part of footage is likely persistently lost. In this case user should start with monitoring write disks capabilities and check their state. If everything is ok and hardware issues are not observed -- the solution should be the same as mentioned previously.
There is one more case when such error might appear. It is logically to assume that if some disk unexpectedly completely fails(local) or goes offline(network) this message will likely be the first thing user notice in the logs.
- "I/O error occurred".
This trivially means that Operating System returned read/write error message to Media Server on the command to read or write data block. Depending on the setup this message might pop up in pair with the previous one. It definitely tells the user that major issues are happening. E.g. Operating System met the bad blocks, drive is unexpectedly remounted to read-only state or network file system returned remote service inaccessibility.
If you have any questions related to this topic or you want to share your experience with other community members or our team, please visit and engage in our support community or reach out to your local reseller.