Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
hogust
New Contributor

fotimail-100c boot error

device is not pinging. here is text from com port: FortiMail-100C (17:04-07.08.2011) Ver:04000006 Serial number:FE100C3911000226 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( 58a8, 37c08000, 6041, 10) = -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) ERROR: Bulk read CSW ret = -32 ERROR: ll_read_block( 58a8, 37c0a000, 6051, 10) = -1
11
11
3 REPLIES 3
emnoc
Esteemed Contributor III

Do you have support contracts services? You might need to get the HQIP image and reformat the unit after running it. It might be a hardware failure on the FML100C What version of FML where you running ?

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
hogust
New Contributor

support contract has expired . fml version is 4.0 mr3. how can i get hqip image (what does it mean, by the way) if device does not boot?
11
11
Istvan_Takacs_FTNT

Create an account for yourself at https://support.fortinet.com/ where you can get access to the HPIQ firmwares. They are used to debug hardware-related issues on the appliance and usually the support engineer asks you to use one. More info here: http://kb.fortinet.com/kb/documentLink.do?externalID=FD34745 Once you have the account, the firmware can be downloaded from https://support.fortinet.com/Download/HQIPImages.aspx You still need to have a valid support contract to do anything with the detected issue, though. BTW, those errors appear to be coming from the USB device that has nothing to do with the network interface. Do you have ping enabled on the specific port?
Labels
Top Kudoed Authors