2

The web console just gets connection refused.

The SSH console connects but hangs when when i:

Attempt to change the configuration. (Hangs after the end command)

Attempt to restore from a config backup. (Hangs after retrieving the file from ftp and verifying it)

The device has been rebooted to no avail.

  • Have you tried to use the console or USB management interfaces? – Ron Maupin Feb 13 '18 at 14:26
  • No, the device is not at my physical locatiom i'm planning to go onsite shortly and will connect a console cable and make said attempt again. – Aaron Tate Feb 13 '18 at 21:32
  • Did any answer help you? If so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you could provide and accept your own answer. – Ron Maupin Feb 21 '18 at 18:06
2

It sounds like the flash filesystem (or hardware) is corrupt and needs rebuilding.

This Fortigate does not have an internal disk but a flash memory storage for holding the firmware, the configuration file and the signature databases for AV, IPS etc. It can happen that the flash filesystem is partially corrupted. You can try to rebuild it but if the underlying reason is a hardware defect this remedy won't last long.

You need physical access to the unit, a console cable (RJ45 to serial, Cisco type), a notebook with

  • a TFTP server
  • the currently installed firmware image (*.out)
  • a backup of the current configuration (*.conf)

Then, - connect to the console port so that you can see the progress and enter something
- reboot the FGT (hard power cycle)
- press any key to interrupt the boot process
- type 'F' to format the boot disk
- connect a notebook via ethernet
- the default IP address of the FGT is 192.168.1.99, choose .101 for the notebook (statically, no DHCP available)
- type 'H' to see the option to load firmware
- upload the firmware image via TFTP
- after reboot the FGT will wake up in factory reset state
that is, default login is 'admin' with no password
- restore the config from file

There is a chance that the internal flash memory chip is damaged, especially if you used it for local logging. If you need to log then log into memory otherwise the wear and tear will damage the flash memory over time. A damaged flash usually signifies the end of life of this FGT.

| improve this answer | |
  • Can't upvote this more than once - but I'd like to. Countless were the night hours spent with crumbling flash filesystems on FG200B until we finally could get rid of them. The symptoms used to be exactly as the orginal question describes - and the cure was indeed to boot from some other source than the internal flash; USB might help here, if TFTP is not available. – Marc 'netztier' Luethi Aug 14 '18 at 21:22

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.