Upgrading the Synology 106e firmware to to 3.1 (And 3.2)

I own one of the first Synology NAS’s ever made, the 106e. Synology stopped the development of new firmware for this model a few years back, but because many of the Synology devices are based on the same hardware it is still possible to upgrade the 106 series to higher than supported firmware. This article will tell you in detail how to do this.

First of all. A disclaimer:
I didn’t figure all this out myself. All credits should go to the active people on the Synology forums, especially Goetz. All I did was to spend 8 hours figuring out how to collect all this info into one single text, and write it in a way that should be easy to understand if you know just a bit about Windows but perhaps not so much about Linux, telnet etc.

Upgrading the firmware to these versions is NOT supported by Synology and it will void your warranty.
You CAN loose all data on the disk easily, and it will not be easy to bring them back unless you know a lot about linux operating systems, have some sort of USB-SATA converter, and an extra pc for this job.
I should also tell you that you might end up with a broken device that you will never be able to fix again. (Even though I believe myself that you can always bring it back to life just by clearing all partitions on the hard drive.)

These steps should work for the 106x the 106j too, but I don’t have those devices and I am therefore not 100% sure.

Alright, with that out of the way lets get busy with the upgrade.

Step 0 – Backup and deletion of all partitions.

This step is optional, but it might benefit you later. Depending on when you bought your device, and the size of the disk you use, the system partition may be too small to upgrade all the way to 3.1. The requirement is somewhere around 350MB, and I noticed that, when I did a complete reinstall on a 320GB disk, that newer versions of the Synology Assistant and firmware, will create a 2.5 GB system partition. This leaves plenty of room, and you will not need to mess with moving partitions around later.

The step simply consists of you doing the following:

  1. Take out the hard drive from the Synology device.
  2. Connect it to a pc. (Either using some inbuilt ports, or use a USB-SATA converter.)
  3. Delete all partitions on the drive. (If you use Windows you can use the Disk Manager to do this. Just make sure that you don’t delete your pc’s drives instead. If you don’t have a clue about what you are doing, then leave this step to someone who does.)
  4. Disconnect the drive, and insert it into your synology device again.

Step 1 – Installation of official firmware

Using the Synology Assistant and the latest official firmware, install the device so it actually runs and can display the web interface. Don’t set up all kinds of shared drives, photostation etc. yet, because you’ll go through a lot of configuration later. And… as always when dealing with firmware upgrades – Keep it simple!

Step 2 – Installation of hacked firmware Version 959

EDIT 30 july 2012: You can simply skip this step, and it will still work. So.. move on to step 3. (My guess is that it’s also possible to skip directly to DSM 4.0 by telling the Synology that it’s a 108j in the synoinfo.conf. Like in step 4.)
Thanks goes to James for testing this out.

EDIT 29 july 2012: Since 1. July 2012 this step no longer works. The links in the forum post are dead since the site file-upload.net apparently did a relaunch, making the files unreachable by the old links :-(
If you happen to have these files somewhere, let me know ;-)

Back in 2009 Goetz created a version of the 959 firmware that will upgrade just as if the firmware came directly from Synology.

  1. Download it using the links in this post on the synology forums.
  2. Upgrade the firmware using the Synology Web interface. (Do not use the Synology Assistant.)

You now have some extra functionality like DNLA, and SSL for FTP connections. This is a must have upgrade :-)

Step 3 – Installation of firmware 1139 (Disk Station Manager 2.3)

