Turn Your TS-209 II Into TS-209 Pro II (Risk-Free)

This post introduces an ideal and safe method to change a TS-209 II into a TS-209 Pro II, the basic idea is to fake the hardware type during system startup, thus make a perfect hack.

There’s a utility /sbin/config_util which is used for many purposes, including get/set hardware signatures, we’ll use it to change the box type.

The Method

SSH onto your TS-209 II, then enter:

mount -o loop /dev/mtdblock5 /tmp/config
cd /tmp/config

Now edit autorun.sh, add the following lines:

ln -s /sbin/config_util /sbin/set_hwtype
/sbin/set_hwtype 2

Then unmount the partition:

cd /
umount /tmp/config

Reboot the box, enjoy your TS-209 Pro II :D

NOTICE: To examine if you’re running as TS-209 Pro II, go to Administration screen, check if you have the AD option in Microsoft Network section, and NFS in left panel.

NOTICE: The NFS in TS-209 Pro II has some limitations, you can’t mount the exported filesystems on a Mac without some hacks, to make the exports mountable on OS X, take the following steps:

1. Setup your exports as usual (through QNAP’s web interface)
2. Go to /etc/config, edit nfssetting, change the access options from rw to rw,insecure,no_subtree_check
3. Re-enable NFS service through web interface.

That’s it.

UPDATE: After upgrading to firmware 2.1.2 build 1031T, this trick still works, check the following image:

UPDATE: Another method is to create a file named hw_type with a single line of ‘0099′ and put it into /dev/mtdblock5, then reboot. This may require reflashing with PRO firmware, tried it on 0904T non-PRO firmware and failed, succeeded with 1031T PRO firmware.

UPDATE: Just did a byte-to-byte comparison between 1031T PRO and STD firmwares, they are the same. So I guess the only difference between two types are hidden in /dev/mtdblock0 ~ /dev/mtdblock5, maybe the hw_type is the key.


