Comments
-
@GandalfTheGrey: Have you already tried to boot the NAS with the following script? http://zyxel.diskstation.eu/Users/Mijzelf/universal_usb_key_func-2015-10-12.zip After extracting the files to the stick, you'll have to rename the desired shell script (in may case usb_key_func.sh.network_telnet.2). That way I was able to…
-
I had to erase the flash first using: /sbin/flash_erase /dev/mtd2 0 0. Then I've rewritten it using the file you've provided and now /firmware/sbin/info_printenv is finally returning readable output. I'm now looking into updating the firmware to correct the checksums in the env partition. Thanks you very much for your help.
-
I took the risk and have written your mtd2 to my NAS. It didn't fix the wrong magic error, but at least the NAS is still booting using the USB stick.
-
At least I've found a workaround to boot the NAS (without any disks at the moment): * Boot it with your universal_usb_key_func-2015-10-12 (network and telnet) * Connect by telnet * Change to root using su * Use vi to change the following lines in /etc/init.d/rcS #ubiattach -m ${IMG_MTD} -d ${IMG_MTD} #mount -t…
-
Thanks for your answer. Based on your other helpful entries in this forum, I think I've reached the right person :-) Unfortunatly I cannot set any values, because the command gives me the same error: / $ /firmware/sbin/info_setenv cur_bootfrom 2 envfs: wrong magic on /dev/mtd2 Based on the recovery script, /dev/mtd2 is the…
