ZyWALL USG 100 won't boot through

ICENo34
ICENo34 Posts: 3
First Comment
edited April 2021 in Security
Hello everyone,

I've been expiriencing an issue with my ZyWALL USG 100 since a while.
Out of nowere it no longer worked properly, so I unplugged the power, waited 2 minutes and plugged the power back in. 

This didn't resolve the issue and the device won't start up.

The SYS LED just keeps blinking green for hours on end.
I tried replacing the power adapter already with a new one, but this didn't help.
(We've had this issue where, if the device had a faulty power adapter it didnt get enough power to boot up)

Can anyone assist me into fixing the issue?

Kind regards,

Jaime

All Replies

  • Zyxel_Charlie
    Zyxel_Charlie Posts: 1,034  Zyxel Employee
    First Anniversary Friend Collector First Answer First Comment
    @ICENo34
    Regarding to this case,
    can you do firmware recovery with latest firmware via console?
    Here is SOP.
    Guide
    Charlie
  • ICENo34
    ICENo34 Posts: 3
    First Comment
    Hi Charlie,

    Thank you for your support in this matter.
    I've tried to do the firmware recovery as provided. 

    After entering the 'atuk' command I receive the following error:
    Starting XMODEM upload (CRC mode)....
    CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
    Product model id is not compatible!!
    This product's model id is 1500
    The kernel image supports the following product model id :


    ERROR

  • ICENo34
    ICENo34 Posts: 3
    First Comment
    Small update: 
    I was able to get it going for a hour or so.
    What I did was still do the following steps after the ATUK command.

    I was able to upload firmware, it rebooted. Got a webinterface.
    I then reset to factory settings again. Rebooted. Still worked.
    After turning it off- and on again for several times it seemed to be back to life.

    Configured the USG100, placed it behind the modem (which is in Bridge Mode) and voila. Worked.
    Then went to the movies, came home, to find I had no internet. Quick search found out the SYS led was blinking again and the USG stopped responding again.

    I think it's soon time to replace the device for a newer series.
  • Zyxel_Charlie
    Zyxel_Charlie Posts: 1,034  Zyxel Employee
    First Anniversary Friend Collector First Answer First Comment
    @ICENo34
    Regarding to your description,
    in order to provide you with a better assistance, we will contact you through private message to get purchase information, and you can contact the local representative to proceed with RMA process.
    Charlie
  • Tortax
    Tortax Posts: 2
    Friend Collector First Comment
    edited October 2020
    @ICENo34
    Regarding to this case,
    can you do firmware recovery with latest firmware via console?
    Here is SOP.
    Guide
    Charlie

    Hello,

    I got a similar problem.
    What is this "atuk" command, the link is dead?

    I tried recovering firmware for "USG 100" with "atkz -u" and "atkz -f -l" and uploaded 330AQQ7C0.bin.
    But I'm still not able to get a solid sys led.

    I do get a DRAM error from time to time => DRAM POST: Testing:  98304K
    DRAM Test Fail at address 06061000. (read:ffff43a7, should:ffffffff)


    ****************************************
    FLASH: AMD 16M              

    BootModule Version: V1.11 | 08/14/2008 14:15:22                                               
    DRAM: Size = 256 Mbytes                       

    DRAM POST: Testing: 262144K                           
    DRAM Test SUCCESS !                   

    Kernel Version: V2.4.27 | 2015-01-08 20:37:07                                             
    ZLD Version: V3.30(AQQ.7) | 2015-01-13 16:30:24                                               

    Press any key to enter debug mode within 3 seconds.                             
    .............................................................

    Start to check file system...
    /dev/hda2: 28/18216 files (0.0% non-contiguous), 56466/72704 blocks
    /dev/hda3: 123/43296 files (10.6% non-contiguous), 47013/173056 blocks
    Done

    INIT: version 2.86 booting
    Setting the System Clock using the Hardware Clock as reference...System Clock se
    t. Local time: Mon Oct 26 16:20:14 UTC 2020

    INIT: Entering runlevel: 3
    Starting zylog daemon: zylogd zylog starts.
    Starting syslog-ng.
    Starting ZLD Wrapper Daemon....
    Starting uam daemon.
    Starting App. Patrol Daemon.
    Starting myzyxel daemon.
    Starting periodic command scheduler: cron.
    Start ZyWALL system daemon....
    Check signature package

    ...................................
    Got LINK_CHANGE
    Port [0] Copper is up --> Group [0] is up
    .......................



Security Highlight