NAS542 bootloop after Debian/OMV (get a new firmware) (solved)

Mijzelf · July 2019

Your egiga0 initially has an apipa address, which the dhcp client assigns when it doesn't get one from a server. Directly after assigning it a fixed address the interface resets, and a new apipa address is assigned.

First thing which comes to my mind is bad cabling, but maybe also a bad NIC. Have you tried another cable/port?

Have you the possibility to measure the voltage of the power supply when the system is up, and when you assign a fixed IP? A bad power supply could also cause this.

The output of netstat seems normal. A bit strange that there are several servers on udp 137 and 138, but that could be the result of a bouncing NIC, in combination with some auto-started daemons on network up.

Triu · July 2019

Tried different Ports (on Router and NAS) and another cable, but with the same result.

Can't measure the voltage. Unfortunately the NAS520 has a 12V power supply so i can't try this out.

Think i do the TFTP and uImage stuff again.

Edit: When i change IP and then directly connect to the webinterface it works, but again with limited Icons on webinterface. After some seconds the IP changes back again and the connection is lost.

Maybe i should try now the old uImage which doesn't worked before to get all Icons?

The webinterface shows me now NAS542 and it doesn't matter if i boot from uimage (both: uImage.521 and uImage.520ABAC1C0.bin) or do nothing, i come to the same webinterface and changing IPs. With the 520ABAC1C0.bin there is some new entries in console.

