| Description | This article describes how to troubleshoot, confirm, and resolve an issue where '/data2/madb.dat file size not match' log appears after a bootup sequence, and reaffirm that it is not a RMA issue. |
| Scope | FortiGate. |
| Solution |
To confirm the issue, take the output of 'diagnose autoupdate versions'. The output should look like the following:
Mac Address Database
The second output that should be collected is 'diagnose debug config-error-log read'. The output should result in the following:
diagnose debug config-error-log read
For a potential solution of the issue, the command 'execute update-now' should be done to trigger an update. However, as the output points out to a potential FortiGuard issue, the steps in the KB article from below should be taken to resolve the issue: Technical Tip: Verifying and troubleshooting FortiGuard updates status and versions.
Sometimes, the FortiGate is in an air-gapped environment and has no internet connectivity. In order to resolve this issue in such a case, open a ticket with TAC and request the latest Mac Address Database. After the installation package is received, the package should be installed. An example with the use of an FTP server is provided below:
execute restore other-objects ftp madb_fos72_00001.00300.pkg <server-ip>:<port> <username> <password>
Upon installation of the package, it is expected that the message will disappear and the issue is solved. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.