Hi!
Recently the new FortiOS 7.6 was released, so being an enthousiast I upgraded a new F40 straight out of the box.
After the update the devices booted but I could not reach it by it's default IP.
Booting the device via console, I got error messages about interfaces en the configuration.
A few of these messages are:
Initialize config error 44010
The config file may contain errors.
Please see details by the command 'diagnose debug config-error-log read'.
The initial boot gives strange characters until it shows "system is starting" and after that everything is perfectly readable.
After the device booted I am unable to type anything in de commandline.
So, after this line it is stuck: Please see details by the command 'diagnose debug config-error-log read'.
I also tried different serial configuration (baud rate etc.). But that doesn't do the trick.
During boot I'm able to press a key but all the characters are gibberish, so a flash format is a challenge.
I'm not sure how to move forward, any suggestions?
Best regards,
Tim
Solved! Go to Solution.
Created on ‎08-19-2024 02:58 AM Edited on ‎08-19-2024 02:59 AM
Hi @tim86 ,
Normally I was going to suggest interrupt boot and format device. But as you said you don't use the boot menu for formatting purposes.
Maybe, you can try this. Download the old version (Because if you take these actions with the same version of the image FortGate will not do anything) of the firmware image from the Fortinet website, copy this file to a USB with the name image.out, and connect this USB to FortiGate. After that, you can reboot the Fortigate. Normally, FortiGate should read this file and format itself with this image.
Hello friend
The same thing is happening to me as to the user safvanv, I can't access anything on my Forti 40F. I see the same message as safvanv on the console, but when I insert the USB drive, it doesn't do anything, it continues loading and then gets stuck. I don't know what to do. Please help me, what should I do to recover it?
if it doesn't do autmatic flash from usb (which is the factory defautl setting btw) maybe some has disabled it or changed the file names.
In that case you still have the option to enter the boot menue and format the boot device (however this will also erase your config). After this is done you can upload a new firmware image via tftp in the boot menue.
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
I got it to work quite easily after switching back to Windows from Mac.
Plugging a console cable into the device and rebooting it, brought up the boot menu.
There, I chose to boot from the backup firmware, and it was as easy as that.
User | Count |
---|---|
2638 | |
1400 | |
810 | |
684 | |
455 |
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.