The 106 series and the 107 series use the same CPU, so some clever guys on the Synology forums figured out that it was possible to cheat the web firmware upgrader into thinking that the device was a Synology 107. This enables installation of the firmware for the 107, which was still officially supported at the time. To do this you follow these steps:

  1. Enable the telnet service on the Synology. You can do this from the web interface.
  2. Get a “terminal program” so you can connect to the Synology via telnet. You can use a program such as Putty to do this.
  3. Log in as root NOT admin. Root and admin share the same password, but if you log in as admin you might not be able to save the file we need to edit.
  4. The Synology telnet is not exactly userfriendly, but when you log in you are located in the folder /root. You need to navigate to the /etc.defaults folder. This is easily done by typing:
    cd ..
    cd etc.defaults

    Make sure you go into etc.defaults and NOT just etc. Both directories will look the same, and have a synoinfo.conf file… but it will not work if you edit the wrong one. (I spent 3 hours trying to figure this out… )

  5. Edit the file synoinfo.conf. This can be done using the built in editor vi. Simply type:
    vi synoinfo.conf

    to start the editor.

  6. Now… vi is not exactly the most typical editor so you might end up with some troubles here. A quick guide is:
    • The vi editor has a command mode, and and input mode.
    • You switch to input mode by pressing the i key.
    • When you are in input mode everything you type is inserted as normal into the document.
    • You go back into the command mode by pressing escape.
    • The cursor keys navigate the document.
    • The x key will delete characters under the cursor when you are in command mode.

    You need to change the first line from:

    unique="synology_powerpc_106e"

    into

    unique="synology_powerpc_107"

    So, first, position the cursor on the number 6. Press the x key twice to delete the “6e”.
    Press the i key, and enter a “7”.

    Now, to save the file, make sure you are in command mode (Press escape if in doubt.) and type:

    :wq

    This tells vi to write and quit. If you messed something up just type:

    :q!

    and the editor will quit without saving. Then start over by typing vi synoinfo.conf again. (Usually you can just press the cursor up key, and then enter, to reissue the command.)If you need more help with vi it might be helpful to read the Mastering the vi editor guide.

  7. Now you can exit the telnet session again if you want. Just type exit and the connection will close.
  8. Now your Synology device will think its a 107 model. This enables you to download the firmware for the 107 and apply it using the web interface just as usual. The firmware can be downloaded from Synologys own download site.
  9. When the upgrade is complete you need to make a few changes again. Since your device is not really a 107 you need to change a lot of stuff in the synoinfo.conf to no. Repeat step section 3, 4 and 5 to edit the file again and change the following lines:
    upnpmodelname="DS107" --> "DS106e"
    supportsystemperature="yes" --> "no"
    showtempdesc="yes" --> "no"
    synobios="ds107" --> "ds106"
    supportdomain="yes" --> "no" (optional)
    supportfanctrl="yes" --> "no"
    support_auto_poweron="yes" --> "no"
    support_mtd_serial="yes" --> "no"
    surveillance_camera_max="2" --> "1"

    Notice that you DON’T change the first line(the one with unique) again. Your device must still think that it’s a 107

  10. Now log into the web interface and do a reboot before you do anything else. Othervise you might end up with seeing things in the web interface that are not really working on your device.

Now you are at the 2.3 interface. It’s fairly close to the earlier one, but the important thing is that you are now able to upgrade to 3.1.

Step 4 – Upgrading to 1748 (Disk Station Manager 3.1)

This step requires that you have more than 350MB available on the system drive. You can check this by logging in via telnet and typing the command “df -h” (It will issue the disk free command showing you human readable numbers.) This is what it looks like on my device. /dev/hda1 has plenty of room.

Nas> df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/hda1                 2.3G    464.3M      1.9G  20% /
/tmp                     14.7M    344.0K     14.4M   2% /tmp
/dev/hda3               290.5G    196.1M    290.2G   0% /volume1

If everything is fine you can upgrade to 3.1. But of course things are never just that easy… :-D

At this point the 107 series is not supported anymore, but fortunately the 108j was. So like in step 3 you need to:

  1. Log into your Synology device via telnet. And edit the synoinfo.conf’s first line from:
     unique="synology_powerpc_107"

    into:

    unique="synology_powerpc_108j"
  2. Get the firmware for the Synology 108j from synologys download site.
  3. And apply it using the web interface.
  4. Again, after the update. Edit the synoinfo.conf again, and disable the same things as in Step 3.9. However this time you will notice that you might be missing some of the lines. I didn’t worry about this and everything seems to work alright.
  5. Again, do a reboot before you start setting up the Synology.

You should now have the most recent firmware possible on your Synology 106e.

