Skip to main content
tim86
tim86
New Member
August 19, 2024
Solved

New device stuck after firmware upgrade to 7.6

  • August 19, 2024
  • 7 replies
  • 18961 views

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 

 

 

 

    Best answer by ozkanaltas

    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.

     

    https://community.fortinet.com/t5/FortiGate/Technical-Tip-Firmware-Upgrade-and-Configuration-Restore-using-a/ta-p/197057

     

    7 replies

    ozkanaltas
    ozkanaltasAnswer
    Valued Contributor III
    August 19, 2024

    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.

     

    https://community.fortinet.com/t5/FortiGate/Technical-Tip-Firmware-Upgrade-and-Configuration-Restore-using-a/ta-p/197057

     

      safvanv
      safvanv
      New Member
      January 28, 2025

      i tried , but nothing happened 

      The config file may contain errors.
      Please see details by the command 'diagnose debug config-error-log read'.
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb485350:0x7f9709a150 duplicated action=find-dup, vdom=root, node=system.interface.name, key=[wan]
      [fwinit_interface:436] cmf_query_table_append_static wan error
      Interface initialize error
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb46a510:0x7f970960c0 duplicated action=find-dup, vdom=root, node=system.physical-switch.name, key=[sw0]
      cmf_query_table_append_static sw0 error
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb48f380:0x7f96e120a8 duplicated action=find-dup, vdom=root, node=system.replacemsg.mail.msg-type, key=[partial]
      Can not add table entry, createTable,705: partial table mail iter 0
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb497390:0x7f96e0e0a8 duplicated action=find-dup, vdom=root, node=system.replacemsg.http.msg-type, key=[url-block]
      Can not add table entry, createTable,705: url-block table http iter 0
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb49f510:0x7f96e0a0a8 duplicated action=find-dup, vdom=root, node=system.replacemsg.alertmail.msg-type, key=[alertmail-virus]
      Can not add table entry, createTable,705: alertmail-virus table alertmail iter 0
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4a7510:0x7f96e060a8 duplicated action=find-dup, vdom=root, node=system.replacemsg.spam.msg-type, key=[ipblocklist]
      Can not add table entry, createTable,705: ipblocklist table spam iter 0
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4af690:0x7f96e020a8 duplicated action=find-dup, vdom=root, node=system.replacemsg.fortiguard-wf.msg-type, key=[ftgd-block]
      Can not add table entry, createTable,705: ftgd-block table fortiguard-wf iter 0
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4b7690:0x7f96dfe0a8 duplicated action=find-dup, vdom=root, node=system.replacemsg.auth.msg-type, key=[auth-disclaimer-page-1]
      Can not add table entry, createTable,705: auth-disclaimer-page-1 table auth iter 0
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4bf810:0x7f96dfa0a8 duplicated action=find-dup, vdom=root, node=system.replacemsg.sslvpn.msg-type, key=[sslvpn-login]
      Can not add table entry, createTable,705: sslvpn-login table sslvpn iter 0
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4c7820:0x7f96df60a8 duplicated action=find-dup, vdom=root, node=system.replacemsg.admin.msg-type, key=[pre_admin-disclaimer-text]
      Can not add table entry, createTable,705: pre_admin-disclaimer-text table admin iter 0
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4cf830:0x7f96df20a8 duplicated action=find-dup, vdom=root, node=system.replacemsg.nac-quar.msg-type, key=[nac-quar-virus]
      Can not add table entry, createTable,705: nac-quar-virus table nac-quar iter 0
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4d79d0:0x7f96dee0a8 duplicated action=find-dup, vdom=root, node=system.replacemsg.traffic-quota.msg-type, key=[per-ip-shaper-block]
      Can not add table entry, createTable,705: per-ip-shaper-block table traffic-quota iter 0
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4dfb70:0x7f96dea0a8 duplicated action=find-dup, vdom=root, node=system.replacemsg.utm.msg-type, key=[virus-html]
      Can not add table entry, createTable,705: virus-html table utm iter 0
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4e7d10:0x7f96de60a8 duplicated action=find-dup, vdom=root, node=system.replacemsg.automation.msg-type, key=[automation-email]
      Can not add table entry, createTable,705: automation-email table automation iter 0
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4e8120:0x7f96dde0f0 duplicated action=find-dup, vdom=root, node=system.accprofile.name, key=[super_admin]
      error at cmd_query_table_append (super_admin) 1192
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4e86b0:0x7f96dde1a8 duplicated action=find-dup, vdom=root, node=system.accprofile.name, key=[super_admin_readonly]
      error at cmd_query_table_append (super_admin_readonly) 1192
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4e8ae0:0x7f96dde260 duplicated action=find-dup, vdom=root, node=system.accprofile.name, key=[admin_no_access]
      error at cmd_query_table_append (admin_no_access) 1192
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4e8f10:0x7f96dde318 duplicated action=find-dup, vdom=root, node=system.accprofile.name, key=[prof_admin]
      error at cmd_query_table_append (prof_admin) 1192
      <pid-135 /bin/cmdbsvr> [__bsearch_index:459] entry 0xb4ead00:0x7f96dd606c duplicated action=find-dup, vdom=root, node=system.standalone-cluster.cluster-peer.sync-id, key=501, attr.size=4(sync-id)
      <pid-135 /bin/cmdbsvr> [__bsearch_index:459] entry 0xb4beed0:0x7f96dd2054 duplicated action=find-dup, vdom=root, node=waf.main-class.id, key=10000000, attr.size=4(id)
      <pid-135 /bin/cmdbsvr> [__bsearch_index:459] entry 0xb4bf400:0x7f96d1f054 duplicated action=find-dup, vdom=root, node=waf.signature.id, key=10000001, attr.size=4(id)
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4ed090:0x7f96d18098 duplicated action=find-dup, vdom=root, node=antivirus.filetype.name, key=[7z]
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4be8f0:0x7f96d110d8 duplicated action=find-dup, vdom=root, node=system.sso-admin.name, key=[fabric-admin]
      error at cmd_query_table_append (fabric-admin) 1340
      <pid-135 /bin/cmdbsvr> [__bsearch_index:433] entry 0xb4e9a70:0x7f96d11208 duplicated action=find-dup, vdom=root, node=system.sso-admin.name, key=[fabric-admin-readonly]
      error at cmd_query_table_append (fabric-admin-readonly) 1340
      Initialize config error 44010
      <pid-135 /bin/cmdbsvr> [__bsearch_index:459] entry 0xb9fce50:0x7f962d6054 duplicated action=find-dup, vdom=root, node=firewall.internet-service-reputation.id, key=1, attr.size=4(id)
      <pid-135 /bin/cmdbsvr> [__bsearch_index:459] entry 0xb9fce50:0x7f962d60e4 duplicated action=find-dup, vdom=root, node=firewall.internet-service-reputation.id, key=2, attr.size=4(id)
      <pid-135 /bin/cmdbsvr> [__bsearch_index:459] entry 0xb9fce50:0x7f962d6174 duplicated action=find-dup, vdom=root, node=firewall.internet-service-reputation.id, key=3, attr.size=4(id)
      <pid-135 /bin/cmdbsvr> [__bsearch_index:459] entry 0xb9fce50:0x7f962d6204 duplicated action=find-dup, vdom=root, node=firewall.internet-service-reputation.id, key=4, attr.size=4(id)
      <pid-135 /bin/cmdbsvr> [__bsearch_index:459] entry 0xb9fce50:0x7f962d6294 duplicated action=find-dup, vdom=root, node=firewall.internet-service-reputation.id, key=5, attr.size=4(id)
      The config file may contain errors.
      Please see details by the command 'diagnose debug config-error-log read'.

        Nelson2
        Nelson2
        New Member
        September 24, 2025

        Hi , I have de same problem how can you fixed ?

        Can you helpme to ?

        tim86
        tim86Author
        New Member
        August 19, 2024

        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!!

          jashkp16
          jashkp16
          New Member
          February 20, 2025

          Hey Brother I'm also facing same issue I've 60F.

          I copied the firmware and rename it with the "image.out". I have used 64 GB USB Drive with FAT32 format. But still not working. Can you help me.

            Jeremiah_Hahn
            Jeremiah_Hahn
            New Member
            August 20, 2024

            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.

              pkrstevski
              pkrstevski
              New Member
              September 2, 2025

              Hey, i have the same problem as you guys, tried with older firmware version, tried with newer version, but the device is stuck. Little intro, i did direct update from older version firmware 7.0 to the latest and now i am stuck. I can't access it via anything, tried console cable.. but nothing works. Any other ideas how to fix it?

                sw2090
                SuperUser
                sw2090
                SuperUser
                September 2, 2025

                well console will work even if there is no firmware (I had that several times after formatting boot device via the boot menue). If it doesn't then either your FGT is dead or something is wrong with your cable and/or serial settings.

                FGT per default do 9600 8-N-1 .

                 

                Also once you have a running config on a FGT a direct update is not recommended because that whould probably screw your config. Fortinet have a tool in the firmware download area in support portal that will give you an upgrade path which you should follow  to not screw your config.

                If you already screwed it you can always use the serial console to do a factory reset (exec factory-reset) and bring it back to the default config of the currently running firmware.

                  pkrstevski
                  pkrstevski
                  New Member
                  September 9, 2025

                  Definitly the console cable was the problem, i tried 5 different console cables from Fortinet and the 5th was working properly. Managed to boot from USB and now its fine. Thank you :)

                  Nelson2
                  Nelson2
                  New Member
                  September 24, 2025

                  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?

                   

                   

                  sw2090
                  SuperUser
                  sw2090
                  SuperUser
                  September 24, 2025

                  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.

                    tim86
                    tim86Author
                    New Member
                    October 3, 2025

                    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.

                    Terms & ConditionsAccessibility statement