Zywall 310 error after boot mount: wrong fs type, bad option, bad superblock on /dev/loop0,

OliZ

Hi there,
after the Zuwahl power up I get the following in the console:

Firmware received ... 

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 syslog - try

       dmesg | tail  or so

[Update Kernel]

        Extracting Kernel Image

        .

        done

        Writing Kernel Image ... done

        Validate Kernel Image ... done

Restarting system.

I already tried to put the latest firmware via ftp to the zywall, it works but the zywall could not start.

Every help would be great.

Thanks in advance
Oliver

gb5102

It appears the firmware image is corrupted, you will likely need to perform a firmware recovery via the serial console. It could also mean the flash memory chip in the device has failed, but I would try the recovery first.

See "Appendix 3. Firmware Recovery" in the following document:

ftp://ftp.zyxel.com/ZyWALL_310/firmware/ZyWALL 310_4.65(AAAB.1)C0_2.pdf

OliZ

Hi,
thanks but I tried already to flash the firmware with the serial cable and the ftp server.
I also tried to flashed the database.
But still the same.

If anybody has another idea?

Regrds
Oliver

Zyxel_Cooldia

Hi @OliZ,
Welcome to Zyxel community. 
Can you paste full console log during device boot up.
With full console log, we will be able to trace where the issue is.

OliZ

Hi Zyxel_Cooldia,

here the log:

U-Boot 2011.03 (Development build, svnversion: u-boot:422M, exec:exported) (Build time: Feb 21 2013 - 10:24:45)

BootModule Version: V1.10 | 02/21/2013 10:45:46
DRAM: Size = 2048 Mbytes

Press any key to enter debug mode within 3 seconds.
............................................................
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

*** NMI Watchdog interrupt on Core 0x00 ***
$0 0x0000000000000000 at 0x0000000010009ce0
v0 0xffffffff80e32018 v1 0x0000000000000001
a0 0xfffffffffffffffe a1 0x0000000000000000
a2 0xffffffff80db0000 a3 0x80000000031797c8
a4 0x80000000031797c8 a5 0x800000008f054d80
a6 0x0000000000000000 a7 0x800000008f049530
t0 0x0000000010009ce0 t1 0x000000001000001f
t2 0xffffffff808ed150 t3 0x80000000003b4000
s0 0x80000000031797c8 s1 0x0000000000000001
s2 0xffffffff80d98e68 s3 0xffffffff80e10500
s4 0xffffffff808797e0 s5 0x0000000000000079
s6 0x0000000000000000 s7 0x0000000000000001
t8 0x0000000000000006 t9 0xffffffff8087b238
k0 0x0000000000000000 k1 0x0000000000000000
gp 0xffffffff80e04000 sp 0xffffffff80e07ae0
s8 0xffffffff80d99fd8 ra 0xffffffff80882734
err_epc 0xffffffff80882738 epc 0xffffffff808797e0
status 0x0000000010489ce4 cause 0x0000000040808c00
sum0 0x0080000000000000 en0 0x09802f0000008000
*** Chip soft reset soon ***

*** NMI Watchdog interrupt on Core 0x01 ***
$0 0x0000000000000000 at 0x0000000010009ce0
v0 0xffffffff80e32018 v1 0x0000000000000001
a0 0xfffffffffffffffd a1 0x0000000000000000
a2 0xffffffff80db0000 a3 0x80000000031837c8
a4 0x80000000031837c8 a5 0x800000008f054c80
a6 0x0000000000000000 a7 0x800000008e5fa040
t0 0x0000000010009ce0 t1 0x000000001000001f
t2 0x000000000000000a t3 0x80000000003e8000
s0 0x80000000031837c8 s1 0x0000000000000001
s2 0xffffffff80d98e68 s3 0xffffffff80e10500
s4 0xffffffff808797e0 s5 0x0000000000000079
s6 0x0000000000000000 s7 0x800000008f800000
t8 0x0000000000000007 t9 0xffffffff8087b238
k0 0x0000000000000000 k1 0x0000000000000000
gp 0x80000000003c0000 sp 0x80000000003c3b40
s8 0xffffffff80d99fd8 ra 0xffffffff80882734
err_epc 0xffffffff80882738 epc 0xffffffff808797e0
status 0x0000000010489ce4 cause 0x0000000040808800
sum0 0x0080000000000000 en0 0x0000000000000000
*** Chip soft reset soon ***

