Upgrade synology DS409 to DSM6

I have bought an DS409 a few years ago and I felt quite disappointed not to get every update brought by DSM 5 then 6.

One easy solution would be to buy a new NAS but, to be honnest, my current one is still working fine (and I have modified it a lot).

Goal of this post will be to show how to upgrade and as well, what is the process to understand if you can upgrade.

First, you need to know what is the CPU of your NAS to install a compatible DSM, one excellent resource:

https://github.com/SynoCommunity/spksrc/wiki/Architecture-per-Synology-model

also available here if the first source stop working:

https://www.synology.com/en-us/knowledgebase/DSM/tutorial/General/What_kind_of_CPU_does_my_NAS_have

For my NAS, I found that it embed a 88f6281 (DS409 – synology_88f6281_409) and wonderful information, a newer version of the 4 slot NAS embed the same CPU (DS411j – synology_88f6281_411j).

So the solution will be to trick my NAS to believe it is a DS411j instead of a DS409.

DSM rely on the file /etc.defaults/synoinfo.conf to recognize the NAS model it is.

In these file, I have replace the model reference in the unique line:

unique="synology_88f6281_409"

by

unique="synology_88f6281_411j"

you then just save the file, connect to the web interface and launch the update process, it will then propose to migrate to DSM V5.

In order to reach DSM V6 you will have to go through a few updates, there are milestones version you cannot skip apparently.

For the upgrade to DSM 5.2.5565, I have encountered an error while going through the installation, the solution was to provide manually the pat file of the update.

All DSM releases are available here:

https://dedl.synology.com/download/DSM/release/

you just need to download the right file, in my case it was:

https://dedl.synology.com/download/DSM/release/5.2/5565/DSM_DS411j_5565.pat

Since then, I am using DSM 6.0 with no regression for my usage.

Known issues are:

  • found on forum: esata not working directly

    in /etc.defaults/synoinfo.conf

    Add supportESATA="yes"under the line: support_s2s=”yes”

    alter the line esataportcfg=”0x0″ to esataportcfg="0x10"

  • If you were connecting on SSH using root account (boooh) it will not work anymore, you should connect with your admin account you are using to connect to the webinterface (and sudo will do the rest)

 

if I find any other issues or tips and tricks it will be added here.

 

