ZyWALL USG 200 booting issues

Options
einaren
einaren Posts: 4
Friend Collector First Comment
in Security

Not able to boot my USG 200, I bought this second hand and tried to reset the device when I lost coms to it.

Now I get the following when booting up:

FLASH: AMD 16M
CF read: device 0 not ready
IDENT command error: 0xf0

IDENT command error: 0xf0

ERROR

BootModule Version: V1.12 | 11/17/2009 18:05:22
DRAM: Size = 256 Mbytes

Kernel Version:
ZLD Version:
IDENT command error: 0xf0

ERROR

Press any key to enter debug mode within 1 seconds.
.....................
Enter Debug Mode

USG 200>
USG 200> atcd 2
ERROR

USG 200> atcd 1
ERROR

USG 200>
USG 200> ?
ERROR

USG 200>
CF device is busy...

FLASH: AMD 16M
CF read: device 0 not ready
IDENT command error: 0xf0

IDENT command error: 0xf0

ERROR

BootModule Version: V1.12 | 11/17/2009 18:05:22
DRAM: Size = 256 Mbytes

Kernel Version:
ZLD Version:
IDENT command error: 0xf0

ERROR

Press any key to enter debug mode within 1 seconds.
.....................
Device Not Ready
Device Not Ready
Formatted fail

IDENT command error: 0xf0

ERROR
J CF device is busy...

FLASH: AMD 16M
CF read: device 0 not ready
IDENT command error: 0xf0

IDENT command error: 0xf0

ERROR

BootModule Version: V1.12 | 11/17/2009 18:05:22
DRAM: Size = 256 Mbytes

Kernel Version:
ZLD Version:
IDENT command error: 0xf0

ERROR

Press any key to enter debug mode within 1 seconds.
.....................
Device Not Ready
Device Not Ready
Formatted fail

IDENT command error: 0xf0

ERROR
IDENT command error: 0xf0

errno = ff
ERROR
Now booting kernel in FLASH
IDENT command error: 0xf0

ERROR

Linux/PPC load: console=ttyS0,115200 root=/dev/ram init=zyinit ""
Uncompressing Linux...done.
Now booting the kernel
mount: /dev/hda3 is not a valid block device
mount: /dev/hda3 is not a valid block device
mount: /dev/hda3 is not a valid block device
mount: /dev/hda3 is not a valid block device
mount: /dev/hda3 is not a valid block device
Check partition table error: 1
Recovering Partition ...
Check partition table error: 1
Check partition table error: 1
Check partition table error: 1
Check partition table error: 1

The message; "Check partition table error: 1" continues indefenetly while power on.

What can I do with this?

All Replies

  • Zyxel_Emily
    Zyxel_Emily Posts: 1,298  Zyxel Employee
    First Anniversary 10 Comments Friend Collector First Answer
    edited February 19
    Options

    Hi @einaren,

    You can try if it is working after firmware recovery. After you enter debug mode, enter "atkz –f –l 192.168.1.1" to configure FTP server IP address and "atgo" to bring up the FTP server on port 1. Then upload the latest firmware version 330AQU7ITS-WK48-r74988 to ZyWALL USG 200 via FTP.

    You can find the details in "Appendix 3. Firmware Recovery" in the release note 330AQU7C0.pdf.

    330AQU7C0.pdf

  • smb_corp_user
    smb_corp_user Posts: 161  Master Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options

    Very good. When I started reading the issue description, I thought this was going to be a case of defective and unrepairable storage device. Good to see that it is a known issue with a known solution.

  • einaren
    einaren Posts: 4
    Friend Collector First Comment
    Options
    https://community.zyxel.com/en/discussion/comment/62094#Comment_62094

    Hi.


    Thanks for the quick reply on this.

    I tried as described above and also followed the provedure given.

    After entering the command "atkz -f -l 192.168.1.1" i run the "atgo" command it starts to boot up. I still get the continues message of "Check partition table error: 1"

    I set up a computer with static IP 192.168.1.55 / 24, tried to connect with the bulit in ftp in Windows, but not able to connect to the FW. I've tried to ping the 192.168.1.1 with no reply.
    I have also tried to connect using WinSCP ftp with same results.

    Any ideas to this? Something else I can try?

    Einar

  • smb_corp_user
    smb_corp_user Posts: 161  Master Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options

    Not sure if this makes any difference, but maybe you could try the serial Console port (DB9) and see if the commands issued via the terminal command line (and the responses) behave any differently.

  • einaren
    einaren Posts: 4
    Friend Collector First Comment
    Options
    https://community.zyxel.com/en/discussion/comment/62236#Comment_62236

    Hi.

    Yes that is what I am currently using, only way I can communicate with it, as far as I know in current status.

    It is also probably worth mentioning that I had coms with the FW before hitting the reset button. So it seems like something failed during reset of device.

  • smb_corp_user
    smb_corp_user Posts: 161  Master Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options

    Unless another attempt at firmware recovery or reset procedure can make a difference, I would be inclined to think that there is a chance some actual storage device failure has happened.

  • einaren
    einaren Posts: 4
    Friend Collector First Comment
    Options

    Can I use the XMODEM fuction to upload the firmware, or is that for something else?

  • smb_corp_user
    smb_corp_user Posts: 161  Master Member
    First Anniversary 10 Comments Friend Collector First Answer
    Options

    Good question, I don't know. I defer to the ZyXEL team members for an authoritative answer.

  • Zyxel_Emily
    Zyxel_Emily Posts: 1,298  Zyxel Employee
    First Anniversary 10 Comments Friend Collector First Answer
    Options

    Hi @einaren,

    ZyWALL USG 200 is EOL several years ago. If firmware recovery is still not working, we're afraid that it might be hardware issue.

Categories

Security Highlight


Read more

Security Help Center

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