Polanskiman

User Reported Compatibility Thread for DSM 6.2

Recommended Posts

Loader version and type (918+):  1.04b  DS918+

DSM version in use (including critical update):  DSM 6.2.1-23824

Using custom modules/ramdisk?   mlx4_core mlx4_en mlx_compat

Hardware details:  Motherboard: MSI B150M-D3 G4400

Device Description    Mellanox MT26448 ConnectX EN 10GigE, PCIe 2.0 5GT/s

Vital Product Data (VPD)    
Identifier    ConnectX-2 SFP+
Part Number    MNPA19-XTR

 

i found the error

 

[   20.006524] mlx4_core: Mellanox ConnectX core driver v4.1-1.0.2 (27 Jun 2017)
[   20.006531] mlx4_core: Initializing
[   20.007792] mlx4_core: probe of 0000:01:00.0 failed with error -5

  • Like 1

Share this post


Link to post
Share on other sites

Loader version and type (DS3615xs):  1.03B DS3615xs+

DSM version in use (including critical update):  DSM 6.2.1-23824 Update 2

Using custom modules/ramdisk? If yes which one?:  None

Hardware details:  DELL Optiplex 7010 USFF (core I5 3470), 6GB RAM

 

Hardware Acceleration with Plex is working

Share this post


Link to post
Share on other sites

Loader version and type (918+):  1.04b2 DS918+

DSM version in use (including critical update):  DSM 6.2.1-23824 Update 2

Using custom modules/ramdisk? If yes which one?:  no

Hardware details:  Motherboard:  Biostar J3060NH;  NIC:  Realtek RTL8111H

 

Successfull fresh installation with DSM_DS918+_23739.pat + update inside System. Didn´t check Hardware transcoding, yet.

Share this post


Link to post
Share on other sites

Loader version and type: 1.04b DS918+

DSM version in use (including critical update):  DSM 6.2.1-23824 Update 4

Using custom modules/ramdisk? If yes which one?:  no

Hardware details: Intel i3-8100, Gigabyte Z370 HD3, Intel lan, 2 X LSI SAS9220-8i  HBA in IT mode. 8GB Hyper X DDR4-2666

Share this post


Link to post
Share on other sites

Loader version and type: 1.04b DS918+

DSM version in use (including critical update):  DSM 6.2.1-23824 Update 4

Using custom modules/ramdisk? If yes which one?:  no

Hardware details: Intel i5-4670, Gigabyte Z87X-UD5H, SATA PCIe card 4 ports (chipset Marvell 88SE9235, Model SI-PEX40062)

 

NOTE - I have 8 hard drives, I usually use the Intel SATA ports on the motherboard and if the others are not compatible then I disable them in BIOS/UEFI  and use the above PCIe card which is cheap and never had problems with in all my Xpenology builds.

Edited by chipped

Share this post


Link to post
Share on other sites

Platform: Supermicro X10-SLL-F 

Loader version and type (918+):  1.04b  DS918+

DSM version in use (including critical update):  DSM 6.2-23739

Using custom modules/ramdisk? NONE

Hardware details:  Motherboard: Supermicro X10-SLL-F  CPU Intel Xeon E3-1225v3 20gb ECC Ddr3   

4x Seagate ST8000DM004
Part Number   X10-SLL-F 

SUCCESSFUL

Comments: I must say, the X10-SLL-F works like OOB with Xpenology. This has taken every loader & 916/918/3615/3617 WITHOUT ANY issue.  This board LOVES Xepenology

Ive been able to add 10GBE t540x2 cards, using 2x sata 6gbs cards with this setup too.

SMOOTH..AS.. BUTTER as if i actually went and bought the Diskstation.

1.04b/6.2/918+ also working flawless on MSI B250m Mortar Pentium G4560 4gb SUCCESSFUL

 

 A Massive thank you to Jun for all the work on the loader. Thank you Polanskiman for everything you do for the community.

Very grateful to be able to have a Nas that i cannot afford. My fam uses every day

 

 

 

Share this post


Link to post
Share on other sites

Loader version and type (918+/3615xs/3617xs): 1.04b DS918+

DSM version in use : DSM 6.2.1-23824

