How to restore my Zywall 110

Jarno_Smits

Good morning,

I got a Zywall 110 with old firmware, it was running on verion 4.15 on paritition 2 
and in the standby paritition 1  was version 4.10.

My bad i didn't read the warning notes, and I upgraded in the UI the zywall  to 4.71...
I uploaded version 4.71 into paritition 1 and rebooted the zywall

Now the Zywall dont startup anymore, the sysled stays blinking.

I was posible  with the serial interface to got the zywall working again by using the "atcd 2" command that it startup again with release 4.10 from paritition 2

because i later know that i needed to use firmware 4.20 first to upgrade into steps to 4.71 , i uploaded now version 4.20 into paritition 2 ( with 4.15 ) and i rebooted the zywall.

But now the zywall is also stuck with a blinking sysled, and also with the serial cable it isn't posible anymore to switch the parititions, i get strange error messages when i want to boot now from paritition 1 or 2 , see the logs below:

BootModule Version: V1.08 | 08/15/2013 10:45:46

DRAM: Size = 1024 Mbytes

Press any key to enter debug mode within 3 seconds.

............................

Enter Debug Mode

ZyWALL 110> atcd 1

Change Boot Number=1

ZyWALL 110> atgod

Booting...

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

Error trying to mount db partition 5 times

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

Could not write 8 blocks in inode table starting at 81923: Attempt to write block from filesystem resulted in short write

mount: wrong fs type, bad option, bad superblock on /dev/sda6,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda3,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

Connect a computer to port 1 and FTP to 192.168.1.1 to upload the new file.


And when i want to boot from Paritition 2 where version 4.20 is in now:

BootModule Version: V1.08 | 08/15/2013 10:45:46

DRAM: Size = 1024 Mbytes

Press any key to enter debug mode within 3 seconds.

.............................................................

EHCI timed out on TD - token=0x800d8d80, td=c00cc7a0, timeout=5000, pipe=0xc8008383

EHCI timed out on TD - token=0x80008d80, td=c00cc7e0, timeout=1000, pipe=0x88000303

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

Error trying to mount db partition 5 times

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

Could not write 8 blocks in inode table starting at 81923: Attempt to write block from filesystem resulted in short write

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda3,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda6,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

Connect a computer to port 1 and FTP to 192.168.1.1 to upload the new file.

I also tried to upload with FTP new firmware into the zywall , but when uploading with FTP, i got a message that the transfer is succeded, in the FTP console, but on the serial console i got a message that the firmware format isn't correct.

( i used the bin command in the FTP program to change to the correct format ) 


for the info, the version 4.20 i used is: 420AAAA2C0.bin
and the release 4.71 i used first is release: 471AAAA0C0.bin

im out of options now, can someone help me to restore the zywall 110 or is it bricked?

kind regards,

Jarno Smits

PeterUK

hold the reset in for 20 seconds as its on  4.71 firmware should work

osake_li_09

When you upload firmware .bin file via FTP, did you disable the Windows defender firewall or another firewall software? You may disable it and try again.

Jarno_Smits

good morning,

i tried already the 20 second reset procedure, but without any success..

Also i disabled the firewall from the pc, one time i got the message that the file transfer with version 4.20 is succeeded, but after the reboot i still get the same messages, after every reboot:

Could not write 8 blocks in inode table starting at 81923: Attempt to write block from filesystem resulted in short write

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

I also tried to boot from a different image with the atcd 0 atcd 1 and atcd 2 command, but still the same.

Only thing i can try is to upload a older version back example version 4.10 of 4.15, but i can't find these on the download page, can someone send me these files? 

Or does someone have a other step by step guide, maybe i'm exacuting wrong steps? 

Kind regards,

Jarno

PeterUK

I have uploaded "ZyWALL 110_4.10(AAAA.0)C0.zip" here:
https://ufile.io/js1dx7zt

Jarno_Smits

PeterUK said:

I have uploaded "ZyWALL 110_4.10(AAAA.0)C0.zip" here:
https://ufile.io/js1dx7zt

Hello Peter, 

Thank you for the 4.10 firmware, i tried to upload it into the zywall, but still after the reboot i got the same error messages.

I'm not sure what is the right procedure now.

The steps i did to upload the firmware:

- first i selected a image with command atcd 1 ( for image 1)
- rebooted the device with command atog
- when it startup again i enterd the debug mode.
- then i used the comand atkz -f -l 192.168.1.1
- rebooted with atgof

