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.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
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.
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.
I think I solved it, after the placement of a USB drive the device suddenly prompted the boot menu.
I was able to boot with the back-up firmware, currently upgrading the device!
Thank you!!
To resolve the issue, try using a USB drive with an older firmware version named image.out. Connect the USB to your FortiGate and reboot the device; this should prompt the boot menu and allow you to restore the firmware. I was able to resolve the issue by properly connecting the USB drive, which triggered the boot menu and allowed me to proceed with the firmware restoration.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1570 | |
1034 | |
749 | |
443 | |
210 |
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 2024 Fortinet, Inc. All Rights Reserved.