Fortinet 658 FortiWeb 5.0 Patch 6 Administration Guide
If FortiWeb has been storing data but has suddenly stopped, first verify that FortiWeb has not
used all of its local storage capacity by entering this CLI command:
diagnose system mount list
to display disk usage for all mounted file systems, such as:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/ram0 61973 31207 30766 50% /
none 262144 736 261408 0% /tmp
none 262144 0 262144 0% /dev/shm
/dev/sdb2 38733 25119 11614 68% /data
/dev/sda1 153785572 187068 145783964 0% /var/log
/dev/sdb3 836612 16584 777528 2% /home
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 (see “Hard disk corruption or failure” on page 658).
Bootup issues
While FortiWeb is booting up, hardware and firmware components must be present and
functional, or startup will fail. Depending on the degree of failure, FortiWeb may appear to be
partially functional. You may notice that you cannot connect at all. If you can connect, you may
notice that features such as reports and anti-defacement do not work. If you have enabled
logging to an external location such as a Syslog server or FortiAnalyzer, or to memory, you
should notice this log message:
log disk not mounted
Depending on the cause of failure, you may be able to fix the problem.

Hard disk corruption or failure

FortiWeb appliances usually have multiple disks. FortiWeb stores its firmware (operating
system) and configuration files in a flash disk, but most models of FortiWeb also have an
internal hard disk or RAID that is used to store non-configuration/firmware data such as logs,
reports, auto-learning data, and web site backups for anti-defacement. During startup, after
FortiWeb loads its boot loader, FortiWeb will attempt to mount its data disk. If this fails due to
errors, you will have the opportunity to attempt to recover the disk.
To determine if one of FortiWeb’s internal disks may either:
• have become corrupted
• have experienced mechanical failure
You can use alerts to notify you when FortiWeb has almost consumed its hard disk space. See
“SNMP Traps” on page 585. You can also configure FortiWeb to overwrite old logs rather than
stopping logging when the disk is full. See “When log disk is full” on page 550. (Keep in mind,
however, that this may not prevent full disk problems for other features. To free disk space,
delete files such as auto-learning data and old reports that you no longer need.)