44 Comments

  1. Max
    Posted November 11, 2008 at 10:28 pm | Permalink

    It works also on TS-109 and TS-109 Pro ?

    Thanks a lot,
    Max

  2. Posted November 11, 2008 at 11:38 pm | Permalink

    I would say it’ll work on TS-109 as well, just give it a try, if in any case it doesn’t work, just revert back, you won’t lose anything.

  3. hugon
    Posted November 15, 2008 at 10:57 pm | Permalink

    I tested the 2 method, without success.
    In the first method, the autorun.sh file does not exist.
    I create but to no avail.
    In the second method hw_type file already exists, with 0055 inside.
    I change 0055 in 0099, without success either.

  4. Posted November 17, 2008 at 12:20 am | Permalink

    @Hugon,

    For the 1st method, it should work because other people have succeeded, the reason you failed might be that your autorun.sh is not ok, make sure it’s a Unix sript file (Windows notepad CANNOT create the correct script file), i.e. it has the contents like:

    #!/bin/sh
    ln -s /sbin/config_util /sbin/set_hwtype && /sbin/set_hwtype 2

    and you give it right permission:

    chmod 755 autorun.sh

    For the 2nd method, as I wrote in the post, you probably need to reflash with a PRO firmware.

  5. hugon
    Posted November 17, 2008 at 2:33 am | Permalink

    thank you for your clarification
    now it works

  6. Max
    Posted November 19, 2008 at 6:11 am | Permalink

    It works also with TS-109, i have used 2nd method.

    Thanks !!!

  7. Point7
    Posted November 20, 2008 at 6:41 pm | Permalink

    I’m a total linux noob. I want to try the method with the hw_type file but i don’t know how to create that file and put it on my 109.
    I’ve downloaded putty (Windows XP) and established a ssh connection. Then i login with admin and password admin to get to root dir. Then i’m stuck.
    Please can someone help me. TIA !

  8. Point7
    Posted November 21, 2008 at 4:17 pm | Permalink

    OK, problem solved. My 109 is now a 109 PRO. I changed the 0055 setting to 0099 in the hw_type file. I used the combination of Putty (for mounting) and WinSCP (for editing). Reflashed the firmware with the latest PRO version 2.1.2 build 1114T and now I can see NFS access in the control panel.

  9. vphan
    Posted November 25, 2008 at 9:15 am | Permalink

    You officially roxor x2 this works too (Method 1) Method 2 did not work for me even after flashing. The hw_type file already had 0099 as its contents. My model is the TS-209 1 non-pro version

  10. Posted December 1, 2008 at 3:32 am | Permalink

    #Q1: I have planned to purchase TS-209 in order to save round 100 euros comparing to TS-209 pro or TS-209 II. Is it possible to “upgrade” std. 209 to 209 Pro? The product looks good enough, but the NFS support will be make life easier with my linux based satellite receiver. Are your instructions applicaple also for 209?

    #Q2: There is “smart fan” feature in QNAP products. Does it really work? – I mean lower noise when idle. Is there “spin-down” feature option in software to make NAS quiet?

  11. Posted December 5, 2008 at 12:33 am | Permalink

    @Mr.HH,

    A1: I think it’s the same for 209 because the only difference between a 209 and a 209II is the memory (128MB vs 256MB).
    A2: Check the official forum, you’ll find plenty of info on spin-down feature, I personally didn’t try it because my NAS has been busy downloading stuffs :)

  12. Hank
    Posted December 5, 2008 at 1:58 pm | Permalink

    Where should autorun.sh be? I don’t see it anywhere on the drive after using WinSCP to ftp into it.

    This is for a 109 II model

    I guess it might help to explain the steps a bit more?

    Any help would be appreciated.

    Thanks

  13. Hank
    Posted December 5, 2008 at 2:13 pm | Permalink

    Well, after digging a lot more, I learned how to use the #vi command, but autorun.sh STILL doesn’t exist. I tried creating one using WINSCP…it showed up, but is EMPTY, which I’m guessing it’s correct.

    Tried using the empty one, editing it to show the lines above using Putty (#vi), but still no luck.

  14. Hank
    Posted December 5, 2008 at 2:14 pm | Permalink

    Ever have one of those days?

    3rd time is a charm apparently. Worked after at third try with the #vi command via putty.

    Thanks for the great hack!

  15. JB
    Posted December 10, 2008 at 8:47 am | Permalink

    None of the methods worked for me on a TS-109 II with version 2.1.2 1114T. So what I did was:

    1) use a program called WinSCP and login in SFTP mode. Make sure you use your admin account.
    2) Now go to tmp/hw_type.
    3) Right-click >> edit >> this file should be empty. Just add 0099 to it and save. Close the file.
    4) Reboot by logging into the Web Interface from your broswer >> Administration >> System Tools >> Restart/Shutdown (left menu) and restart the system. It should take approximately 5 minutes. After a series of beeps the web interface will auto-log you back into the web interface. Go to home page of your Web Interface and you should see your TS-109 II is now a pro.

    Why there was 2 versions? Money grab. It’s a $100 difference here in Canada.

    Thank-you George for the help. =]

  16. Hugh
    Posted December 11, 2008 at 3:26 am | Permalink

    I try the first methode on my TS-209II 2.2.2 1113

    I reboot and now nothing work. A few time after restart, there’s 2 bip and then nothing. It’s impossible to connect with ssh telnet or the web interface.
    My nas is now out of work.
    What else can I do now?

  17. JB
    Posted December 11, 2008 at 5:45 am | Permalink

    Hugh,

    Either:

    1) Press and hold the reset button behind your NAS and try booting again.

    2) Or, alternatively, download/open the QNAP Finder utility (it can be found on their website or the CD) and reload the latest firmware.

    Good luck.

  18. Sol
    Posted December 13, 2008 at 12:51 am | Permalink

    Great stuff! Even I bought the Pro…

    Here’s another thing you could investigate: I’d like to install Debian on the Qnap. The only thing which bothers is that the Twonky Media won’t work because the license is missing.
    So maybe there’s a hack you can find to make it work?

  19. FL
    Posted December 28, 2008 at 6:51 pm | Permalink

    George,

    I am new to Mac and Linux and have two questions for you:

    1. I have tried to follow you instructions above, but how can I edit the autorun.sh file?

    2. Can you direct me to a site where I can read about, how to setup my TS-209 II with all its functionality in an environment with a MacBook Pro and a MacBook?

    Greeatly appreciaated

  20. Craig
    Posted January 5, 2009 at 3:04 pm | Permalink

    Thanks for the tip!
    The first method mentioned worked perfectly on my TS-109.

    I now have the missing NFS I was so hoping for.

    Thanks again.

  21. Posted January 9, 2009 at 7:57 am | Permalink

    @FL,

    1. you may ssh to your NAS and edit the file with vi
    2. you configure all the settings through the web interface, a good start is the product manual

  22. Andrea
    Posted January 13, 2009 at 4:30 pm | Permalink

    have you ever tried to install Qnap firmware on a different hardware? for example on the Intel Storage ss4200?

  23. JB
    Posted January 23, 2009 at 8:49 am | Permalink

    The BETA 3.0 Firmware on QNAP’s forums now incude NFS for the TS-209 II.

  24. torres
    Posted January 24, 2009 at 1:54 pm | Permalink

    And Active Directory support? Is this feature also included with the TS-209 und Firmware 3.0?

  25. Peter Hyde
    Posted January 31, 2009 at 11:59 am | Permalink

    I have a TS209 II running Version 2.1.3 build 1217T and tried your Method 1 and method 2.

    With Method 1, it all seemed to work fine, NFS appeared in the menu as you said it should, except on restart everything reverted to the non PRO version.

    Changing the hw_type to 0099 and restarting had no effect. The hw_type was reset to 0055 by the system.

    What next??

    rgds
    Peter

  26. aki
    Posted February 4, 2009 at 8:42 am | Permalink

    Hello, with the 2nd method, after the reflash it’s works.
    It’s not write TS-209 “pro” but NFS option exist now !
    Thank you very much !

  27. Posted February 6, 2009 at 9:01 am | Permalink

    @Peter Hyde,

    For method #1, the change is not permanent, you have to do it after every reboot, that’s why I put that into the autorun.sh.

    For method #2, the change is permanent, however, sometimes the trick may not work, I don’t know why. From what I have tried, I can’t make it work on previous firmwares (before 1031T). To make it work, I first use the first method to change system type, then upgrade firmware to 1031T and it suddenly becomes PRO even without any patch in autorun.sh.

  28. Josh
    Posted March 1, 2009 at 12:57 am | Permalink

    Genius. Nice work thanks for the tip.
    Happy to know I’ve saved the money but can get the functionality if needs be.

    Next stop; trying to get Tortoise SVN server version control running on it :D

  29. Posted March 1, 2009 at 1:10 am | Permalink

    @Josh, subversion server is easy to install, get optware installed first, then you may use ipkg to install svn server. The startup script may need to be tweaked because you may need to chroot before firing up the svnserve, otherwise it’ll complain about the library things.

  30. jurgen
    Posted March 16, 2009 at 6:01 am | Permalink

    Hi, great hack. BTW all I did is:

    mount -o loop /dev/mtdblock5 /tmp/config
    cd /tmp/config
    cp hw_type hw_type_old
    vi hw_type
    Replaced 0055 with 0099 save, quit & reboot.

    Changed my 209 to a 209 pro. Cool!!!

  31. bent
    Posted March 26, 2009 at 5:17 am | Permalink

    Create the autorun.sh file

    # mount /dev/mtdblock5 -t ext2 /tmp/config
    # cd /tmp/config
    # vi autorun.sh

  32. AG
    Posted April 6, 2009 at 8:49 pm | Permalink

    Thanks for this HowTo!

    I’ll try this today on my TS-209 (non-II).
    Do you have some more info about this procedure?
    What will be the hw_type file content for TS-209 PRO (non-II)? Is it same as on II?
    You said that many people tried this already. Can you send me a link per e-mail on discussions?
    Do you know if this method works with TD-409? I wanna buy one soon. :-)

    Thanks!

    Ich

  33. Budgie
    Posted April 13, 2009 at 1:21 am | Permalink

    Awesome tip dude! Just “upgraded” my TS-209 into a PRO version!

    I tried the 2nd method first but had no joy so I set my hardware using the following:

    mount -o loop /dev/mtdblock5 /tmp/config
    cd /tmp/config
    ln -s /sbin/config_util /sbin/set_hwtype
    /sbin/set_hwtype 2

    Then once done I flashed the latest PRO 2.1.4 build 0318T onto the NAS and it was all good.

  34. cdb
    Posted April 23, 2009 at 12:43 am | Permalink

    Has anyone tried this on the QNAP 409? Know if it will work?

    I’m interested in purchasing one, but not willing to pay an extra $150 for the pro version. Any feedback would be appreciated.

  35. pete
    Posted May 12, 2009 at 4:35 pm | Permalink

    Hi guy,

    thanks for your hack – it works fine for me with the 2.x firmware.
    But what about the new upcoming 3.0-Firmware release? This would bring some great new features like automatic ip blocker…
    But it seems that your hack doesn’t work for the new firmware – could it be that they have changed the hwtype-values?

    if I mount the mtdblock5 and cd, there is the autorun.sh file and a file called “hw_type”:

    [/tmp/config] # cat hw_type
    0055

    on a TS-209 Non-Pro with the latest beta release of the Firmware (3.0.0 T0430).
    Any ideas?
    :-)
    Greetings, pete

  36. Posted May 12, 2009 at 4:53 pm | Permalink

    @pete, well, I didn’t check the 3.0 firmware because it’s still in beta and any change could happen before it turns into final, so I’ll wait till it’s out of beta and give it a try.

  37. Pete
    Posted July 9, 2009 at 12:19 am | Permalink

    Hey George,

    I#ve good news for you.
    The v3.1.0 Build 0708 firmware for the QNAP TS-109/209/409 (II) is out now. You can download it from the official qnap.com download section.

    And the best thing: I “upgraded” my TS under the old firmware (2.1), then updated to new brand new one – and the NFS service is still available!

    Greetings, Pete

  38. mattwalker
    Posted July 18, 2009 at 6:50 pm | Permalink

    Very happy! I tried this on my TS409. I am now the proud owner of a TS409 Pro!!! — I bought it thinking I could use it without the NFS (I own a Tvix) and was disappointed to find it was a little slow and that I could not update my box to include this feature. Everything else about this box for me is spot on and this was a niggly little item that was annoying me.

    I am a complete newbie when it comes to linux and even I was able to follow the instructions and get it working first go.

    Kudos to you Gearge Zhu….Kudos to you!

  39. mattwalker
    Posted July 26, 2009 at 7:48 pm | Permalink

    OK…whilst it works it doesnt stay working :(

    After a reboot it disappeared but after re inputing the steps we are away again.

    My question is: Is there a way of making it a little more permanent?

  40. Posted July 27, 2009 at 5:36 pm | Permalink

    @mattwalker, that’s weird, as it IS permanent for me and many other people, and it stays effective even after I upgraded the firmware to the latest version 3.1.0 build 0708T.

  41. Román
    Posted August 4, 2009 at 3:22 pm | Permalink

    Does it work with branded new TS-409?? Thank you very much for this trick!

  42. orait
    Posted August 18, 2009 at 9:43 pm | Permalink

    Thank you very much for this! This is what I did (as explained above) to change my new TS-409 to TS-409 Pro with the newest firmware 3.1.0 build 0708T.

    mount -o loop /dev/mtdblock5 /tmp/config
    cd /tmp/config
    vi hw_type
    Replaced (“i”) 0055 with 0099 save, quit (:wq) & reboot.

    After reboot I have both NFS service and Windows AD service accessible.

  43. knf
    Posted August 22, 2009 at 2:08 am | Permalink

    I got my 209 II today and I have firmware 3.1.0 Build 0708T installed. I was manually enabling nfs by starting up /etc/init.d/nfs. Then I came across this site. Coolest thing ever, I followed method 1 and it DOES work!! I have NFS now thanks to you guys!

    One thing I saw no one mentioning, is that when I did a showmount -e , I notice the shares are named after /Qdownload, etc. To actually mount it, I need to mount :/share/MD0_DATA/Qdownload. Hope that’s useful.

  44. mrc99
    Posted January 24, 2010 at 2:31 am | Permalink

    and it’s work ok on ts-109 pro
    :)

One Trackback

  1. [...] specs – there are 2 differences in software, those being the 209 Pro II supports NFS and AD Hack here to turn a 209 II into 209 Pro II Or pay an extra

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

*
To prove you're a person (not a spam script), type the security word shown in the picture. Click on the picture to hear an audio file of the word.
Click to hear an audio file of the anti-spam word

Site hosted by