NAS 542 dead

Pandino84
Pandino84 Posts: 14  Freshman Member
Third Anniversary
in Personal Cloud Storage
hi, after a failed update of firmware my nas542 seem dead.
when on it restart continuosly... no assistance for me in italy... any idea?
«13

All Replies

  • ikubuf
    ikubuf Posts: 142  Ally Member
    5 Answers First Comment Friend Collector Second Anniversary
    edited August 2022
    There is a worldwide website include country local support.
    You can find Italy local support here.


  • Pandino84
    Pandino84 Posts: 14  Freshman Member
    Third Anniversary
    thanks ikubuf, but turin don't support private nas for local policy. no one of the zyxel partner soing it. this forum is the only hope or i have to trash it....
  • Mijzelf
    Mijzelf Posts: 2,763  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    You can try a 'RescueStick'. Here I have one for the '540, that can be adapted for the '542. Extract the zipfile to a (fat formatted) USB thumb drive, replace the ras.bin file by the <firmware>.bin from a 542, and adapt some textfile to have the right md5 sum of the new ras.bin file. Plug the thumb drive in, and boot the NAS. If you are lucky, it will reflash the firmware and cure the problem.
  • Pandino84
    Pandino84 Posts: 14  Freshman Member
    Third Anniversary
    edited August 2022
    thanks mijzelf. 
    i try you'r solution with a friend tomorrow evening... 4 eyes are better than 2
    i'll provide you any update.
    for now thanks
    if i ahve problem can you prepare to me a 'personalized' rescuestick? your instruction are pretty simple but i'm a newby....
    for modify the textfile is ok wordpad?
  • mMontana
    mMontana Posts: 1,389  Guru Member
    50 Answers 1000 Comments Friend Collector Fifth Anniversary
    @Pandino84 I'd suggest you to use Notepad++
  • Pandino84
    Pandino84 Posts: 14  Freshman Member
    Third Anniversary
    thanks mMontana
  • Mijzelf
    Mijzelf Posts: 2,763  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary
    if i ahve problem can you prepare to me a 'personalized' rescuestick?

    Yes, I can. But I have no way to test it, so it's only best effort.

  • Pandino84
    Pandino84 Posts: 14  Freshman Member
    Third Anniversary
    thanks mijzelf. i wry for now with my own, in case of failure i ask you
  • Pandino84
    Pandino84 Posts: 14  Freshman Member
    Third Anniversary
    update.
    usb key formatted fat inserted in tre front port usb
    blinking red led usb

    i post the flash log

    + FW_FILE=/mnt/partnerkey/nas5xx_fw/ras.bin
    + NANDPATH=/firmware/mnt/nand2
    + /firmware/sbin/info_printenv curr_bootfrom
    + awk -F= {print $2}
    + CURR_BOOTFROM=1
    + [ 1 -eq 1 ]
    + NEXT_BOOTFROM=2
    + /firmware/sbin/info_printenv kernel_mtd_1
    + awk -F= {print $2}
    + CURR_KERNEL_MTD=4
    + /firmware/sbin/info_printenv sysimg_mtd_1
    + awk -F= {print $2}
    + CURR_IMG_MTD=5
    + /firmware/sbin/info_printenv kernel_mtd_2
    + awk -F= {print $2}
    + NEXT_KERNEL_MTD=6
    + /firmware/sbin/info_printenv sysimg_mtd_2
    + awk -F= {print $2}
    + NEXT_IMG_MTD=7
    + md5sum -c /mnt/partnerkey/nas5xx_fw/ras.bin.md5sum
    /mnt/partnerkey/nas5xx_fw/ras.bin: OK
    + [ 0 -ne 0 ]
    + /sbin/setLED SYS ORANGE BLINK
    Fail to open gpio device
    + sleep 1
    + mkdir -p /mnt/partnerkey/buffer
    + /sbin/bin2ram little /mnt/partnerkey/nas5xx_fw/ras.bin /mnt/partnerkey/buffer/tlv.bin
    + [ 4 -ne 4 ]
    + sync
    + sleep 1
    + cd /mnt/partnerkey/buffer
    + /sbin/fw_unpack -C . -i ./tlv.bin
    + [ 0 -ne 0 ]
    + sync
    + sync
    + ls /mnt/partnerkey/buffer
    DATA_0000
    DATA_0001
    DATA_0002
    DATA_0101
    DATA_0200
    DATA_0201
    DATA_0202
    DATA_0203
    DATA_0204
    DATA_1000
    DATA_1004
    DATA_a000
    DATA_a002
    tlv.bin
    + sleep 10
    + /bin/rm -f /mnt/partnerkey/buffer/tlv.bin
    + [ -s /mnt/partnerkey/buffer/DATA_0101 ]
    + /firmware/sbin/mrd_model -p
    + board_model=B203
    + cat /mnt/partnerkey/buffer/DATA_0101
    + file_model=B103
    + echo -n board_model=(B203), file_model=(B103) ... 
    board_model=(B203), file_model=(B103) ... + [ xB203 == xB103 ]
    + echo NOT equal! /firmware/sbin/mrd_model -s B103
    NOT equal! /firmware/sbin/mrd_model -s B103
    + error_exit
    + setLED SYS RED BLINK
    Fail to open gpio device
    + setLED HDD1 RED BLINK
    Fail to open gpio device
    + setLED HDD2 RED BLINK
    Fail to open gpio device
    + setLED HDD3 RED BLINK
    Fail to open gpio device
    + setLED HDD4 RED BLINK
    Fail to open gpio device
    + setLED COPY RED BLINK
    Fail to open gpio device
    + /bin/sync
    + read


    help thanks
    i use last  firware for 542
  • Mijzelf
    Mijzelf Posts: 2,763  Guru Member
    250 Answers 2500 Comments Friend Collector Seventh Anniversary

    board_model=(B203), file_model=(B103) ... + [ xB203 == xB103 ]
    NOT equal! /firmware/sbin/mrd_model -s B103

    According to this lines you used a firmware file of the '540 (B103). Did you exchange the ras.bin? And your board is a '520. (B203). A 542 is a B403. Are you sure you have a 542?

Categories

Consumer Product Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）