Skip to main content
A
Anonymous_User
Contributor
January 8, 2009
Question

Fortigate 100 won' t boot v3.00

  • January 8, 2009
  • 6 replies
  • 4389 views
Hi, I am trying to upgrade my Fortigate 100 to v3.00 firmware. I tried many different builds of the firmware, but the device will not boot v3.00. On the other hand, v2.80 works fine. Here are some examples of the errors: Build 0733 (MR7 Patch 2): Reading boot image 1034767 bytes. Initializing firewall... System is started. Abort booting! unknown operation mode(0) @@@@ nsm_mcast.c:nsm_mcast_init(line 135) sock 14 VR (null) vdom_id -1 ret -1 er rno 2 PIM-SM: NSM service is not sufficient PIM-SM: IPV4 MRIB service service not available PIM-SM: IPV4 MRIB PIM service service not available PIM-DM: [NSM] Recv Service: Services are not sufficient PIM-DM: [NSM] Recv Service: IPV4 MRIB service service not available PIM-DM: [NSM] Recv Service: IPV4 MRIB PIM service service not available The system is going down NOW !! Build 0726 (MR7): Reading boot image 1034621 bytes. Initializing firewall... System is started. Failed to save PRNG state. init_nids_db: ips_so_open failed, ret=1 Initialize config error 200 failed to change to (/data/./config/) Error generating self-signed certificate Error generating self-signed certificate Error generating self-signed certificate unknown operation mode(0) The system is going down NOW !! Build 0673 (MR6 Patch 4): Reading boot image 1024516 bytes. Initializing firewall... System is started. init_nids_db: ips_so_open failed, ret=1 Initialize config error 200 failed to change to (/data/./config/) unknown operation mode(0) The system is going down NOW !! Here is the device hardware information: OS image name : flatkc vendor_id : GenuineIntel cpu family : 6 model : 8 model name : Celeron (Coppermine) stepping : 10 cpu MHz : 300.651 cache size : 128 KB memory : SDRAM 256MB 100MHz IDE device channel 0 drive 0: Model Number: SanDisk SDCFJ-64 Serial Number: 003519K2204X5058 Firmware Revision: HDX 2.15 device size with M = 1024*1024: 61 MBytes DMA: mdma0 mdma1 *mdma2 Cycle time: min=120ns recommended=120ns PIO modes: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns IDE device channel 0 drive 1: No device IDE device channel 1 drive 0: No device IDE device channel 1 drive 1: No device Hardware Monitor Information: CPU1_temp: 0.000 temperature1: 0.000 Any ideas? Thanks.

    6 replies

    Carl_Wallmark
    Carl_Wallmark
    New Member
    January 8, 2009
    Hi, Try to boot your FG and load the start menu using a console cable, format the internal disk, and then load a new firmware using TFTP.
    A
    Anonymous_UserAuthor
    Contributor
    January 8, 2009
    Thanks. I think that is basically what I did already. I tried the " Format boot device" option somewhere in the midst of trying different firmware versions, but it didn' t make any difference as far as I can tell. (If there is another internal disk that I should be formatting, I haven' t found that option.)
    Carl_Wallmark
    Carl_Wallmark
    New Member
    January 9, 2009
    strange... if i where you i would open a support ticet with fortinet.
    A
    Anonymous_UserAuthor
    Contributor
    January 9, 2009
    Okay, thanks. I haven' t purchased a support contract for this unit since I only use it for occasional configuration testing. But it' s hard to test anything if the unit doesn' t boot.
    abelio
    SuperUser
    abelio
    SuperUser
    January 9, 2009
    Hi, little question: how do post the output if diagnose hardware deviceinfo command if the unit cannot boot? did you save it in another opportunity? Commands that Selective suggested involves the procedure detailed in article http://kc.forticare.com/default.asp?id=338 and run also the comand ' execute formatlogdisk' for better perfomance. regards
    A
    Anonymous_UserAuthor
    Contributor
    January 9, 2009
    Hi Abel, When I restart the unit and " press any key to display configuration menu," one of the options is " Configuration and information" which then provides an option to display the hardware information. The command " execute formatlogdisk" just gives an error saying the log disk is not available. The procedure you linked matches what I did in my previous attempts to install v3.0 firmware, except that I did not always format the boot device. Now the good news: I decided to give it one more shot, using the " format boot device" option and then immediately attempting to install the latest build (0733). This time it worked, and the unit is booting properly now. Go figure! Thanks.
    iFortify
    iFortify
    New Member
    January 17, 2009
    Hardware Troubleshooting http://emea.fortinet.net/fortinet/
    Terms & ConditionsAccessibility statement