Zyxel nas542 boot loop after installing OMV
Options
All Replies
-
the image is the one shared by you https://zyxel.diskstation.eu/Users/Mijzelf/NAS/542/and it has 6.99 MB, i rename it to uImage.520.bin from uImage.520ABAG1C0.bin0
-
That should be right. Maybe the load address is the problem. Try something else, like 82000000 or 2000000.
0 -
So, i made some progress using the bellow commands:
eth0.ipaddr=192.168.1.191
eth0.serverip=192.168.1.139
addpart /dev/mem 8M@0x8000(kernelraw)
addpart /dev/mem 8M@8M(kernel)
netload="/dev/mem.kernel"
tftp uImage.520.bin $netload
bootm ${netload}
It boots from the image but in the end, after restart i get bad magic number. Looking on this thread https://community.zyxel.com/en/discussion/7674/nas542-bootloop-after-debian-omv-get-a-new-firmware-solved/p4 i can see that some bootargs was modified on the config file, can you please help me with what i need to modify on the config file?1 -
So it boots the stock kernel, but after a restart nothing is changed? If you didn't do anything than booting the stock kernel, indeed nothing is changed. The idea is let the stock kernel use a Rescue stick (you can use the 540 one, when you exchange the ras.bin file by a 542 one, and set the right md5sum in the ras.bin.md5sum file) to flash the firmware, or a Universal usb_key_func stick to get telnet access to do some stuff.faierbol said:It boots from the image but in the end, after restart i get bad magic number.
0
Categories
- All Categories
- 439 Beta Program
- 2.8K Nebula
- 201 Nebula Ideas
- 126 Nebula Status and Incidents
- 6.3K Security
- 503 USG FLEX H Series
- 325 Security Ideas
- 1.6K Switch
- 84 Switch Ideas
- 1.3K Wireless
- 49 Wireless Ideas
- 6.8K Consumer Product
- 287 Service & License
- 458 News and Release
- 89 Security Advisories
- 31 Education Center
- 10 [Campaign] Zyxel Network Detective
- 4.3K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 96 Security Highlight
Freshman Member
Guru Member