Data storage issues
If FortiRecorder cannot locally store any data such as logs, reports, and video, and FortiRecorder has been storing data but has suddenly stopped, first verify that FortiRecorder has not used all of its local storage capacity by entering this CLI command:
diagnose hardware sysinfo df
which will include disk usage for all mounted file systems, such as:
Filesystem Size Used Avail Use% Mounted on
none 180M 104M 77M 58% /
none 0 0 0 - /proc
none 0 0 0 - /sys
none 0 0 0 - /dev/pts
none 10M 32K 10M 1% /dev/shm
/dev/sdb1 284M 54M 230M 19% /data
/dev/sda2 92G 333M 87G 1% /var/log
/dev/sda3 824G 118G 665G 16% /var/spool
//172.16.10.200/NVR 226G 25G 201G 11% /mnt/remote
| You can use alerts to notify you when FortiRecorder has almost consumed its hard disk space. You can also configure FortiRecorder to overwrite old logs rather than stopping logging when the disk is full. (Keep in mind, however, that this may not prevent full disk problems for other features. To free disk space, delete files such as old reports and video that you no longer need.) |
If a full disk is not the problem, examine the configuration to determine if an administrator has disabled those features that store data.
If neither of those indicate the cause of the problem, verify that the disk’s file system has not been mounted in read-only mode, which can occur if the hard disk is experiencing problems with its write capabilities. For details, contact Fortinet Technical Support.