flyride

Tutorial/Reference: 6.x Loaders and Platforms

Recommended Posts

Also to report, Mellanox ConnectX-3 MCX311A-XCAT Single Port SFP+ also works OOB for 1.03B DS3615xs (It's not a ConnectX-3 Pro, but the same driver works)

 

To be accurate, there is a compliant list from Synology themselves which works just fine.

 

https://www.synology.com/en-global/compatibility?search_by=category&category=network_interface_cards&p=1

 

Also, it seems like it's hardcoded to not able to add more than 2 NICs for the device, unless you disable PCIe NIC devices (in a physical baremetal environment), it is impossible (for now) to add a third NIC (i.e. you have two onboard 1Gbe and wishes to add a 10Gbe base T or SFP+)

 

Edited by kazuni

Share this post


Link to post
Share on other sites
On 1/25/2019 at 8:36 AM, Vodka2014 said:

Hi All

 

Intel I350T2V2 Dual work with DS3615xs Loader 1.03b On DSM 6.2.1

 

Thanks

 

I was asking does it work not that is does work. Sorry about that.

Share this post


Link to post
Share on other sites

These compatibility comments and questions probably belong in either the loader thread or the "user-reported compatibility" thread.

  • Thanks 1

Share this post


Link to post
Share on other sites

All this divergence is getting confusing.

 

I’m running a 3615, bare metal, 6.1.7, with i3 6300t Skylake, EFI boot.

 

Am I better waiting until everything sorts itself out into one loader?  Or maybe Change my system from 3615 to 918?

 

Share this post


Link to post
Share on other sites

Hi. Is the Intel EXPI9301CTBLK NIC supported by the 1.03b 3615x loader in order to perform the update from 6.1.7 to 6.2.1on a baremetal? I'm asking because according to the Synology compatibility list this model is not supported. With 2 x 1GB ports only E1G42ET / E1G42ETBLK is there.
Thanks

Edited by sadycus

Share this post


Link to post
Share on other sites

With 1.03b bootloader I'm able to boot only UEFI. But that way I do not see computer (I have Intel NIC).

However I'm not able to boot in Legacy BIOS. It finds no boot info on USB key. Should I prepare USB key somewhat differently to be able to boot in Legacy mode?

The table at the beginning of this thread says DSM 6.2 it should work only in Legacy. But how to boot that way? I already lost many hours and no progress ...

Help appreciated.

I have HP Elite 8200, and trying 3615x loader. 1.02b 3615x loader works fine, but initially boots in UEFI. Even those version I'm not able to boot in Legacy.

Edited by Mitja

Share this post


Link to post
Share on other sites

Create the USB using rufus and make sure you have Partition Scheme at MBR and Target System is BIOS

Share this post


Link to post
Share on other sites

very useful I have amd opteron 6272 that works with DSM 6.2  3615 but not 3617 dont know why i have tried a lot of stuff but cant get it to work, any thoughts

Supermicro H8SGL-F  c1E disable 

 

the reason i wanted 3617 DSM 6.2 is i know it supports 16 cores ( i have tested it the an intel cpu)

cat /proc/cpuinfo | grep "cpu cores" | sort -u | awk '{print $NF}'

 

Share this post


Link to post
Share on other sites

AFAIK all supported DSM versions support 8 threads total regardless of the processor type.  So 4 hyperthreaded cores, or 8 non-HT cores.

Share this post


Link to post
Share on other sites

Intel Core i5-4590T works with 1.04 and DS918+

 

(it does NOT work with 1.03b / DS3617xs / 6.2.1 needed to switch to DS918+ to get it working again)

Share this post


Link to post
Share on other sites
On 10/19/2018 at 8:36 AM, flyride said:

In addition to bricked boxes due to inattentive upgrades, there seems to be a surge of questions regarding how to select a DSM platform, version and loader.

This table should help navigate the options and current state of the loaders.  While situations rapidly change, it should be correct as of the listed date.

 

6.x Loaders and Platforms as of 12/Jan/2019

Loader DSM Platform DSM Version Kernel DSM /dev/dri DSM NVMe cache Boot method CPU Needed Notes
1.04b DS918 6.2 to 6.2.1 4.4.x Supported Supported EFI or Legacy BIOS Haswell or later recommended
1.03b DS3615 6.2 to 6.2.1 3.10.x Not Supported Not Supported Legacy BIOS only Nehalem or later 6.2.1 requires Intel NIC

 

  Change log (Reveal hidden contents)

[12/Jan/2019] No known DS3617 6.2.1 installs running

[22/Dec/2018] Added information for Genesys loader build

[20/Oct/2018] Updated for 1.04b loader

[22/Nov/2018] Corrected E1000 vNIC dialect to e1000e for 1.03b on ESXi

[10/Dec/2018] Updated earliest processor capability to reflect Nehalem report

@flyride Thank-you this table is very helpful!  Successfully upgraded to 6.1.7 with old hw and it is running very stable.  Just curious, this table says the kernel for ds3615 even on 6.2.1 is still 3.10.x - is that right?  Is only ds918 on kernel 4.4.x?  Is it likely at some point kernel 4.4.x will be on ds3615 or is kernel 3.10.x the end of the road?

Share this post


Link to post
Share on other sites
36 minutes ago, rl77 said:

Just curious, this table says the kernel for ds3615 even on 6.2.1 is still 3.10.x - is that right?  Is only ds918 on kernel 4.4.x?  Is it likely at some point kernel 4.4.x will be on ds3615 or is kernel 3.10.x the end of the road? 

 

Yes, DS918 is the only loader-supported DSM release that is on the 4.4 kernel tree.  I'm sure that Synology is using 4.4 for all their newly released product lines.

 

I'm not sure how anyone outside of Synology development would know if they intend to update the kernel on older products. They publicly state that they backport security updates to older kernels.  If they were going to arbitrarily upgrade the kernel (or if they were compelled to do so for DSM functionality dependencies), the DSM 7.0 release would seem to be a likely opportunity.

Share this post


Link to post
Share on other sites
Posted (edited)

could you please add a column whether hyper-v is supported? many people still hope to see the xplenology on hyper-v after dsm 5.2

Edited by mar1boro

Share this post


Link to post
Share on other sites
On 10/19/2018 at 10:36 AM, flyride said:

[12/Jan/2019] No known DS3617 6.2.1 installs running

 

Am I missing something, or am I just blind? I am running DS3617xs DSM 6.2.1-23824 Update 6

 

 

ds.png

Share this post


Link to post
Share on other sites
Posted (edited)
On 4/6/2019 at 8:39 AM, viper359 said:

Am I missing something, or am I just blind? I am running DS3617xs DSM 6.2.1-23824 Update 6

 

Aside from courteous language, no.  As of 12 Jan that appeared to be true.  Everything you see in that post comes from community experience and reports.  I'll remove that statement based on your note.

Edited by flyride

Share this post


Link to post
Share on other sites

That wasn't a slight at you, but rather me! I was certain i was missing something!

Share this post


Link to post
Share on other sites
Posted (edited)

I have a ASRock J3455-ITX Board with integrated Intel® Celeron® Prozessor J3455. I'm currently trying to update from my current version (DSM 6.0.2-8451 Update 9 with Jun's Loader V1.01, machine type DS3615xs) to the newest possible version. I can see from your matrix that I need a "Haswell or later" CPU for the recommended combination 1.04b loader and DSM 6.2.1 (not 6.2.2 because you mention that this DSM version fails on AsRock JXXXX). The CPU of my board (Apollo Lake / Goldmont generation) is a 14nm architecture and it was released in 2016 that makes me think that it is indeed "Haswell or later", but I'm not 100% sure, because the atom line is a parallel product line (Haswell is not part of this line). Is this the way to go for me? Flash my USB to Jun 1.04b and then on the DSM interface do a direct manual update to 6.2.1?

 

