Unable to boot up

[franchino87]

Hi there, i got a problem with a Fortinet FortiGate 60C.

I saved my configuration and after that i restarted the fortigate, using the console port (and putty with an opened COM connection) i managed to format the boot.

After that i'm unable to connect to a TFTP server because it seems that NO port are working (WAN1, WAN2, DMZ, 1to5)

Now i'm unable to boot and unable to connect to a TFTP server to flash the firmware again.

Is there any solution?

Thanks

[rwpatterson]

Are you sure it's the ports and not the network? Internal should work right out of the box. Internal split into individual ports (internal1, internal2...internalx) are not created until after the config is loaded into memory and executed.

A few things to check:

 What's the brand/manufacturer of the TFTP server?

 Is the cable straight through or cross?

 What's the next device in line?

[franchino87]

Thanks all for the reply, the only way i can connect is through the Ethernet Console Cable with Putty

This is what the Fortigate show me on boot

FortiGate-60C (16:24-09.28.2011)
Ver:04000026
Serial number: FGT60C3G11035927
CPU(00): 525MHz
Total RAM: 512MB
Initializing boot device...
Initializing MAC... nplite#0
Press any key to display configuration menu...

ver tag :ffffffff
wrong OS: ff
Boot failed. Please check boot device or OS image ...
 Please power cycle. System halted.

rwpatterson wrote:

Are you sure it's the ports and not the network? Internal should work right out of the box. Internal split into individual ports (internal1, internal2...internalx) are not created until after the config is loaded into memory and executed.

A few things to check:

 What's the brand/manufacturer of the TFTP server?

 Is the cable straight through or cross?

 What's the next device in line?

I'm sure that is not the network, i was directly connected to the Fortigate without anything in the middle.

I tried every port (LAN, WAN, Console) but i'm unable to Ping the device because, once i connected the ethernet cable, it appears that there is no network (like the cable isn't connected)

I'm using TFTPD64 (tftp server was working correctly after boot format)

I'm using a straight cable.

No other device in line (directly connected).

allwinmasc wrote:

are you following step 2 from the doc:  2 - Connect the computer running the TFTP server to the FortiGate unit. Use the table below to determine which port to connect to.

 FortiGate Model                                Interface  ============================================================= 50, 50A, 100, 200, 300, 500, 800, 800F          Internal  50B, all 60 models, 100A, 200A                  Internal port 1 100A, 200A (If Internal Port1 does not work)    Internal port 4  300A, 310A, 400, 400A, 500A, 1000 and higher    LAN port 1  1240B                                           port40 Fortigate with a dedicated management port      mgmt1

Your issue sounds like you missed it.

I've tried every port available, even tried to select the various port through the option available on BOOT without luck (Set image download port)

Joshua.MJ wrote:

Can you access the fortigate via console cable?

I can't access console via USB Management (with a "printer USB" cable like)

I can access the "starting" console through Ethernet Console port using Putty

[rwpatterson · Accepted solution]

Until the OS is loaded, you will not be able to PING the interface. Just try to TFTP the software up from the internal port number one.

FortiGate-60C (16:24-09.28.2011)
Ver:04000026
Serial number: FGT60C3G11035927
CPU(00): 525MHz
Total RAM: 512MB
Initializing boot device...
Initializing MAC... nplite#0
Press any key to display configuration menu...  <- at this line here

ver tag :ffffffff
wrong OS: ff
Boot failed. Please check boot device or OS image ...
 Please power cycle. System halted.

On the line designated by "at this line here", you have 5 seconds to hit a key to enter the configuration utility. Once in there, you select TFTP firmware. At this point, choose the TFTP options and watch the hashes "#####" grow until the firmware is loaded.

[franchino87]

rwpatterson wrote:

Until the OS is loaded, you will not be able to PING the interface. Just try to TFTP the software up from the internal port number one.

Hi rwpatterson, thanks for your reply.

I set the image download port to LAN port 1to5, but the main problem is that it seems that my ethernet isn't connected at all

If i go on windows connection manager it shows that the network is disconnected even if i connected my pc to LAN port 1

Same behaviour on every other port (they were working before boot format)

**** EDIT *** 

IT WORKED! THANK YOU!!! love u men :)

[rwpatterson]

Great to hear. Enjoy.

[postmasternca]

franchino87 wrote:

**** EDIT *** 

IT WORKED! THANK YOU!!! love u men :)

Could you explain how you managed to do it ?

I'm in the exact same case but with a FG 40C.

Thanks

[franchino87]

i haven't a perfect recall of the procedure i followed, though i can tell you that i used the Port 1 and i managed to let the TFTP server to work, even if it seems that the network is disconnected the Fortigate could reach the TFTP server and download the image.

could u explain a little better what happen to you so maybe we can help

[postmasternca]

It seems the NAND memory has bad blocks. I was able to load firmware v5.2.6 by TFTP and after the reboot my 40C showed errors related to the shared data :

Please connect TFTP server to Ethernet port '5'.

Enter TFTP server address [192.168.1.168]:
Enter local address [192.168.1.188]:
Enter firmware image file name [image.out]:
MAC: 00:09:0f:4a:30:92

Connect to tftp server 192.168.1.168 ...

#####################################################
Image Received.
Checking image... OK
Save as Default firmware/Backup firmware/Run image without saving:[D/B/R]?D

Programming the boot device now.
.................................................................
Reading boot image... 1086553 bytes.
Initializing firewall...

System is starting...
Starting system maintenance...
Scanning /dev/sda1... (100%)
Formatting shared data partition ... done!
Cannot mount shared data partition.
[fs.c:896] Read from MBR of boot device '/dev/sda' failed.
EXT2-fs error (device sd(8,1)): ext2_read_inode: unable to read inode block - in
ode=17, block=263
Failed to save PRNG state
Using default data disk /dev/hda: platform 40 version 1
fgtag.c - 139: Failed to open device: /dev/hda
Abort booting!
EXT2-fs error (device sd(8,1)): read_inode_bitmap: Cannot read inode bitmap - bl
ock_group = 0, inode_bitmap = 260
unzip dict file ERROR!
__read_country_map, Open dict file ERROR!
Failed to rea
__get_backdoor_timeout: Couldn't get shm
__set_backdoor_timeoEXT2-fs error (device sd(8,1)): read_inode_bitmap: Cannot re
ad inode bitmap - block_group = 0, inode_bitmap = 260
ut: Couldn't get shm
[others.c:2390] get_ttree('root') failed
[others.c:2390] get_ttree('root') failed
[others.c:2390] get_ttree('root') failed

 login: open libips.so error:/data/lib/libips.so: cannot open shared object file
: No such file or directory
fcron_set_mgmt_vdom()-124: mgmt vd=-1 is not created yet
fcron_set_mgmt_vdom()-124: mgmt vd=-1 is not created yet
unzip dict file ERROR!
__read_country_map, Open dict file ERROR!
Failed to read ip country-map
__init_ip_country_dict, geoip_get_country_map return error
...

And it keeps showings errors reading files...

I followed the procedure mentioned here meant for 60C but the NAND scan program is not implemented on the 40C when I press the "n" key:

Enter G,F,I,B,Q,or H:

:  Get firmware image from TFTP server.
:  Format boot device.
:  Configuration and information.
:  Boot with backup firmware and set as default.
:  Quit menu and continue to boot.
:  Display this list of options.

Enter G,F,I,B,Q,or H:

:  Normal POST test.
:  Quit this menu.
Unknown command 'nand' - try 'help'
NAND scan failed. Try to reboot.

Is there anything else I can try ?

Thanks for your help

[rwpatterson]

Have you tried formatting the flash first?