*** NMI Watchdog interrupt on Core 0x02 ***
$0 0x0000000000000000 at 0x0000000010009ce0
v0 0xffffffff80e32018 v1 0x0000000000000001
a0 0xfffffffffffffffb a1 0x0000000000000000
a2 0xffffffff80db0000 a3 0x800000000318d7c8
a4 0x800000000318d7c8 a5 0x800000008f054b80
a6 0x0000000000000000 a7 0x800000008d844ab0
t0 0x0000000010009ce0 t1 0x000000001000001f
t2 0xffffffff808ed150 t3 0x800000008f014000
s0 0x800000000318d7c8 s1 0x0000000000000001
s2 0xffffffff80d98e68 s3 0xffffffff80e10500
s4 0xffffffff808797e0 s5 0x0000000000000079
s6 0x0000000000000000 s7 0x800000008f800000
t8 0x0000000000000007 t9 0xffffffff8087b238
k0 0x0000000000000000 k1 0x0000000000000000
gp 0x80000000003c8000 sp 0x80000000003cbb40
s8 0xffffffff80d99fd8 ra 0xffffffff80882734
err_epc 0xffffffff80882738 epc 0xffffffff808797e0
status 0x0000000010489ce4 cause 0x0000000040808800
sum0 0x0080000000000000 en0 0x0000000000000000
*** Chip soft reset soon ***

*** NMI Watchdog interrupt on Core 0x04 ***
$0 0x0000000000000000 at 0x0000000010009ce0
v0 0xffffffff80e32018 v1 0x0000000000000001
a0 0xffffffffffffffef a1 0x0000000000000000
a2 0xffffffff80db0000 a3 0x80000000031a17c8
a4 0x80000000031a17c8 a5 0x800000008f054980
a6 0x0000000000000000 a7 0x0000000000000000
t0 0x0000000010009ce0 t1 0x000000001000001f
t2 0xffffffff813c0000 t3 0x800000008f090000
s0 0x80000000031a17c8 s1 0x0000000000000001
s2 0xffffffff80d98e68 s3 0xffffffff80e10500
s4 0xffffffff808797e0 s5 0x0000000000000079
s6 0x0000000000000000 s7 0x800000008f800000
t8 0x0000000000000004 t9 0xffffffff8087b238
k0 0xf30eaf5e2a89df4f k1 0x7427cfb03be8dec6
gp 0x80000000003d4000 sp 0x80000000003d7b40
s8 0xffffffff80d99fd8 ra 0xffffffff80882734
err_epc 0xffffffff80882738 epc 0xffffffff808797e0
status 0x0000000010489ce4 cause 0x0000000040808800
sum0 0x0080000000000000 en0 0x0000000000000000
*** Chip soft reset soon ***

*** NMI Watchdog interrupt on Core 0x05 ***
$0 0x0000000000000000 at 0x0000000010009ce0
v0 0xffffffff80e32018 v1 0x0000000000000001
a0 0xffffffffffffffdf a1 0x0000000000000000
a2 0xffffffff80db0000 a3 0x80000000031ab7c8
a4 0x80000000031ab7c8 a5 0x800000008f054880
a6 0x0000000000000000 a7 0x0000000000000000
t0 0x0000000010009ce0 t1 0x000000001000001f
t2 0xffffffff813c0000 t3 0x80000000003ac000
s0 0x80000000031ab7c8 s1 0x0000000000000001
s2 0xffffffff80d98e68 s3 0xffffffff80e10500
s4 0xffffffff808797e0 s5 0x0000000000000079
s6 0x0000000000000000 s7 0x800000008f800000
t8 0x0000000000000004 t9 0xffffffff8087b238
k0 0xfc5175ebf3ed65fb k1 0xfc8ba6de7ed91fff
gp 0x80000000003dc000 sp 0x80000000003dfb40
s8 0xffffffff80d99fd8 ra 0xffffffff80882734
err_epc 0xffffffff80882738 epc 0xffffffff808797e0
status 0x0000000010489ce4 cause 0x0000000040808800
sum0 0x0080000000000000 en0 0x0000000000000000
*** Chip soft reset soon ***

Zyxel_Cooldia

Hi @OliZ,

Not sure if it is hardware issue or just firmware corrupted in firmware update process.

ZyWal-310 have dual partition, please try to boot up in other partition.

Step:

1) Attached serial console and boot up ZyWal-310.

2) Hit any key to enter debug mode when you see "Press any key to enter debug mode within 3 seconds."

3) Type atcd 1 or atcd 2 to switch boot up please

4) type atgo to boot up device.

OliZ

Now, when I switch it on it shows only U-Boot 2011.03 (Development build, svnversion: u-boot:422M, exec:exported) (Build time: Feb 21 2013 - 10:24:45)
nothing more.

OliZ

Hi there,

the zywall doesn't response to atcd 1 or atcd 2 or atcd 0:

Press any key to enter debug mode within 3 seconds.

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

Enter Debug Mode

ZW310> atcd1

ERROR

ZW310> atcd 2

ERROR

ZW310> atcd 1

ERROR

ZW310> atcd1

ERROR

ZW310> ?

ERROR

ZW310> atcd 0

ERROR

ZW310> atgo

Booting...

Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

the only thing working is the ftp server and atgo?

Greetings 
Oliver

Zyxel_Cooldia

Hi @OliZ,
You might need to proceed to RMA if it is still unable to boot up successfully via firmware recovery.