How to recovery database when it is broken.
Options
Zyxel_Stanley
Posts: 1,366 Zyxel Employee
When file system broken, the device is unable boot up successfully.
And may display error log like:
(1) Plug-in power cable and enter to debug mode.
(2) Enter at command:
a. atcd 0
b. atkz -f -l 192.168.1.1
c. atgof
(3) After device boots up, connect your network cable to USG Port1 and change IP address as the same subnet in 192.168.1.0/24.
(4) PC access to USG FTP by 192.168.1.1 and upload .db file to to USG.
a. bin
b. hash
c. put *the file path of .db*
(5) After uploaded successfully then do hardware reboot again.
Then system should able boots up successfully.
And may display error log like:
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or other error
You can the follow this steps to recovery device database.(Console cable is required)(1) Plug-in power cable and enter to debug mode.
(2) Enter at command:
a. atcd 0
b. atkz -f -l 192.168.1.1
c. atgof
(3) After device boots up, connect your network cable to USG Port1 and change IP address as the same subnet in 192.168.1.0/24.
(4) PC access to USG FTP by 192.168.1.1 and upload .db file to to USG.
a. bin
b. hash
c. put *the file path of .db*
(5) After uploaded successfully then do hardware reboot again.
Then system should able boots up successfully.
Tagged:
0
Categories
- All Categories
- 397 Beta Program
- 2.1K Nebula
- 116 Nebula Ideas
- 78 Nebula Status and Incidents
- 5.1K Security
- 51 USG FLEX H Series
- 247 Security Ideas
- 1.3K Switch
- 70 Switch Ideas
- 907 WirelessLAN
- 34 WLAN Ideas
- 5.9K Consumer Product
- 210 Service & License
- 332 News and Release
- 71 Security Advisories
- 21 Education Center
- 5 [Campaign] Zyxel Network Detective
- 1.9K FAQ
- 880 Nebula FAQ
- 415 Security FAQ
- 221 Switch FAQ
- 195 WirelessLAN FAQ
- 46 Consumer Product FAQ
- 137 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 72 About Community
- 63 Security Highlight