then i opened with cmd  the ftp from windows:

used the command "bin " and "hash and then uploaded the bin file with the firmware.

( I get the info that the file is transferd , but when i checked the console screen still i get the message that the format of the firmware is wrong and that i need to that that it is binary ?

Can someone help me with the exact procedure?  or are the steps correct what i did? 

Zyxel_James

Hello @Jarno_Smits,

According to "mount: wrong fs type, bad option, bad superblock", it could be database has been damaged, please try db recovery.

The steps are the same as uploading .bin file via FTP, except uploading the .db file. (471AAAA0C0.db)

Thank you.

James.

Jarno_Smits

hello James,

Sorry for the delayed answer, i also tried to upload the .db file in the simalair way, but still no success, almost every time i get the message that if a file is uploaded that the format is wrong??
that it must be binary??

I'm using the ftp function from Windows 11 in the command prompt, as descriped in the zyxel troubleshoot notes i found online, before uploading in need to use the command bin, and hash.

I also tried to use filezilla to access the paritition of the zywall, i'm able to access the paritition, but when i tried to upload the firmware file or a db file, then the upload dont start.

Does someone have some experiance with other FTP tools to upload the files to the zywall? 
that i can try, otherwise i think this zywall is good for the ewaste.

Zyxel_James

Hello @Jarno_Smits,

Yes, the command "bin" is necessary.

Which troubleshoot notes did you refer to?

database recovery has another step that firmware recovery doesn't have, that is, input "atcd 1" after entering to the debug mode, is it possible you miss this step? 

Please disable the PC firewall and refer to the steps below.

If db recovery still fail, could you provide the entire FTP log and console log? Thank you.

James

Zyxel_Stanley said:

1. Initial database recover process.
Connect the device directly via the console port using a terminal emulation program. And also connect the device on 1st Ethernet port with your PC. Reboot the device.

• Enter to debug mode
• Enter "atcd 1"
• Enter "atkz -f -l 192.168.1.1"
• Enter "atgof"

• After entering "atgof" system will go to restart and initial FTP server on device.

2. Upload Database file to device

• Change your PC IP address as 192.168.1.1.2 and mask 255.255.255.0

• Access device by FTP(by anonymous) and upload XXXX.db file.

• System will start to recover as default database.

After finishing the steps, you can do power recycle to make sure your device could boot up successfully.

Jarno_Smits

Zyxel_James said:

Hello @Jarno_Smits,

Yes, the command "bin" is necessary.

Which troubleshoot notes did you refer to?

database recovery has another step that firmware recovery doesn't have, that is, input "atcd 1" after entering to the debug mode, is it possible you miss this step? 

Please disable the PC firewall and refer to the steps below.

If db recovery still fail, could you provide the entire FTP log and console log? Thank you.

James

Zyxel_Stanley said:

1. Initial database recover process.
Connect the device directly via the console port using a terminal emulation program. And also connect the device on 1st Ethernet port with your PC. Reboot the device.

• Enter to debug mode
• Enter "atcd 1"
• Enter "atkz -f -l 192.168.1.1"
• Enter "atgof"

• After entering "atgof" system will go to restart and initial FTP server on device.

2. Upload Database file to device

• Change your PC IP address as 192.168.1.1.2 and mask 255.255.255.0

• Access device by FTP(by anonymous) and upload XXXX.db file.

• System will start to recover as default database.

After finishing the steps, you can do power recycle to make sure your device could boot up successfully.

Hello James,

I tried this procedure already, i did it again exactly as you descriped, see below the messages i get from the Zywall:

ZyWALL 110> atcd 1

Change Boot Number=1

ZyWALL 110> atkz -f -l 192.168.1.1

-f -l 192.168.1.1

OK

ZyWALL 110> atgof

Booting...

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

Error trying to mount db partition 5 times

mount: wrong fs type, bad option, bad superblock on /dev/sda4,

       missing codepage or other error

       In some cases useful info is found in syslog - try

       dmesg | tail  or so

Could not write 8 blocks in inode table starting at 81923: Attempt to write block from filesystem resulted in short write

Connect a computer to port 1 and FTP to 192.168.1.1 to upload the new file.

below the screenshot from the console when i upload the db file with FTP:

Zyxel_James

Hello @Jarno_Smits, 

Is it possible to arrange a remote session for database recovery?

I will contact you through private message, please check on your inbox, thank you.

James