General NAS-Central Forums

Welcome to the NAS community
It is currently Mon Jun 26, 2017 5:12 am

All times are UTC




Post new topic Reply to topic  [ 9 posts ] 
Author Message
 Post subject: Manual firmware-flashing
PostPosted: Fri Dec 26, 2014 11:00 pm 
Offline

Joined: Fri Dec 26, 2014 10:52 pm
Posts: 5
I have a NSA 210 device which is running V3.20(AFL.0)D0 firmware. My guess is that this version is specific to the company that sold the device and also why I'm unable to upgrade it using Zyxel-firmwares. My question is related to how I would flash the firmware over like telnet or ssh? This should be possible, right?

Thankful for any help!


Top
 Profile  
 
PostPosted: Sat Dec 27, 2014 10:02 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6002
Who branded it?

What is the output of
Code:
/zyxel/sbin/mrd_model -p


Top
 Profile  
 
PostPosted: Sat Dec 27, 2014 11:03 am 
Offline

Joined: Fri Dec 26, 2014 10:52 pm
Posts: 5
Mijzelf wrote:
Who branded it?

My device is branded by Telia in Sweden. The only difference in features is another backup utility for the cloud. I was thinking it is a standard 3.20 apart from that. But perhaps I might be wrong.

Quote:
What is the output of
Code:
/zyxel/sbin/mrd_model -p

The "/zyxel/" path does not exist on my device.

Output for
Code:
/sbin/mrd_model -p
gives me this:
Code:
sh-4.1# /sbin/mrd_model -p
sh: /zyxel/sbin/fw_printenv: not found


Top
 Profile  
 
PostPosted: Sat Dec 27, 2014 12:34 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6002
Quote:
The "/zyxel/" path does not exist on my device.
That complicates it. The scripts/binaries needed to flash the device are stored in /zyxel/sbin/. But maybe it's only renamed? What gives 'ls /' ?

Can you find a fw_printenv anywhere?


Top
 Profile  
 
PostPosted: Sat Dec 27, 2014 12:50 pm 
Offline

Joined: Fri Dec 26, 2014 10:52 pm
Posts: 5
Quote:
Can you find a fw_printenv anywhere?

Not that I can find :(
Code:
sh-4.1# find / -name fw_printenv
find: File system loop detected; `/e-data/1580b6c6-a829-4b03-84b0-ca13818f4edc/ffproot' is part of the same file system loop as `/'.

Quote:
What gives 'ls /' ?

Code:
sh-4.1# ls /
after_booting.sh  dev     etc  home    lib  proc  sys  usr
bin               e-data  ffp  i-data  mnt  sbin  tmp  var

However, /sbin/ contains a few firmware scripts:
Code:
sh-4.1# ls /sbin/
CheckPrinter                          mkdosfs
Decompress_To_HD.sh                   mkfs.ext2
account.sh                            mkfs.ext3
adjtimex                              mkreiserfs
badblocks                             mkswap
blockdev                              modprobe
buzzerc                               monitord
check_key                             mount.fuse
chroot                                mount.ntfs-3g
crond                                 mrd_model
debugreiserfs                         mtools
dhcpcd                                myhotplug
dosfsck                               ntpdate_sync.sh
dumpe2fs                              pivot_root
e2fsck.sh                             poweroff
eject                                 pwr_resume
fanctrld                              quotacheck
flash_eraseall                        quotaoff
flashcp                               quotaon
freeramdisk                           ras2mtd
fsck.ext2                             reboot
fsck.ext3                             reiserfsck
fwupgrade_erase_write_ras.sh          reiserfsck_rebuild_tree.sh
fwupgrade_extract_verify.sh           reiserfstune
fwupgrade_make_ramdisk_at_devram1.sh  repquota
fwupgrade_umount_freeramdisk.sh       resize_reiserfs
getLED                                rmmod
getty                                 route
halt                                  setLED
hotplug                               start-stop-daemon
hotplug_add_PTP.sh                    storage_autoRepair.sh
hotplug_add_SATA.sh                   storage_gen_swap.sh
hotplug_add_storage.sh                storage_gen_swap_usb.sh
hotplug_remove_PTP.sh                 storage_synceSATA_sdx1.sh
hotplug_remove_SATA.sh                swapoff
hotplug_remove_storage.sh             swapon
hwclock                               syslogd
i2cget                                telnetd
i2cset                                todefault.sh
ifconfig                              tune2fs
init                                  usbzync
insmod                                usbzync.sh
klogd                                 usbzync_rm_rf.sh
losetup                               uuidgen
lsmod                                 xfs_repair.sh
makekey                               zcip
makepwd                               zysh.sh
md5sum                                zyshclient
mdadm                                 zyshd
mdir


I would be happy to provide you with direct telnet access if you would care to take a look yourself?


Top
 Profile  
 
PostPosted: Sat Dec 27, 2014 2:38 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6002
You are running chrooted ffp, which makes it impossible to see the root directory directly. You can use execute_outside_chroot to see if /zyxel exists, and to start a telnet daemon outside the chroot. (Use the -p option of telnetd to start it on a different port. The default port is already in use by ffp telnetd).


Top
 Profile  
 
PostPosted: Sat Dec 27, 2014 3:15 pm 
Offline

Joined: Fri Dec 26, 2014 10:52 pm
Posts: 5
Ah, my bad. I should have discovered that.

Code:
/ # /zyxel/sbin/mrd_model -p
DB01


Top
 Profile  
 
PostPosted: Sat Dec 27, 2014 6:09 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6002
Good. The upgrade script /zyxel/sbin/fwupgrade_extract_verify.sh checks the nas hardware tag against some tag in the firmware. When it doesn't fit, it refuses to install the firmware. On a 'genuine' 210 the tag is D401, on your box it is DB01. So if you change the tag, I expect you to be able to install the 'normal' 210 firmware.

You can change the tag by executing
Code:
/zyxel/sbin/mrd_model -s D401
This stores the value in the u-boot environment.

After a reboot you should be able to install genuine firmware. I recommend you to not directly install the latest, as I don't know if the flash partition sizes are stable over all versions, but first 3.20, then 4.10, then 4.40, and finally 4.41. The firmware can be found here.


Top
 Profile  
 
PostPosted: Sat Dec 27, 2014 11:49 pm 
Offline

Joined: Fri Dec 26, 2014 10:52 pm
Posts: 5
Changed the tag and tried updating. Everything works!

Thanks a lot for your help. You rock!


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 9 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group