FortiGate200B Will not boot.

[Keith42]

Hi Everyone, My first post and it' s a problem. Here is the console log of the affected unit just before it hangs.

 FortiGate-200B (14:12-11.05.2009)
 Ver:04000006
 Serial number:FG200B*********
 RAM activation
 Total RAM: 1024MB
 Enabling cache...Done.
 Scanning PCI bus...Done.
 Allocating PCI resources...Done.
 Enabling PCI resources...Done.
 Zeroing IRQ settings...Done.
 Verifying PIRQ tables...Done.
 Disabling local APIC...Done.
 Boot up, boot device capacity: 3824MB.
 Press any key to display configuration menu...
 ......
 ../src/device/usb2/usb.c: 342: usb_start_wait_urb status!=0(-32)
 
 ERROR: Bulk read CSW ret = -32
 ERROR: ll_read_block( 5e08, 37010000, 20081, 20) = -1
 ../src/device/usb2/usb.c: 342: usb_start_wait_urb status!=0(-32)
 
 ERROR:Bulk read data ret = -32
 ../src/device/usb2/usb.c: 342: usb_start_wait_urb status!=0(-32)
 

Does anyone know what is causing this error. The 3 USB ports are empty on the FG200B Thanks

[rwpatterson]

Welcome to the forums. I hope you had a backup made sometime recently.... Since the menu goes past the boot options, I would try a format/reload of the firmware the unit was running before it went south for the winter. If you' re feeling energetic, I would even run an interface test on the unit before the load to confirm everything is in order. It may help you sleep better at night. The link to the testing tools: http://emea.fortinet.net/fortinet/aht/index.php Scroll through the list and find the test firmware for your model. Load it, but just run, don' t set as the default code. Follow the instructions for cross wiring the ports. It takes a few minutes (depending on port count). When done, if everything looks good, upload the firmware, restore, and have a cold one. Hope this helps.

[Keith42]

Thanks for the reply. This is the second time this unit has failed to boot. The last time was Dec 2012. Fortinet Support instructed me to format and reflash which worked. Is there any way to know what is wrong with the unit or is the error message too vauge? I have a backup from 8 days ago so not too bad. I' ll only be missing 3 changes I made. I don' t know which test image I should use on the FG200B. FortiGate 200B FortiGate-200B_HQIP_1400.img FG200B39096xxxxxx and upper FGT_200B-HQIP.1.1.4.8002.OUT FGT_200B-HQIP.1.0.0.2005.OUT FGT_200B-HQIP.1.1.4.2061.OUT Any idea which I should use? Thanks Keith

[rwpatterson]

If your serial number doesn' t start with ' FG200B39096' or higher, then I would choose the newest of the remaining options.

[Keith42]

Thanks, I' ll give it a go on Monday.

[Keith42]

I ran the Advanced Hardware Test but don' t know what to make of it. It' s attached. I also formatted the unit and re-uploaded 4 MR3 Patch11 as default and backup os. I now get EXT3 errors. Anyone got any ideas on what to troubleshoot next?

 FortiGate-200B (14:12-11.05.2009)
 Ver:04000006
 Serial number:FG200B39**********
 RAM activation
 Total RAM: 1024MB
 Enabling cache...Done.
 Scanning PCI bus...Done.
 Allocating PCI resources...Done.
 Enabling PCI resources...Done.
 Zeroing IRQ settings...Done.
 Verifying PIRQ tables...Done.
 Disabling local APIC...Done.
 Boot up, boot device capacity: 3824MB.
 Press any key to display configuration menu...
 ..
 :  Get firmware image from TFTP server.
 :  Format boot device.
  B]:  Boot with backup firmware and set as default.
  I]:  Configuration and information.
 :  Quit menu and continue to boot with default firmware.
 :  Display this list of options.
 
 Enter Selection :b
 
 Loading backup firmware from boot device...
 
 Reading boot image 1315258 bytes.
 Initializing firewall...
 System is started.
 
 
 RTR-FG200B-DUB01 login: EXT3-fs error (device sd(8,3)): ext3_readdir: bad entry in directory #342049: directory entry across blocks - offset=968, inode=31209, rec_len=4140, name_len=34
 EXT3-fs error (device sd(8,3)): ext3_free_blocks: bit already cleared for block 626583
 EXT3-fs error (device sd(8,3)): ext3_free_branches: Read failure, inode=309528, block=-62063595
 EXT3-fs error (device sd(8,3)): ext3_free_blocks: Freeing blocks not in datazone - block = 252313870, count = 1
 EXT3-fs error (device sd(8,3)): ext3_free_blocks: Freeing blocks not in datazone - block = 67511041, count = 1
 *EXT3-fs error (device sd(8,3)): ext3_free_blocks: Freeing blocks not in datazone - block = 18713235, count = 1
 EXT3-fs error (device sd(8,3)): ext3_free_blocks: Freeing blocks not in datazone - block = 1917259070, count = 1
 EXT3-fs error (device sd(8,3)): ext3_free_blocks: Freeing blocks not in datazone - block = 1601205615, count = 1
 EXT3-fs error (device sd(8,3)): ext3_free_blocks: Freeing blocks not in datazone - block = 1718579792, count = 1
 

[Dave_Hall]

I now get EXT3 errors. Anyone got any ideas on what to troubleshoot next?

Based on the history of the unit, I would say RMA.

[Keith42]

I' m waiting on FortiNet support to get back to me on this. Is the boot device an SD or CF card inside the device?

[Keith42]

Fortinet have RMA' ed the unit. They believe that the CF card is faulty.

[Dave_Hall]

They believe that the CF card is faulty.

The 200B is nice IMHO but out of a batch of may be 20 I had to RMA about 4-5 of them over the course of two years due to CF related issues.