EDIT 2012-01-19: Warning. Updating to 3.2 seems to work, but some process that has to with the LED’s keep writing error messages in the log every few seconds. A fix for this is found in the comment section, but since those were written Synology has removed the beta file required for that fix to work :-/  The files in the newer beta file (For 4.0 ) do not work as a fix but will mess up your system making it unable to start.

 

EDIT 2011-09-04:  An even higher revision was just released, and according to Tormods comment below, you can use the file DSM_DS-108j_1869.pat to update all the way to 3.2
If you’re doing a complete reinstall, my guess is that you can simply use that file instead of the file in step 4 and go directly to 3.2, skipping 3.1 altogether.

 

A few things might surprise you if you are used to the old firmware:

The new interface has a completely new look.
There is now a section called Application privileges that you need to use to allow users (other than admin) to access the audiostation, downloadstation etc.
User management is now way easier, but you might mess it up because it is a bit too easy to forget about user-groups.
Audiostation, filestation and photostation have been given an overhaul so they are actually useful now.

I hope you made it all the way and sit right now and enjoy bringing some old hardware up to date. I know I do ;-)

100 thoughts on “Upgrading the Synology 106e firmware to to 3.1 (And 3.2)

  1. Thanks, this is a very well written guide. :)
    I don’t have a 106 but I’m definitely bookmarking this for when my 209+II goes out of support. There is a compatible processor in the 210+. :)

  2. Thanks for the great guide, just installed DSM_DS-108j_1869.pat onto my DS106e – so I’m running DSM 3.2 beta as we speak (OS X Lion is supported now!)

  3. Very well written guide and easy to follow. A great thumb-up to you. I have a DS-106 running on DSM 2.2-0959 now. Will bookmark this when I’ve decided to upgrade in the future.

  4. Thanks for this great guide, just installed on an old DS101G+ (Transformed first into a DS106e) DSM 3.2 1922 (In Step 4, I use DSM_DS-108j_1922.pat instead of DSM_DS-108j_1869.pat or DSM_DS-108j_1748.pat).

  5. Amazing guide. So thankful I tried this on a temp drive while 1tb was being repaired. Just wondered what happens when old drive comes back. All upgrades done except first through web interface but when new drive is in it will be through synology assistant. Just wondered which firmware I will have to put on it. Many thanks

    • When inserting a new (or in your case an “old” drive) all changes will be gone. The synology “firmware” is really an operating system, and not so much firmware (A term more often used for something that is “burnt” onto a chip on the actual device.)
      So you’ll probably need to use Synology Assistant for the first install, and then just follow the guide to add the “hacked” updates.

  6. Thanks. I tried today without a drive and I was able to see it showed 3.2 on it. I then inserted a fresh drive and it allowed me to go straight to an DS108J on 3.2 on my DS106e Nas. Myself and a friend have used your guide in the last few days and updated our Nas’s. Your guide is well written and gave all needed advice. Many Thanks

  7. Well done !
    It’s very clear and easy. My 106J is now 108J with the last update DSM 3.2
    But now I don’t know if it’s able to work. Tonight maybe.
    I have only one problem. I never be able to edit after installing 1139 for DS107 /etc.defaults/synoinfo.conf. I tryed later when I change to DS108J but it has been the same.
    Only I can see that :
    DiskStation> cd ..
    DiskStation> cd etc.defaults/
    DiskStation> vi synoinfo.conf

    unique=”synology_powerpc_108j”
    company_title=”Synology”

    # system options
    timezone=”Pacific”
    language=”def”
    maillang=”enu”
    codepage=”enu”
    defquota=”5″
    defshare=”public”
    defgroup=”users”
    defright=”writeable”
    eventsmtp=””
    eventmail1=””
    eventmail2=””
    eventauth=”no”
    eventuser=””
    eventpass=””
    configured=”no”
    admin_port=”5000″
    secure_admin_port=”5001″
    pswdprotect=”no”
    supportweb=”yes”
    supportphoto=”yes”
    support_download=”yes”
    supportmysql=”yes”
    supportquota=”yes”
    supportitunes=”yes”
    supportddns=”yes”
    supportfilestation=”yes”
    supportssl=”yes”
    supportssh=”yes”
    supportHTTPS=”yes”
    supportNFS=”yes”
    supportrsrcmon=”yes”
    supportmemtest=”yes”

    # service options
    runsamba=”yes”
    runapple=”yes”
    runftpd=”no”
    ftpport=”21″
    syslogport=”514″
    – synoinfo.conf 1/185 0%

    I am sorry !

    One more thing. I didn’t find how to expand the size of my root partition. I didn’t need it, but I’d like to know if it’s possible with a Mac.

    Realy nice work !

    JLuc

  8. thank you for this guide. i’m upgrading my 106j in 107 and tomorrow in 108j.
    By the way the 108j has vpn support ?

    @jluc If you have to modify the partition just open your synology and link it to a pc to change the partition. I did it and tooks me a 8 hours.

  9. @jluc **If you have to modify the partition just open your synology and link your hard disk it to a pc to change the partition. I did it and tooks me a 8 hours.

  10. Many thanks for this guide.
    I have a problem: after installing the firmware named DSM3.1-1748 for DS108j, I realized that my external eSata disk was no more recognized by DS106e! unable to see the shared directory “satashare” as usual before. Along the different steps of upgrading, It well worked until DSM2.3-1139 for DS107.
    So, I wonder if the DS108j configuration is the good choice for me because DS108j does not physically support external disk with eSATA connection.
    Do you have an idea. Does another firmware version could be more accurate, from DS109 or DS110+ for example?

  11. My partition ran out of space! Do you have any suggestions without wiping the whole disk and starting again (which will create the same problems…)

    /dev/hda1 341.8M 290.5M 51.3M 85% /
    /tmp 14.7M 352.0k 14.4M 2% /tmp
    /dev/hda3 366.1G 323.6G 38.8G 89% /volume1

    • Well.. you should be able to put the disk into a pc, and then use some sort of partition management tool. But since this is a dangerous operation you’ll need to back up your data first. Even if you skip this step it can take an extremely long time to move data around and then extend the partition.
      Really.. since a backup is always needed, you’re better off just copying all data to somewhere else and then wipe the drive.

      I don’t understand why you should end up with the same problem if you wipe the drive? The newer versions of Synology Assistant makes a huge partition for the very first install.

  12. Hi,

    My HDD get over, so i changed it and reinstall full DSM 3.2.1955 of the 108j …

    https connections can’t be etablished and return Invalid Certificat, any idea ?

  13. Damned, i made a big mistake. I rebooted directly after 3.9. Now my config thinks it is a 107 (it is a 106j). After rebooting the installation is interrupted: the diskspace is inufficient. What to do?

    • I don’t think thats possible. But you want to do this because you want to restore settings, you can use the “settings backup” thats built into the control panel of the more recent versions of DSM.

  14. Following all the procedures described on the synology forum and on this blog, I upgraded my DS-106e to DSM 3.2-1955 (the one for the DS-108j).

    After reboot, everything seems to works, except /var/log/messages written every 4 seconds with “modules/led.c:82 unexpected LED behavior”.

    To solve this problem, with 3.2-1955, replacing /usr/syno/bin/scemd by the /usr/syno/bin/scemd from 3.2-1869 (beta) is not enough.
    I try to replace /lib/modules/synobios.o too, with the version from 3.2-1869 (beta) and this solves the LED problem.

    My “synobios” argument value in /etc.defaults/synoinfo.conf is “ds106″

    Note: I didn’t tried hibernation or eSATA. I don’t know if these features are still working with this files. I m currently testing that everything is working. Use this procedure with caution.

    • Well in order to replace the syn I had to force the overwrite
      cp -f /usr/syno/bin/scemd
      Just trying a reboot now, which takes an absolute age in comparison to the previous 106e software versions.
      One thing I do notice is that the status LED is no longer working and the HDD LED is near enough permanentely on until you

      I can confirm that at least the 1955 version at least lets you use USB drives. I will check with eSATA later on and let you know if there is any problem

    • Well in order to replace the syn I had to force the overwrite
      cp -f /usr/syno/bin/scemd
      Just trying a reboot now, which takes an absolute age in comparison to the previous 106e software versions.
      One thing I do notice is that the status LED is no longer working and the HDD LED is near enough permanentely on until you

      I can confirm that at least the 1955 version at least lets you use USB drives. I will check with eSATA later on and let you know if there is any problem

  15. Thanks a lot for this !
    For information after reading EDIT 2011-09-04 (step 4) I did an upgrade from DSM 2.3-1139 to DSM 3.2-1955. No issue until now.

  16. Thanks for the guide! Finally got my DiskStation to be an OS-X Time machine again.

    By the way, I went from 2.2 straight to 3.1 on a DS106j without repartitioning or anything and all seems to work fine. Not sure whether I will go to 3.2 though as it all seems to work okay now and does what it’s supposed to do…

  17. Thank you very much for this very usefull guide. It allowed me to upgrade my DS-106j to DSM 3.2 and use the DS audio app on my new iPod touch. Very good guide. I had some small trouble at some points, but in the final it worked. The best thing to do, in my case, was to start by removing all the partitions from the disk.

  18. Hello!

    Thank you for this wonderful guide! I updated my old ds101g+ now to the ds107 DSM 3.1-1636. Really Nice. Very much thanks for all your tipps! Now i am thinking about to upgrade to the DSM 3.2. Do you think its possible with my old 101g+ device or is it better to stay at DSM 3.1???

    Stefan

  19. DSM_DS-108j_1869.pat isn’t available on the synology beta site. Can anyone tell me where i can find the files needed to correct the led problemens?

  20. Hi,
    As requested by Axel
    I have updated my syno ds106e/dsm3.2-1955 with the files /synobios.o and scemd from DSM_DS-108j_1869.tar (beta).

    That’s perfect, I have no more the “modules/led.c:82 unexpected LED behavior” in /var/log/messages written every 4 seconds.

    Thanks

  21. Damned, i made a big mistake. I rebooted directly after 3.9. Now my config thinks it is a 107 (it is a 106j). After rebooting the installation is interrupted: the diskspace is inufficient. What to do?

    Have any idea?

  22. Hi all,
    I have 101g+ with DSM 3.1-1636 from 107.
    Now I am thinking about upgrade to the DSM 3.2. eSATA is working on DSM 3.2-1955 with add hotplug and hotplug.d from last 107.pat?

  23. so – if i go to 108j and the latest DSM is 4.0 – is that going to work or should i stick to 3.2? thank you

    • Well.. I installed 4.0 beta on my 106e, so 4.0 will probably install, if you got 3.0 or higher on it now.
      But I haven’t really used it for anything yet, so I don’t know if it actually runs ok with 4.0. There might be some errors that need fixing, like there was in 3.2.

  24. oki – installed 4.0 latest 108j DSM from Synology – only pre-req was 3.2 – so did the 1955.pat version (last 3.2 for 108j) – all working – but…. v sloooww…. shame: because its quite a nice new skin they have added. Got the ZyXEL 310NSA incase things went pete-tong.. they havent yet: but syno iphone apps not working (time out i think…).
    i think i read you can now setup seperate photo websites based on user login – which is nice – but cannot play movies on a website yet…

  25. S*+t, I have a problem. In step 3 after changing the synoinfo.conf file to “107” I rebooted. Or rather I tried to reboot before updating the system. System is hung now… any advice on how to get out of this??

    Thanks, Chris

    • In some cases where I’ve messed it up (and the system couln’t be reached via the admin interface), I was able to run the synology assistant and make it find the NAS.
      The assistant would then say: “Not initialized” or “System not installed” or something like that. I would then pick the latest .pat file that I had put on the NAS and then install it. The data was still there in my case.
      In fact I think that it does check the version, so you might need to install the next .pat file, eg. one that can be used on a DS 107. The assistant will tell you something like “The PAT file needs to be compatible with 107″ or something like that, if you pick the wrong one.

      • Ok well I did think about doing it that way, however what I ended up doing was the following.
        1. Removing the SATA drive from the ds106e
        2. Connecting the SATA via an external disk drive to Windows 7
        3. Installing ext2fsd with patch (for ext4)
        4. mounting drive and editing (via notepad) the synoinfo.conf file
        5. disconnect / shutdown the external drive
        6. rebuild the SATA drive back into the ds106e
        7. Reboot the ds106e and start back at step 3 again

        I quite simply didn’t trust the synology assistant to do a quick fix I guess!

  26. Hi,
    I’ve succesfully updraded my DS-106e to DSM 3.1-1748.
    I’m using an esata backup and i can’t manage to copy the hotplug files using “goetz” cmd lines
    i’ve extracted usr/syno/hotplug and hotplug.d from last 107.PAT and copy it on my “public” folder but this code:

    cp /volume1/public/pci.* /usr/syno/hotplug
    cp -r /volume1/public/pci /usr/syno/hotplug.d

    is not working for me (don’t understand the “/pci.*”) (i’m not very confortable with command lines and path :)

    Thanks

    • The * in the pci.* is the so called wildcard. i.e. it will copy everything that starts with pci. from a-z and whatever else is listed there. you can try an ls pci.* in the directory to see exactly what will be copied

  27. I actually upgraded my DS106 to the newest firmware/ software DSM4 using this method but am also having the issue with the status light, will the method in this thread work?

    and also more importantly I’ve lost USB Audio functionality anyone else have any experience with USB speakers?!

    thanks for your help!

  28. Can someone tell me if after upgrading to 3.1 or 3.2 via this method, does the 106e support large harddrives? (ie. 2tb and 3tb)

    Or is that in fact a hardware limitation.

    • I was running my 106j with 1.5Gb SATA HD using a IDE_TO_SATA converter for almost 2 years now with the 959 version.
      No problems, only SMART-test is telling me there is something abnormal.

  29. Could you tell me how to obtain this firmware, as from you article writen that, it is must to have DS-106e_0959.pat installed before step 3.

    thanks

  30. Editing the “etc.defaults” file can be much easier if you install the 3rd party package “config file editor” available at http://www.mertymade.com/syno/#cfe
    You will have to edit it’s own config first and add the location and name of “etc.defaults/synoinfo.conf”.
    Once you have done that restart the package, start it, and select the “etc.defaults/synoinfo.conf” file and edit away (it’s very easy).

    I managed to upgrade my 106j in two steps without data-loss from the 959 version to DMS 3.2-1955, and directly after that to DMS 4.0-2228. I just renamed 106j to 108j in “etc.defaults” and upgraded as you would normally upgrade from Synology website.

  31. I forgot:
    you must upgrade to DMS 3.2 first, the upgrade programm tells you to if you try to upgrade to DMS 4.0 and youre firmware is not at least DMS 3.2.

    I didn’t change back any lines as mentioned under 3.9, so it’s still running as a 108j with all options.
    It seems a littlebit faster than when running the 959 version, only booting is much slower.
    DS-106j is still running without any problems with DMS 4.0-2228.

    DOES ANYBODY KNOW (anybody tried?) if this trick is also possible for my DS-207+ ???
    If possible I want to upgrade my 207+ to DMS 4.0 also… maybe anybody just can tell me which compatible model to choose ?

    • Ive just upgraded to dsm 4 on 106e and … it works but its a bit slower because of the memory i think ill have to go back to 3.2

  32. Upgraded my 106j from DSm 4.0 to DSM 4.1, it’s running fine.
    changed the model to 109j in “etc.defaults/synoinfo.conf” and did a manul upgrade.

  33. Well, good …
    I turn my old DS106 under 2.2 to 4.0. Everything seems to work well, except the external Sata (Satashare) … Any idea ? Please a little help …

    And what about the 4.1 ?

    Thanks a lot

  34. Great instructions ! and many of the followup comments and replies helped too!
    I just upgraded my DS-106e. Because of an error message about DSM 2.2 being required I moved up in 3 steps, first 107_0959, then 107_1139 and finally to 107_1636. By using the 107 version of DSM 3.1 I was able to keep my eSATA drive working.

    I found the page on the Synology web site titled “What kind of CPU does my NAS have” and see that the DS-109j has the same powerpc processor as my 106e. There is a DSM 4.1_2647 download that I might try next. However the DS-109j only has exteral USB ports, no eSATA port so I would expect to lose that capability if I go to that 4.1 version.

    Any thoughts on the performance I would get with 4.1 running on a 106e with only 32mb of memory?

    • I Try to go to DSM4.1, but I failed. When I change the file Synoinfo.conf : 108j, -> 109j, save, and then restart the Syno,the Syno not restart (blinking of the status led on orange, and seems to be freez).. So i return back to 4.0. Do you have tried? Is it functioning?
      Thanks.

  35. Just to say thank you…

    This is a clear version,

    Step 1 – Installation of official firmware

    Install synology_powerpc_106_0731.pat Using DSAssistant

    Step 2 – Installation of hacked firmware Version 959

    Upgrade DS-106_0959.pat using the web interface

    Step 3 – Installation of firmware 1139 (Disk Station Manager 2.3)

    vi /etc.defaults/synoinfo.conf
    unique=”synology_powerpc_106e” -> “synology_powerpc_107″

    Upgrade synology_powerpc_107_1139.pat using the web interface

    vi /etc.defaults/synoinfo.conf
    upnpmodelname=”DS107″ –> “DS106e”
    supportsystemperature=”yes” –> “no”
    showtempdesc=”yes” –> “no”
    synobios=”ds107″ –> “ds106″
    supportdomain=”yes” –> “no” (optional)
    supportfanctrl=”yes” –> “no”
    support_auto_poweron=”yes” –> “no”
    support_mtd_serial=”yes” –> “no”
    surveillance_camera_max=”2″ –> “1”

    reboot

    Step 4 – Upgrading to firmware 1955 (Disk Station Manager 3.2)

    df -h
    check >350MB

    vi /etc.defaults/synoinfo.conf
    unique=”synology_powerpc_107″ -> “synology_powerpc_108j”

    Upgrade DSM_DS108j_1955.pat using the web interface

    replacing /usr/syno/bin/scemd (DSM_DS108j_1955.pat) by the /usr/syno/bin/scemd from (DSM_DS-108j_1869.pat)
    replacing /lib/modules/synobios.o (DSM_DS108j_1955.pat) by the /lib/modules/synobios.o from (DSM_DS-108j_1869.pat)

    vi /etc.defaults/synoinfo.conf
    upnpmodelname=”DS107″ –> “DS106e”
    supportsystemperature=”yes” –> “no”
    showtempdesc=”yes” –> “no”
    synobios=”ds107″ –> “ds106″
    supportdomain=”yes” –> “no” (optional)
    supportfanctrl=”yes” –> “no”
    support_auto_poweron=”yes” –> “no”
    support_mtd_serial=”yes” –> “no”
    surveillance_camera_max=”2″ –> “1”

    reboot

    You can get the DSM_DSXXXX_XXXX.pat FROM GOOGLE!

  36. Thanks for this guide. I succesfully upgraded my DS106 with original firmware (very old looking!) to 3.1 However, step 2 could not be skipped in my case. After uploading the firmware from step 3, DSM complained that it needed 2.2 in order to upgrade. Furthermore it wracked everything so it couldn’t even boot and Synology Assistant couldn’t talk to it. Not a big deal, I just took out the HD and deleted all partitions and started over, this time applying step 2. The special modded file 959 can be downloaded here for DS106: http://synology.asfi-fr.com/index.php?path=DS-106%2Fbeta/

    My question now is: I understand there are some problems with 3.2 such a LED log messages and eSata not working. What am I missing of important stuff by staying at 3.1?

  37. hello
    thanks for all. My DS106e is yes running with DSM 4.1 2668. it’s great !
    I first upgraded to 2.2 (DS107 alias), then direct to 3.2 (DS108j alias).
    Then DSM proposed in web interface to upgrade to 4.0.2228 directly. Well done
    Then i changed the alias to 109j, and upgraded to 4.1.2668 in web interface.
    All is running well.
    I think the slow down problem is not the RAM but the CPU. With the minimum service loaded, the RAM is 40% used but the CPU is at 80% usage

  38. Hello All

    Does anybody know if it is possible to get an old DS207+ to firmware DSM4.1
    and if so, how should i go about

    thanks in advance

      • Also tried 209j, f*cked it up again.
        Sorry guys I tried but failed (also I am new with this).
        Can anybody help kroppieright am me on getting DSM 4.x to run on a DS207+ ?

        • All this “hack” works because there is the same processor (mpc8241) in those different models (DS106, DSx07, DS108j, DSx09j). In the DSx07+ there is à mv5281 processor and no other DS have this f*cking proc inside…

  39. Is it possible to load this NAS firmware on a standard PC or Virtual Machine? This will allow more flexibility in terms of CPU, Memory as well as hard drive capacity. Would appreciate any pointers or experience you’ll have had in this regard.

  40. Have a DS106j and have successfully upgraded to a ds108j 4.0-2228. I followed the instructions above to the letter. I think the j series is much easier to upgrade I found that I didn’t have to change anything to NO in step 3.9 – Just left it. I found the DSM software for the various stages of upgrades from my original 106j only added functions it could handle; previously “sleeping” . Also now I have a 2.5 HDD Hitachi 1TB running with a IDE SATA convertor . She runs like a swiss watch. Also added a large ext fan on the side running from the units internal power (small dc power lead runs out of the top of the box to the fan)

  41. Perfect, thank you :)
    My Synology DS106j runing great with DSM3.1!
    One question, when i install a new HDD on my Synology, can i direct to dsm3.1 update?

    • Yes. In fact, since the current firmware version is stored in a flashrom on the device, it will force you to install the 3.1.
      I’m not sure if it was always this way, but with the newer firmware and versions of Synology Assistant it is impossible to downgrade the firmware.

  42. I upgraded my old ds106e to DSM4.0-2228 (with the above procedure. Everything went well, but I cann’t access the NAS from the internet anymore.
    I cann’t see any service on any service port (eg. port 5000 nas admin).
    The port forwarding in my router is setup correctly.
    Does anybody encountred problems with this after the upgrade?

    • I’ve been running DSM 3.2beta stable since 3.sept 2011 on my DS106e, upgraded just now.
      My /etc.defaults/synoinfo.conf was set to DS108j, used the plain web management to upgrade to DSM 4.0-2228. Edited the synoinfo.conf file back to include the various DS106e limitations.
      I also downloaded the latest DS107e .pat file, and copied the esata files via the /volume1/public share to /usr/syno/hotplug
      cp /volume1/public/pci.* /usr/syno/hotplug
      cp -r /volume1/public/pci /usr/syno/hotplug.d
      from: http://forum.synology.com/enu/viewtopic.php?f=128&t=15761&hilit=goetz+esata&start=375 (the previous page has some info that Goetz replies to with the copy commands)
      Have not tried the esata connection yet; but the box reboots, web management and everything + settings work perfectly.

  43. Just bought a second hand 106e. Thanks for the guide .Installed the 959 fw to get DLNA. Didn’t bother to get DSM3

  44. Does anyone know if it’s possible to upgrade my Synology DS207+ to the latest firmware. Different processor (Marvell Orion mv5281) with reference to Synolgoy DS207 (Freescale PowerQUICC II MPC8241)

  45. Hi, thanks for this great guide. I succesfully upgraded my old DS106 to DMS 4.2 – 3247. Does anybody encountred problems with DS Video Station app (Android/iOS) . Don’t know why I can’t see video station in Control Panel > Application Portal. I have there only Download,Audio and File station. Has anyone a clue, what to do?

    Thanks

  46. A bit of info for people reading this guide, be aware of the extra CPU usage of the higher DSM versions.
    I just used this guide to upgrade my 207 (not 207+) by setting it to 209j.
    Upgraded all the way to DSM 4.2
    Now I have downgraded it again to DSM 3.2. (happy that was possible)

    Reason: My network copy speed lost about 33% after I upgraded to 4.2, and looking at the ressource manager I could see that the CPU was running at full speed when I copied files.
    I don’t need any of the newer features in the DSM packages, so I will stick with the 3.2 version for now :)

  47. I recently updated to 4.2, works like a charm but I can’t seem to add the SynoCommunity Source. Anyone have a fix?

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>