USG20W-VPN FSCK message

Kevin_Objsys
Kevin_Objsys Posts: 7  Freshman Member
First Comment
in Security

When rebooting our USG20W-VPN router via the console port, I noticed this message:

/dev/mmcblk0p7: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)

I already used the reset button on the router and then reapplied a saved config file. The above error was still reported.

How can I get rid of the above error?

All Replies

  • Zyxel_Melen
    Zyxel_Melen Posts: 2,595  Zyxel Employee
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate

    Hi @Kevin_Objsys,

    What happened when this log was printed? Are you able to record the logs when rebooting so we can check?

    Zyxel Melen


  • Kevin_Objsys
    Kevin_Objsys Posts: 7  Freshman Member
    First Comment

    Attached is the output showing the reboot command and what followed. We've had some intermittent trouble with traffic not going in or out through the WAN. I am not sure the problem lies with the Zyxel, but I noticed this message about the file system inconsistency while rebooting and wanted to look into it.

    reboot.txt

  • Zyxel_Melen
    Zyxel_Melen Posts: 2,595  Zyxel Employee
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate

    Hi @Kevin_Objsys,

    We recommand you follow the steps below to recover it first:

    1. Please backup your configuration.
    2. Please reset the USG20w-VPN to factory default.
    3. Please reference this FAQ to recover the db.
      https://community.zyxel.com/en/discussion/2632/how-to-recovery-database-when-it-is-broken
    4. Restore the original configuration.

    Hope it helps.

    Zyxel Melen


  • Kevin_Objsys
    Kevin_Objsys Posts: 7  Freshman Member
    First Comment

    First, note that the error I am seeing during boot up is not the same error that is mentioned in the FAQ you referenced and also my device does boot up despite the error. But, beyond that, the instructions tell me to FTP some *.db file to the router - where does that file come from?

  • Zyxel_Melen
    Zyxel_Melen Posts: 2,595  Zyxel Employee
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate

    Hi @Kevin_Objsys,

    Thanks for letting me know your concerns. After checking, please take these actions first:

    (1) Plug-in power cable and enter debug mode.

    gcrs2bv0e7yy.png

    (2) Enter at command:

    1. atkz -d
    2. atgo

    Zyxel Melen


  • Kevin_Objsys
    Kevin_Objsys Posts: 7  Freshman Member
    First Comment

    What will those commands do? Do they make any changes to the firewall, or are they purely diagnostic?

  • Zyxel_Melen
    Zyxel_Melen Posts: 2,595  Zyxel Employee
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate

    Hi @Kevin_Objsys,

    The command atkz -d is to print more information when booting, and atgo is to reboot the firewall.

    Zyxel Melen


  • Kevin_Objsys
    Kevin_Objsys Posts: 7  Freshman Member
    First Comment
    edited November 22

    Here is the log from rebooting with the commands given. I've scrubbed potentially sensitive stuff from the log (user names, IP addresses, passwords, some address object definitions)

    <file downloaded by Melen and removed for privacy reason>

  • Kevin_Objsys
    Kevin_Objsys Posts: 7  Freshman Member
    First Comment

    Oh, and the message about file system inconsistency and running FSCK is gone now. Along the way, I updated to the latest firmware (Nov 16 just came out) and I followed your instructions for atkz and atgo twice, because the first time I failed to capture the log. So, I'm not sure what resolved the issue, but it appears to be resolved!

Categories

Security Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）