FortiAnalyzer
FortiAnalyzer can receive logs and Windows host events directly from endpoints connected to EMS, and you can use FortiAnalyzer to analyze the logs and run reports.
vkulik
Staff
Staff
Article Id 198434

Description

 

This article describes how to handle an issue where a FortiGate or a FortiAnalyzer unit doesn't boot properly and/or some errors are displayed in the console during the boot.

Example 1

Reading boot image 1463602 bytes.
Initializing firewall...
System is started.
EXT3-fs error (device md(9,0)): ext3_readdir: bad entry in directory #1474561: r
ec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
EXT3-fs error (device md(9,0)): ext3_readdir: bad entry in directory #1474561: r
ec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0

 

Example 2

Reading boot image 1463602 bytes.
Initializing firewall...
System is started.
EXT3-fs error (device ide0(3,1)): ext3_get_inode_loc: unable to read inode block - inode=65409, block=131074
EXT3-fs error (device ide0(3,1)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,1)): ext3_get_inode_loc: unable to read inode block - inode=65409, block=131074
EXT3-fs error (device ide0(3,1)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,1)): ext3_get_inode_loc: unable to read inode block - inode=130817, block=262146
EXT3-fs error (device ide0(3,1)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide0(3,1)): ext3_get_inode_loc: unable to read inode block - inode=65409, block=131074
EXT3-fs error (device ide0(3,1)) in ext3_reserve_inode_write: IO failur

 

Some error details may vary from a device to another, but the EXT3-fs error indicates there is an issue with the local file system.

Scope


Fortigate, FortiAnalyzer, FortiOS, hardware, firmware, boot, filesystem.

Solution


This issue appears to be due to some corruption in the file system that affects the boot device and/or firmware loading.
Fix this by using diagnose system fsck harddisk.

If the issue persists, this may be resolved by reformatting the boot device and reinstalling the firmware via TFTP.
Make sure to reload the same firmware version as the one used to save the configuration backup file. In case there is no  configuration backup file, the unit needs to be reconfigured from scratch.

Solution steps:

 

  1. Connect to the unit on the serial console.
  2. Reboot the unit and hit any key to enter the Boot Menu
  3. Select 'format boot device'.
  4. Select 'Reload Firmware via TFTP'.
  5. When the unit is up, open the Web Based Manager (GUI) and go to System -> Maintenance -> Restore -> restore latest configuration form backup.

Related articles:

Technical Tip: Formatting and loading FortiGate firmware image using TFTP.