Skip to main content
billysanson
New Member
August 24, 2013
Question

Log disk failure is imminent

  • August 24, 2013
  • 3 replies
  • 6660 views
Log disk failure is imminent <-- I am getting this alert message on a FortiGate 300C. Following the instructions at http://kb.fortinet.com/kb/microsites/microsite.do?cmd=displayKC&externalId=FD31881 gives me the following results FG300C3912601113 # get sys stat Version: FortiGate-300C v5.0,build0208,130603 (GA Patch 3) Virus-DB: 19.00070(2013-08-23 07:22) Extended DB: 19.00028(2013-08-13 07:21) IPS-DB: 4.00383(2013-08-21 23:48) IPS-ETDB: 0.00000(2000-00-00 00:00) Serial-Number: FG300C3912601113 Botnet DB: 1.00209(2013-08-12 11:39) BIOS version: 04000019 System Part-Number: P09616-04 Log hard disk: Available Hostname: FG300C3912601113 Operation Mode: NAT Current virtual domain: root Max number of virtual domains: 10 Virtual domains status: 1 in NAT mode, 0 in TP mode Virtual domain configuration: disable FIPS-CC mode: disable Current HA mode: standalone Branch point: 208 Release Version Information: GA Patch 3 System time: Sat Aug 24 07:20:54 2013 FG300C3912601113 # diagnose sys logdisk smart This feature is available only for ASM-S08 HDD module. FG300C3912601113 # diagnose sys logdisk status This feature is available only for ASM-S08 HDD module. FG300C3912601113 # diagnose sys logdisk test This feature is available only for ASM-S08 HDD module. should I try for a low level format of the disk? or should I RMA this already? Thanks.

    3 replies

    Dave_Hall
    New Member
    August 24, 2013
    should I try for a low level format of the disk? or should I RMA this already?
    Most likely support is going ask you to format the boot device and/or log device, either before or after running the HQIP test.
    TheJaeene
    New Member
    August 26, 2013
    I had these log entries on several Boxes running 5.0.3 ... After uprgading to 5.0.4 the Disk repaired itself
    RH2
    New Member
    August 28, 2013
    It was a bug in 5.0.3 my vm64 was generating a log disk failure, but none of my 100Ds were doing it. Support said it was a bug. Stopped with 5.0.4