Posted in Hacks
27 comments on “Upgrade synology DS409 to DSM6
  1. John says:

    So now that it’s been a while, how has this held up? I’m considering it for my DS409. Did you add additional RAM? If not, did that affect performance at all?

    • HackGins says:

      The NAS is still working fine and I haven’t encountered any issue since the upgrade.
      I continue to receive the DSM update (current version is Version: 6.2-23739-2 (2018-07-12)).
      I have not added any additional RAM and didn’t see any performance impact at first.
      Now, I start to have some performance issue (linked mostly with nodejs server and latest java version), it is mostly visible when I use the web interface, it is slower than before but no impact on network transfer speed, only the web interface is slower.

  2. Gunter says:

    Hi there,

    discovered your post yesterday and tried it on my DS209 which was stuck with DSM 4.22
    Upgraded to DSM 6.2.1-23824 Update 6 now by telling my DS209 it’s a DS212j. So far I see no issues – as written before the CPU goes more towards 100% than before which should be related due to the heavy HTML5 UI. I’ll try out more in the next days!

    Anyway, thanks a bunch, no need to buy a new Diskstation!

    • Mike says:

      How did you manage to upgrade the 209? Mine doesn’t see any updates when I change the model number in the syncinfo.conf. It still sees it as a DS209j and if I reboot after changing this I need to reinstall DSM 4.22

      • HackGins says:

        Depend on your NAS model,
        if your nas is a DS209J then the CPU is a ppc824x, no model later received this CPU so there is no DSM package update possible.
        if it is a DS209 then the CPU is a 88f6281 onboarded as well on DS210j, DS211j and DS212j and it should work as described in the article.

  3. Peter says:

    This Idea sounds very good. I do have a 409+, do you think this hack would work with a 409+, too?

  4. Kenneth Wieben says:

    I am trying to upgrade my 409+ to 410.
    I keep getting “file is corrupted”.
    All I have done is open the .pat file with notepad and chance 410 to 409+.
    The .pat file is a notepad file

    • HackGins says:

      to do so, you should update the synoinfo.conf in order to trick your NAS into believing it is a 410.
      Update files are usually checked with a hash signature so any modification will lead to corruption.
      you should have a line that should look like: unique=”synology_ppc853x_409+” which should be replaced by unique=”synology_ppc853x_410″
      but if it works it will only allow you to update until DSM 5.2 not later as the 410 is not supported anymore for firmware update.

    • Joser says:

      Have you got it?
      I still have no access to change the “unique line”

  5. Scholar says:

    FWIW, just editing the unique= attributed for my DS209 didn’t work. I kept ending up with the DS209 in a ‘migrating’ status.
    Once I edit synobios=”ds211j” (also in /etc.defaults/synoinfi.conf) everything worked.

    Here was my upgrade path:

    modify synoinfo.conf with:
    unique=”synology_88f6281_211j”
    and
    synobios=”ds211j”

    then manual upgrades as below:
    4.2-3211 -> 4.3-3827 -> 5.0-4528 -> 5.2-5967 -> 6.0.3-8754 -> 6.2.3-25423

    My old DS209 is now a great hyper backup vault for my 916+

  6. AweSmAsh says:

    Tried this on my 209 and it says
    “synoinfo.conf” File is read only

    I logged in as admin but cant seem to get past this issue.

    Any ideas?

    • HackGins says:

      The file synoinfo.conf belongs to root and admin does not have the right to update it, you need to open it as root.
      To do so, if you do this through SSH, you should sudo your command
      (ex:
      sudo vi synoinfo.conf
      it will prompt for password which is the same than the admin one by default)
      Hope it helps

  7. Stewart says:

    I was so happy to find this! But I couldn’t get it to work and was wondering if you had any insight. I have a DS409. I made three attempts:

    Attempt 1: SSH in. Changed unique=”synology_88f6281_409″ to unique=”synology_88f6281_411j” Saved. Restarted via web interface.

    Result 1: Wouldn’t let me log back in via the web interface. Had to reinstall DSM 4.2 via the synology assistant.

    Attempt 2: Same as attempt 1, but I also changed synobios=”ds409” to synobios=”ds411j”

    Result 2: Same as result 1.

    Attempt 3: Same as attempt 2, but I also changed upnpmodelname=”DS409″ to upnpmodelname=”DS411j”

    Result 3: Same as result 1.

    Do you have any idea what I’m doing wrong? My DSM is currently 4.2-3255.

    I have a new synology NAS coming and I need to find a way to migrate the data from this to the new one, but apparently I need a v5+ version of DSM to do it easily. Really appreciate the help.

    • HackGins says:

      Ouch, tough question.
      to be honest I don’t really see what is going wrong.
      The only difference I see is that I have not restarted the NAS after updating the synoinfo.conf file, I have launched directly the update from the web interface.

      When you did the 1st attempt, were you still able to connect through SSH? was it only the web interface that was rejecting the credentials?
      Another potential difference as well is that I am using another admin account (not admin or root). Have you tried to connect with other account to the web interface?

    • Pre says:

      @Stewart
      Something new ?

    • Paulo says:

      Hello
      I got same issues as you.
      Recovered with syno assistant and DSM_DS409_3259.pat
      Then I changed agaain /etc.defaults/synoinfo.conf with “*_411j”.
      But Don’t reboot !!!!
      Then I did a manual update with DSM_DS411j_3827.pat

      And after that I manually updated in this order
      DSM_DS411j_4458.pat
      DSM_DS411j_5565.pat
      DSM_DS411j_25426.pat
      synology_88f6281_411j.pat (this is the name for 5426-2)
      Then used interface automated updates to get 6.2
      I also modified the esata ports as adviced here.
      So far no issue …

      To get the pat files go to syno download center select 411j NAS and use the firmware to firmware upgrade wizard in the bottom of the page
      No need to modify other files only synoinfo.conf

      Cheers

  8. mutmut says:

    Hi, thanks for this article.
    I made the stuff on a DS210j (DSM5.2) and “upgraded” it to DS211j.
    I had some issues but finally I can have the last DSM version (6.2.3).
    But at this time, I can’t connect to my synology account to activate Quickconnect.
    People from Synology support told me that S/N, Mac address and synology NAS are not matching in order to connect to Synology account in DSM.
    Did you have such issue ?

    And as I really need Quickconnect (this NAS will go in another place and I don’t want to play with the ISP box), I’m trying to going back to DS210j but not sure it will work.
    Any try ?

    Thanks for your help.

    • Bob Hannent says:

      I have also tried upgrading my DS210j from DSM 5.2-5967 Update 9 to DSM 6.0-8754 but it offers the upgrade and at 2% it says “Incompatible upgrade”.

      I’ve changed the above ID and also “synobios”, but it didn’t work. I haven’t rebooted yet and I did try logging out and back in to reinitialise the session but that didn’t help.

  9. Thomas says:

    Thanks for the very inspirational post.

    I’m considering upgrading a DS110j to a DS112j which should be possible when considering your first (Github) link. However, the second (Synology) link mentions that the models have different CPU’s, but identical “spksrc architectures” mentioned as “88f628x”. 
      
    Do you think it’ll work out or do the CPU’s need to be EXACTLY identical ?  

  10. Franz says:

    I bricked my ds409+ 🙁

    did it as above, tried to install 4.3-3827 but the dsm does not boot.

    Diskstation is booting but DSM does not start, Status led is orange, the other Lights are green…

    what can i do now?

  11. GB says:

    Hello, I just upgraded my DS209 to DS212j and 6.2.3. One thing that was not clear on your post was that I was supposed to use Putty to SSH into my DS209. I used your tips along with a youtube video I found. It took a bit of figuring but got it to work.

    For others that need more of a visual here is what I used. In the comments there is a “Buddy Thompson” who shares some additional information on getting this to work.

    https://www.youtube.com/watch?v=FtpZoXVY8OY

    Basically you use Putty to SSH into your DS209. You tell your DS209 that it’s now a DS212j and save it’s conf file. Then download the DS212j DSM and install it. worked great. Thanks again.

  12. Carlos says:

    Hi, thanks for the post!

    I have a DS-508 running DSM 4.0. I need to upgrade it because its OpenSSL libs are too old (1.0.0n), vulnerable, and do not support the current TLS versions anymore. Just updating OpenSSL seems unfeasible, as there are many dependencies to be rebuilt.

    The DS508 uses a PowerPC MPC8543 processor; there are no newer models using this same CPU. However, the DS410 model uses the MPC8533E CPU model, which seems (to me) very similar.

    Are you aware of successful cases of this kind of “not-exactly the same CPU” upgrades? I’m afraid of bricking my old-timer…

    Regards!

    • HackGins says:

      Hi
      Just had a quick look at the spec of both CPU and there are few differences (L2 cache size for example) as they are considered different family (PPC854 vs PPC853).
      Having a look into Synology Tool Chain source code (tool suite used to compile the source code to be able to run on the target CPU), the DSM 4.0 is the latest one supporting the PPC 854x family (starting from 4.1 only the 853x is included), you can access the source code here: https://sourceforge.net/projects/dsgpl/files/Tool%20Chain/
      Sorry but I don’t see a solution with my current competence level.

      Depending on the expected usage, could it be a solution to install chroot to have a 2nd version of openssl running in the chroot jail?

Leave a Reply to Joser Cancel reply

Your email address will not be published. Required fields are marked *

*