Using custom modules/ramdisk? None

Hardware details : VC65R-G039M

 

RAM : 8G * 2

HDD  : 2T * 4

 

Lan (Realtek) Work well but WLan (Intel 7265) not recorgnized

 

SD Card Reader Recognized but can't usb SD media

 

Bluetooth, serial works

 

Can't boot with Additional Driver (v0.5 test)

 

Edited by dateno1
add more info

Share this post


Link to post
Share on other sites

Loader version and type (918+/3615xs/3617xs): Jun's Loader v1.03b - DS3615xs

DSM version in use: DSM 6.2.1-23824 update 4

Using custom modules/ramdisk: NO

Hardware details: HP Elite 8200, Intel Core i5, integrated NIC Intel 82579LM

 

Prerequisites:

Computer needs to be booted in Legacy BIOS mode for network to work. However HP Elite 8200 UEFI BIOS refused to boot loader in Legacy mode, only EFI.

Booting EFI mode makes that network is not working for Jun's Loader 1.03b.

How I solved the boot issue? Loader's USB key partition table has Protected partition table. And looks like HP's UEFI BIOS for mentioned model has issues booting in Legacy mode in that situation.

I converted USB key's partition table to Hybrid partition table. That helped BIOS to see MBR partitions and boot in Legacy mode.

For conversion I used 'gdisk' tool in linux/macOS. I selected all three USB key's partitions to be part of MBR partition table, whereas I flagged first (EFI) partition as bootable for Legacy boot to work correctly.

To make Legacy boot mandatory I could disable all UEFI boot options in BIOS. However I rather renamed EFI folder name on first USB key partition to something else. That way Legacy boot became the only option for that USB key.

Edited by Mitja
  • Like 1

Share this post


Link to post
Share on other sites
On 12.2.2019 at 08:14, Mitja said:

Version und Typ des Loaders (918 + / 3615xs / 3617xs): Jun's Loader v1.03b - DS3615xs

Verwendete DSM-Version: DSM 6.2.1-23824-Update 4

Verwenden von benutzerdefinierten Modulen / RAM-Disk: NEIN

Hardwaredetails: HP Elite 8200, Intel Core i5, integrierte NIC Intel 82579LM

 

Voraussetzungen:

Der Computer muss im Legacy-BIOS-Modus gestartet werden, damit das Netzwerk funktioniert. Das HP Elite 8200 UEFI BIOS hat jedoch den Bootloader im Legacy-Modus (EFI) abgelehnt.

Beim Booten des EFI-Modus funktioniert das Netzwerk für Jun's Loader 1.03b nicht.

Wie habe ich das Bootproblem gelöst? Die USB-Schlüsselpartitionstabelle des Laders verfügt über eine geschützte Partitionstabelle. Und wie es aussieht, hat das UEFI-BIOS von HP für das erwähnte Modell in dieser Situation Probleme beim Starten des Legacy-Modus.

Ich habe die Partitionstabelle des USB-Schlüssels in eine Hybridpartitionstabelle umgewandelt. Dies half dem BIOS, MBR-Partitionen anzuzeigen und im Legacy-Modus zu starten.

Für die Konvertierung habe ich 'gdisk' in Linux / MacOS verwendet. Ich habe alle drei Partitionen des USB-Sticks als Teil der MBR-Partitionstabelle ausgewählt, während ich die erste (EFI) -Partition als startfähig gekennzeichnet habe, damit Legacy-Boot ordnungsgemäß funktioniert.

Um den Legacy-Start obligatorisch zu machen, könnte ich alle UEFI-Startoptionen im BIOS deaktivieren. Ich habe jedoch den EFI-Ordnernamen auf der ersten USB-Schlüsselpartition in etwas anderes umbenannt. Auf diese Weise wurde Legacy-Boot die einzige Option für diesen USB-Schlüssel.

 

Hello Mitja
I have the same problem as you.
In my setup I have the same NIC (82579lm) and it is not found at 1.03b. I tried to follow your instructions, unfortunately without success.
Can you please explain how I used it on a win 10 client (I converted the USB key partition table to a hybrid partition table.) That helped BIOS to see MBR partitions and boot in legacy mode.

