Skip to main content
ergotherego
ergotherego
New Member
April 5, 2019
Question

CLI hangs when entering VDOM - WebUI won't load at all

  • April 5, 2019
  • 1 reply
  • 2586 views

200D HA cluster running 5.6.5. Traffic is passing fine, first noticed issue when FMG wouldn't push changes down. Get into CLI and its fine while in global mode, but once you try to enter a VDOM the CLI just hangs.

 

WebUI lets you login and get past all the prompts, but then won't load the page.

 

CPU is 100% idle, memory usage is 45%.

 

Anyone have any ideas?

    1 reply

    ergotherego
    ergotheregoAuthor
    New Member
    April 5, 2019

    Looks like its due to disk errors. Was able to find some events in FAZ for it:

     

    date=2019-04-05 time=05:43:10 bid=737436011 dvid=1035 itime=1554464594 logver=56 logid="0100020010" type="event" subtype="system" level="critical" msg="EXT2-fs error (device sd(8,1)): ext2_read_inode: unable to read inode block - inode=22530, block=90115" logdesc="Kernel error" eventtime=1554464590 devid="FG200D39xxxxxxxx" vd="root" devname="firewall-01"
    date=2019-04-05 time=03:36:56 bid=737358370 dvid=1035 itime=1554457019 logver=56 logid="0100020010" type="event" subtype="system" level="critical" msg="EXT2-fs error (device sd(8,1)): ext2_read_inode: unable to read inode block - inode=22530, block=90115" logdesc="Kernel error" eventtime=1554457016 devid="FG200D39xxxxxxxx" vd="root" devname="firewall-01"
    date=2019-04-05 time=03:16:56 bid=737346183 dvid=1035 itime=1554455819 logver=56 logid="0100020010" type="event" subtype="system" level="critical" msg="EXT2-fs error (device sd(8,1)): ext2_read_inode: unable to read inode block - inode=22530, block=90115" logdesc="Kernel error" eventtime=1554455816 devid="FG200D39xxxxxxxx" vd="root" devname="firewall-01"

    Terms & ConditionsAccessibility statement