usg 210 kernel panic
Options
One of our usg 210 firewall stopped working.
Message is:
We tried to reload firmware:
Message is:
Booting...
Start to check file system...
/dev/sda3: 480/20480 files (0.6% non-contiguous), 75445/81920 blocks
/dev/sda4: 198/23040 files (3.0% non-contiguous), 20926/92160 blocks
Done
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Kernel panic - not syncing: Attempted to kill init!
We tried to reload firmware:
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
USG210> atur
ERROR
USG210> atkz -f -i 192.168.1.1
-f
OK
atkz -f -l 192.168.1.1
USG210>
ERROR
USG210> atgof
Booting...
Connect a computer to port 1 and FTP to 192.168.1.1 to upload the new file.
Firmware received ...
Could not write 8 blocks in inode table starting at 65539: Attempt to write bloc
k from filesystem resulted in short write
Start to check file system...
/dev/sda3: 11/20480 files (0.0% non-contiguous), 6720/81920 blocks
/dev/sda4: 11/23040 files (0.0% non-contiguous), 7044/92160 blocks
Done
Building ...
[Update Filesystem]
Updating Code
..
done
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or other error
In some cases useful info is found in
dmesg | tail or so
.
[Update Kernel]
Extracting Kernel Image
//.
done
.
Writing Kernel Image ... done
Validate Kernel Image ... done
Restarting system.
U-Boot 2011.03 (Development build, svnversion: u-boot:425:427M, exec:exported) (
Build time: Aug 20 2013 - 14:09:25)
BootModule Version: V1.08 | 08/15/2013 10:45:46
DRAM: Size = 1024 Mbytes
Press any key to enter debug mode within 3 seconds.
............................................................
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.
Any ideas?
0
All Replies
-
Hi @selexi
I will send you private message for check this issue more details.
Share yours now!
Stanley
0 -
Hi @selexi
I don't know what have you done on this device and it caused device file system broken then leads device unable boots up.
So recovery system DataBase can resolve this situation.
And it's good hear the device is able work now.
Share yours now!
Stanley
0
Categories
- All Categories
- 413 Beta Program
- 2.3K Nebula
- 192 Nebula Ideas
- 87 Nebula Status and Incidents
- 5.3K Security
- 142 USG FLEX H Series
- 253 Security Ideas
- 1.3K Switch
- 75 Switch Ideas
- 993 Wireless
- 51 Wireless Ideas
- 6.1K Consumer Product
- 231 Service & License
- 362 News and Release
- 74 Security Advisories
- 23 Education Center
- 5 [Campaign] Zyxel Network Detective
- 2.6K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 101 About Community
- 67 Security Highlight