grafik.thumb.png.c35d668008083ffb2f6e670ec64c0686.png 

 

grafik.png.20830d9c40ec8f31d2faa270cd94a1c1.png

 

 

Edited by 5237478232

Share this post


Link to post
Share on other sites
10 minutes ago, 5237478232 said:

I have a ASRock J3455-ITX Board with integrated Intel® Celeron® Prozessor J3455. I'm currently trying to update from my current version (DSM 6.0.2-8451 Update 9 with Jun's Loader V1.01, machine type DS3615xs) to the newest possible version. I can see from your matrix that I need a "Haswell or later" CPU for the recommended combination 1.04b loader and DSM 6.2.1 Flash my USB to Jun 1.04b and then on the DSM interface do a direct manual update to 6.2.1?

 

Yes, your J3455 supports the instruction set needed.  When you install the new loader, your system will boot to a migration install since you are changing DSM platforms. So download the 6.2.1-23824 PAT file in advance.

  • Like 1

Share this post


Link to post
Share on other sites
4 hours ago, Olegin said:

@5237478232 But hw trancoding will not work on your mb.

 

I think that won't be a problem for me. It's only needed for Plex, right? I don't use that service anyway. So I can flash 1.04b loader and then upload to DSM 6.2.1 (not 6.2.2, as it doesn't seem to work on my board) if I don't plan to use hardware transcoding, am I right?

Share this post


Link to post
Share on other sites

Hello I'm trying to get xpenology working on my terramaster f2-221 I got it to boot and it worked but didn't see any drive volumes I know it can work on it from another forum  any idea?

Share this post


Link to post
Share on other sites
Posted (edited)

Hi,

 

I would like use DSM 6.2.2 and I see that 1.04b loader isn't compatible with AsRock Jxxxx Motherboard...

 

I have an motherboard ASRock FM2A85X-ITX with an AMD A10-6700 with DS3615xs DSM , it's not a J serie, i can update my server with DS918 DSM (without lost all my data ;) )?

An 1.05 is planned to correct AMD issue ?

 

Rgds

Akhlan

Edited by Akhlan

Share this post


Link to post
Share on other sites

DSM 6.2.2 with Jun v1.04b - DS918 

there are problem also with realtek network

(r8168 driver on DSM 6.2.1 works)

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.