For conversion I used 'gdisk' tool in linux / macOS. I selected all three USB key partitions to part of the MBR partition table, while I flagged first (EFI) partition as bootable for legacy boot to work correctly.)
Thank you for your answer

Share this post


Link to post
Share on other sites

Loader version and type (3615xs):  1.03b DS3615xs // DSM 6.2-23739 Update 1

Loader version and type (3617xs):  1.03b DS3617xs // DSM 6.2-23739 Update 1

Loader version and type (918+):  1.04b DS918+ // DSM 6.2.1-23824

 

Using custom modules/ramdisk? If yes which one?:  None / 0.2 / 0.3 / 0.4 / 0.5 tested, all good but raid controller

Hardware details:  FANTEC SRC-2080X07, ASUS H81M-Plus, i3-4350, 4GB DDR3

Controller: DawiControl DC-624e, 1xDC-600e, 2xDC-600e, LSI MegaRAID 8708EM2, SUN ASR-5805 RAID Controller 3G SAS / SATA

 

 

Share this post


Link to post
Share on other sites

Loader version and type (ds3615xs):  1.03b (!!!)  DSM_3615xs

DSM version in use (including critical update):  DSM 6.2.1-23824 Update 4

Using custom modules/ramdisk?   None

Hardware details:  Motherboard: GIGABYTE GA-945GCM-S2L

ePCI x1  NIC ASMedia 106x ($10 :)

.

Share this post


Link to post
Share on other sites
On 2/15/2019 at 9:02 PM, plan_B said:

 

Hello Mitja
I have the same problem as you.
In my setup I have the same NIC (82579lm) and it is not found at 1.03b. I tried to follow your instructions, unfortunately without success.
Can you please explain how I used it on a win 10 client (I converted the USB key partition table to a hybrid partition table.) That helped BIOS to see MBR partitions and boot in legacy mode.

For conversion I used 'gdisk' tool in linux / macOS. I selected all three USB key partitions to part of the MBR partition table, while I flagged first (EFI) partition as bootable for legacy boot to work correctly.)
Thank you for your answer

Hi.

If you are asking me, how to convert to Hybrid under Windows, there is also a gdisk version for Win:

https://sourceforge.net/projects/gptfdisk/files/gptfdisk/1.0.4/gdisk-binaries/

How to do a change (steps were taken on macOS):

$ gdisk /dev/disk2  (USB key was in my case recognized as disk2; theck your situation, which disk number should be used for yours)
Command: r - recovery ...
Command: o - print protective MBR data
  -> list current MBR partitions; should be one before conversion
Recovery: h - make hybrid MBR
Type partition numbers: 1 2 3
Place EFI GPT (0xEE) partition first: n
Enter code (MBR partition #1): <Enter>
Set the bootable flag: y
Enter code (MBR partition #2): <Enter>
Set the bootable flag: n
Enter code (MBR partition #3): <Enter>
Set the bootable flag: n
Recovery: w - write table to disk and exit

 

Under Windows, go to the Command Line, and launch gdisk64 (or gdisk32, if you use older Windows), something like:

  gdisk64 X:

Where X is a disk number of your USB key. Number 0 is usually first internal disk, so be careful!

  • Like 1

Share this post


Link to post
Share on other sites

Success

Loader version and type 3617xs V1.03b for DSM 6.2 (current)
DSM version in use (including critical update): DSM 6.2-23739
Using custom modules/ramdisk? If yes which one?: NO
Hardware details (try being specific without giving long and useless technical details - model version, motherboard and NIC used should suffice): MB Asus P6X58D Premium, 12Gb ddr3  1600 i7 980x H2O corsair, Marvell LAN on board

 

Share this post


Link to post
Share on other sites
Posted (edited)

Are CPU requirements 100% set in stone or is it worth me trying the 1.04b loader with my i7 2700k (sandy bridge, couple gens older) when I have time. If definitely not I'll just go with the older loader. Also have a Core 2 Duo E8400 and a C2Quad available

Edited by mack26

Share this post


Link to post
Share on other sites

Haswell or later required with DS918+ image, which is what 1.04b supports

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.