Please press Enter to activate this console. Jul 28 19:33:54 (none) netatalk[1458]: Restarting 'cnid_metad' (restarts: 17)
Jul 28 19:33:54 (none) cnid_metad[2507]: tsockfd_create: getaddrinfo: Temporary failure in name resolution
Jul 28 19:33:54 (none) httpd[2482]: [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
Jul 28 19:33:54 (none) httpd[2482]: [warn] RSA server certificate CommonName (CN) `(none)' does NOT match server name!?
Jul 28 19:33:54 (none) httpd[2482]: [error] mod_auth_zyxel: initialized.
Jul 28 19:33:55 (none) netatalk[1458]: Restarting 'cnid_metad' (restarts: 18)
Jul 28 19:33:55 (none) cnid_metad[2510]: tsockfd_create: getaddrinfo: Temporary failure in name resolution
Jul 28 19:33:56 (none) netatalk[1458]: Restarting 'cnid_metad' (restarts: 19)
Jul 28 19:33:56 (none) cnid_metad[2511]: tsockfd_create: getaddrinfo: Temporary failure in name resolution
Jul 28 19:33:57 (none) netatalk[1458]: Restarting 'cnid_metad' (restarts: 20)
Jul 28 19:33:57 (none) cnid_metad[2512]: tsockfd_create: getaddrinfo: Temporary failure in name resolution
Jul 28 19:33:58 (none) netatalk[1458]: Restarting 'cnid_metad' (restarts: 21)
Jul 28 19:33:58 (none) cnid_metad[2513]: tsockfd_create: getaddrinfo: Temporary failure in name resolution
Jul 28 19:33:59 (none) netatalk[1458]: Restarting 'cnid_metad' (restarts: 22)
Jul 28 19:33:59 (none) cnid_metad[2514]: tsockfd_create: getaddrinfo: Temporary failure in name resolution
Jul 28 19:34:00 (none) netatalk[1458]: Restarting 'cnid_metad' (restarts: 23)
Jul 28 19:34:00 (none) cnid_metad[2515]: tsockfd_create: getaddrinfo: Temporary failure in name resolution
Jul 28 19:34:01 (none) netatalk[1458]: Restarting 'cnid_metad' (restarts: 24)
Jul 28 19:34:01 (none) cnid_metad[2518]: tsockfd_create: getaddrinfo: Temporary failure in name resolution
Jul 28 19:34:02 (none) netatalk[1458]: Restarting 'cnid_metad' (restarts: 25)
Jul 28 19:34:02 (none) cnid_metad[2519]: tsockfd_create: getaddrinfo: Temporary failure in name resolution

Also i have done again the software reset_and_reboot and the hardware button (3 beeps) without any change, but i see the apipa adress and also after i changed IP, the new IP at the router. (little change, i can't get to the webinterface, no matter what IP is set)

How can i request a new IP from dhcp, cause the barebox "dhcp" command doesn't work when the zyxel firmware is up, also dhclient doesn't work.

Could this problem come from the sysdis.img i have mounted and copied to flash?

Triu · July 2019

Don't think about it anymore.

It costs me and you alot of time and after i switched back to my workdesk, i put in the power cable and it turned on without the power button. I tried to shut it down with the power button and it worked, but disconnect the cable and connect it again, turned it on immediately.

What should i say......after that, a concatenation of unfortunate circumstances lead to a complete failure which i would say is not repairable anymore.

Maybe i will use the case and the backplane with SATA ports and buy a singleboardcomputer with PCIe on it (maybe RockPro64). But will first try if the backplane will work out of the box with debian on another PC.

Mijzelf, thank you alot for your time and patience.

Mijzelf · July 2019

You are welcome.

greenwitch · November 2020

Hi,

I have the same problem. Is it possible to run again Debian. I dont want to go back to original crappy firmware?

Do I understand that I need to upload kernel again and set correct paths in kernel command line?

I have following log:

" 1
booting kernel of type uimage from /dev/nand0.kernel2.bb
Verifying Checksum ... Bad Data CRC
Failed.
booting kernel of type uimage from /dev/nand0.kernel1.bb
ERROR: out of memory
"

Adam

greenwitch · November 2020

OK, I moved forward a little bit. I was able to upload debian kernel.
What is strange on bank 1 i got following error

booting kernel of type uimage from /dev/nand0.kernel1.bb

Bad Header Checksum

Failed.

which is strange as I upload exactly the same kernel as on bank 2.

on bank 2 I have kernel panic

[   20.364539] VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
[   20.371618] Please append a correct "root=" boot option; here are the available partitions:
[   20.380009] 1f00             256 mtdblock0 (driver?)
[   20.385089] 1f01             512 mtdblock1 (driver?)
[   20.390173] 1f02             256 mtdblock2 (driver?)
[   20.395252] 1f03           10240 mtdblock3 (driver?)
[   20.400336] 1f04           10240 mtdblock4 (driver?)
[   20.405415] 1f05          112640 mtdblock5 (driver?)
[   20.410498] 1f06           10240 mtdblock6 (driver?)
[   20.415576] 1f07          112640 mtdblock7 (driver?)
[   20.420660] 1f08            6144 mtdblock8 (driver?)
[   20.425738] 0800      2930266584 sda driver: sd
[   20.430389]   0801      2930265088 sda1 81ae083b-429a-4768-9f2c-a38c8ddeb287
[   20.437478] 0810      2930266584 sdb driver: sd
[   20.442122]   0811      2930265088 sdb1 eceb1340-7ebb-477c-8594-46d3d3ca0f4c
[   20.449210] 0830      1953514584 sdd driver: sd
[   20.453853]   0831          514048 sdd1 00000000-0000-0000-0000-000000000000
[   20.460940]   0832      1952997952 sdd2 00000000-0000-0000-0000-000000000000
[   20.468025] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I can see it is related to lack of initrams for that kernel.
I am using this kernel linux-image-3.2.102-1-nas5xx-armhf.zip from site: http://seafile.servator.de/nas/zyxel/

I assume I should adjust boot arguments? Any hint how to fix that?

Barebox-C2K >/ printenv
locals:
PATH=/env/bin
ip=dhcp
kernel_loc=nand
rootfs_loc=nand
uloaderimage=microloader-c2kevm.bin
bareboximage=barebox-c2kevm.bin
mfg_kernel_img=uImage_MFG
mfg_rootfs_img=rootfs_ubi.img_MFG
rootfs_type=ubifs
rootfsimage=root.ubifs-128k
kernelimage_type=uimage
kernelimage=uImage
spi_parts=256k(uloader)ro,512k(barebox)ro,256k(env)
spi_device=spi0.0
nand_device=comcertonand
nand_parts=10M(config),10M(kernel1),110M(rootfs1),10M(kernel2),110M(rootfs2),-(reserved)
rootfs_mtdblock_nand=2
autoboot_timeout=3
usb3_internal_clk=yes
bootargs=console=ttyS0,115200n8, init=/etc/preinit pcie_gen1_only=yes mac_addr=,,
next_bootfrom=1
curr_bootfrom=1
kernel_mtd_1=4
sysimg_mtd_1=5
kernel_mtd_2=6
sysimg_mtd_2=7
MODEL_ID=B103
globals:

greenwitch · November 2020

OK, I moved forward a little bit. I was able to upload debian kernel.
What is strange on bank 1 i got following error

booting kernel of type uimage from /dev/nand0.kernel1.bb
Bad Header Checksum
Failed.

which is strange as I upload exactly the same kernel as on bank 2.

on bank 2 I have kernel panic

[   20.364539] VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
[   20.371618] Please append a correct "root=" boot option; here are the available partitions:
[   20.380009] 1f00             256 mtdblock0 (driver?)
[   20.385089] 1f01             512 mtdblock1 (driver?)
[   20.390173] 1f02             256 mtdblock2 (driver?)
[   20.395252] 1f03           10240 mtdblock3 (driver?)
[   20.400336] 1f04           10240 mtdblock4 (driver?)
[   20.405415] 1f05          112640 mtdblock5 (driver?)
[   20.410498] 1f06           10240 mtdblock6 (driver?)
[   20.415576] 1f07          112640 mtdblock7 (driver?)
[   20.420660] 1f08            6144 mtdblock8 (driver?)
[   20.425738] 0800      2930266584 sda driver: sd
[   20.430389]   0801      2930265088 sda1 81ae083b-429a-4768-9f2c-a38c8ddeb287
[   20.437478] 0810      2930266584 sdb driver: sd
[   20.442122]   0811      2930265088 sdb1 eceb1340-7ebb-477c-8594-46d3d3ca0f4c
[   20.449210] 0830      1953514584 sdd driver: sd
[   20.453853]   0831          514048 sdd1 00000000-0000-0000-0000-000000000000
[   20.460940]   0832      1952997952 sdd2 00000000-0000-0000-0000-000000000000
[   20.468025] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I can see it is related to lack of initrams for that kernel. ANy hint how to fix that?

I am using this kernel linux-image-3.2.102-1-nas5xx-armhf.zip

my boot config

Barebox-C2K >/ printenv
locals:
PATH=/env/bin
ip=dhcp
kernel_loc=nand
rootfs_loc=nand
uloaderimage=microloader-c2kevm.bin
bareboximage=barebox-c2kevm.bin
mfg_kernel_img=uImage_MFG
mfg_rootfs_img=rootfs_ubi.img_MFG
rootfs_type=ubifs
rootfsimage=root.ubifs-128k
kernelimage_type=uimage
kernelimage=uImage
spi_parts=256k(uloader)ro,512k(barebox)ro,256k(env)
spi_device=spi0.0
nand_device=comcertonand
nand_parts=10M(config),10M(kernel1),110M(rootfs1),10M(kernel2),110M(rootfs2),-(reserved)
rootfs_mtdblock_nand=2
autoboot_timeout=3
usb3_internal_clk=yes
bootargs=console=ttyS0,115200n8, init=/etc/preinit pcie_gen1_only=yes mac_addr=,,
next_bootfrom=1
curr_bootfrom=1
kernel_mtd_1=4
sysimg_mtd_1=5
kernel_mtd_2=6
sysimg_mtd_2=7
MODEL_ID=B103
globals:

Can somebody share their bootargs?

greenwitch · November 2020

Or better printenv.

I am digging further. I have changed bootargs but it is not stores after reboot i have always go back to I have posted. I can change it and boot by bootm /dev/nand0.kernel2.bb

archigraf · September 2021

Have a look at this Posting: https://community.zyxel.com/en/discussion/11609/nas-542-doesn-t-boot-anymore-no-usb-stick-is-working-serial-connection-is-working/p1

MEriksen · May 2022

Hello.
Have read through and tested these suggested solutions. 
After updating / env / config, I get syntax error at boot. 
Have I lost access to the device? 
Is the next stop for this device in the trash or is it possible to reach config in other ways?

NAS542 bootloop after Debian/OMV (get a new firmware) (solved)

Comments

Categories

Consumer Product Help Center