IG-88

i answered your question in the other thread, the linked Vantec UGT-ST655 https://www.vantecusa.com/products_detail.php?p_id=286#tab-2 seems to be a normal jmb585 card

from the manual for the SFF unit there is no "full high" pcie slot all 4 are on the mainboard (no riser) and are side by side so the case will limit it for all 4 to low profile you might need keep that in mind when going for added pcie sata card as its skylake it should have pcie 3.0 support so a newer pcie controller like the jmb585 or asm1166 might give some advantage but the 1G nic will limit the usable performance to ~115 MByte/s the psu with 180W would be ok for 6 x 3.5" disks but fitting these in and have them properly cooled ... i guess even 4 x 3.5" disks will not fit into that thing (by design its just 2 x 3.5" and 1 x 2.5"), it already hast 4 x sata onbard (there is no use for the ODD with DSM so the 4th sata ist free for disks too) so is guess some frankenstein mod into a new case might be needed (HP usually has some custom stuff so standard mountings in a normal housing might not fit) even the psu might not be the normal atx so si might be needed to use that too in a new housing (i have seen 12v psu that do 3.3v and 5v on the board and that might even limit the usable amount of sata power connectors (depending on how strong the regulators on the board for 5v are) so there can be some headaches with these HP units when trying to go beyond the spec design the sata ports can be added as it has 4 pcie slots (2 x pcie 1x, 1 x pcie 4x, 1 x pcie 16x), the low profile is just a limit of the original housing so when using a different housing the card's size is no problem but if you have to use the original psu and all 5v comes from the mainbaord (12v only psu) then your limit in in that area looks like a jmb585 and from the text its a Vantec UGT-ST655 and as it only has one chip on it and say's pcie 3.0 its for sure a jmb585 https://www.vantecusa.com/products_detail.php?p_id=286 when using the pictures and zooming in there is a jmb logo in the chip and with some imagination you can also read the 585 (but there is no other pcie to 5x sata chip from jmb so its for sure a jmb585 based card) link did not work for me but if its jmb585 the it should do it also link did not work but when its jmb582 aka two sata ports coming from pcie and ends in 10 sata ports the ist a multiplexer for sure (every "real" sata port gets a one to five multiplexer chip) - no go for dsm/xpenology especially with this board i would guess you m.2 slot is just a sata m.2 slot no nvme (aka pcie) so a m.2 pcie card will not work - also i hyve not much faith in these cards even when working properly there are mechanical problems with these thin cards (direkt sata ports on the m.2 card, i successfully used a m.2 to pcie dapater with a short cable between m.2 and the pcie slot, but a 2nd wit a slightly longer cable hat problems so there are material/quality issues i expect) you might read up on that with the newer loaders, not sure how well they work on 918+/920+ images, will work for sure on 3617/3622 but you "loose" the intel quick sync hw transcoding that way, sata support seems to be build into all synology kernels, so ahci sata ports are kind of a safer bet

kannst ja auch mal das "Synology Directory Server" Paket (AD Server) installieren und eine Domain anlegen (falls das Paket denn mit 6.1 läuft) habe mal testweise beides aktiv und win10 21H2 sieht die syno als fileserver in der netzwerkumgebung (ohne mitglied der domian zu sein)

mein screenshot war dsm 6.2.3, ist unter dsm 7 jetzt wohl unter SMB zu finden https://kb.synology.com/de-de/DSM/help/DSM/AdminCenter/file_ws_discovery?version=7

versuch mal unter file services / advanced das WS-Discovery zu aktivieren

klingt nach generischen smb/cifs problemen mit evtl. versch. betriebsystem versionen schau mal hier rein (ist einer der vorteile wenn man xpenology nimmt, man kann auch die kb von syno nutzen) https://kb.synology.com/de-de/DSM/help/DSM/AdminCenter/file_winmacnfs_win?version=7

du hast nicht gschrieben welchen loader du benutzt, im 2. screenshot sieht man jun's loader (der bis dsm 6.2.3 u3 geht - und auch da gibt es drei "geschmacksrichtugen die sich etwas unterscheiden weil 918+ etwas höhere cpu anforderungen hat - aber dein 4th gen intel sollte dafür reichen, der ist aber auch das minimum) generell ist wichtig das die mac des nic in der vm identisch ist mit der die in der grub.cfg gesetzt ist (zumindest bei virtualbox) ansonsten gibt es im howto bereich auch sachen zu virtualbox die man sich ansehen kann (geht dann meist weiter hinten im thread zu neueren dsm versionen und was man da evtl. extra beachten sollte bzw. bekommt man da auch screenshots wie es mit neueren dsm versionen getestet wurde) ich verwende beim chipsatz ich9 in der vm config (es sollte min. 2 cpu's sein), sound habe ich abgeschalten (sollte aber auch nicht stören) da der support für 6.2 in <1 jahr endet (afair) wäre es wohl besser du versuchst dich an einem neueren loader der 7.0/7.1 unterstützt - aber zum üben ist der 1.03b/1.04b loader auch ok

was für ein controller wäre es denn (markings auf der karte, link zu bildern?) und was für firmware hast du benutzt? ist eher selten zu sehen das firmware für controller (karten) in dem bereich ausgegeben wird (download quelle? sicher das es nicht eine jmb585 firmware war die du auf den jmb582 controller geschrieben hast?) generell wäre ich vorsichtig mit sowas wenn nicht bekannt ist wie viel oem anteil da drin steckt (und man keinen weg zurück hat wenn es schief geht) habe schon mal eine jmb firmware eines anderen oem's auf eine externes gehäuse aufgebracht und danach war z.b. das sata port layout und die led steuerung anders aber sowas kann auch mit einem brick enden ansonsten kannst du alternativ auc nach etwas von asm statt jmb schauen oder die älteren marevell produkte (nur pcie 2.0) nehmen, sollte halt ahci kompatibl sein damit es in dsm vom ahci kernel treiber (in den base kernel eingeaut) ohne extra treiber funktioniert

at least there are some rumors about "the other" kernel 5.x based unit - the rtd1619 https://nascompares.com/rumour/synology-ds423-4-bay-nas-drive-rumour-mill/ "he architecture of which is incredibly likely to be for the DS223j, DS223 and DS423:" also interesting is the rumored 923+, most likely not a rtd1619 but also surly not a epyc7002 maybe the 923+ will be the icelake we have seen in the kernel config, maybe this cpu? https://ark.intel.com/content/www/us/en/ark/products/197122/intel-core-i31000g1-processor-4m-cache-up-to-3-20-ghz.html its tdp might fit the power consumption of a nas but the price point might be a problem but a r1000 base is also possible but we have not seen anything from synology using the amd gpu's for transcoding (and the plus in the name indicates that feature)

there seems to be no unit yet released based on that epyc7002, might happen later this year, maybe with with dsm 7.2? synology usually does not release the kernel for the recent dsm version (atm 7.1, kernel source from syno only for 7.0 available) so we dont expect the syno kernel source for 5.x available soon but nic drivers should be possible to build from the vanilla kernel.org source so IF there is a dsm *.pat file for a epyc7002 (released) unit available the repill loader could be extended to support that unit (if there are no new obstacles in terms of protection) - its just guessing from how things where going the last years but at least its kind of a logical chain how things might work out as a time frame (at best) i would not expect anything usable before december anyone in need of kernel 5.x now might consider open media vault or any other nas system out there its possible to set up a xpenology dsm system the normal way (to be ready when kernel 5.x is available) and then boot that system with a different boot media using OMV, the raid set of dsm should be usable with omv (even SHR sets should work) and its possible to boot dsm at any time by removing the omv boot media (my use case is the other way around, omv is my fallback if dsm cant be used anymore, https://xpenology.com/forum/topic/42793-hp-gen8-dsm-623-25426-update-3-failed/?do=findComment&comment=200475) - kind of a xpenology ready OMV nas system (dsm uses a 2GB and 2.4GB partition on every disk as raid1 for system and swap and installing dsm before using it with omv makes shure there is everything in place to run dsm later without the need changing anything on the disks as dsm 7.2(?) later will install on the already present system partition and leave the raid set untouched - but a backup of the data on the raid would be good, just in case)

ich würde da kein hindernis sehen, dein altsystem is avoron (64bit atom) und deine zielplattform ist je nach loader und modell Apollolake, Broadwell, Broadwellnk, Bromolow, ... https://kb.synology.com/en-global/DSM/tutorial/How_to_migrate_between_Synology_NAS_DSM_6_0_HDD limits sollte es da keine wesentlichen geben da du auch x86_64 bleibst https://kb.synology.com/en-global/DSM/tutorial/How_to_migrate_between_Synology_NAS_DSM_6_0_and_later#x_anchor_id7 allerdings ist ein umstieg auf dsm 7 mit ein paar haken verbunden da es u.a. bei den 3rd party paketen dann auch neue versionen für 7.x benötigt, ist aber kein xpenology problem, das haben alle die von 6.x auf 7.x updaten (würdest du auch haben wenn du deine 415+ auf 7.1 umstellst während des umstiegs auf xpenology sollte man nicht unbedingt ein downgrade versuchen (das offiziell von syno nicht unterstützt wird), dicht an den szenarien bleiben die syno selbst vorsieht, dann kann man auch deren tools und KB benutzen, denn abgesehen vom loader ist das installierte dsm "ganz normal" so wie auf einem orginalen system

versuch mal die ip adresse des nas auf dem du installierst am router für internet zu blockieren oder trenne internet per kabel das pat file kommt dann von lokal auf dem pc und er kann nichts im internet nachladen

the drivers will only work for 6.2.3 but there are patches and driver for newer DSM Versions https://xpenology.com/forum/topic/59909-i915ko-backported-driver-for-intel-10th-gen-ds918-ver-701-up3/

extra/extra2 from 1st page, that will remove jun's special i915 driver that does not work anymore with 6.2.3, synology has a new i915 with 6.2.3 that is more or less the same as jun's driver your J3710 is a braswell and will not be able to encode hevc (h.265), so if you do reencoding use avc (h.264) https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video

usually limits with DSM are about cpu gen's like min 4th gen for 918+, with just the cpu its usually about two possible gen's (intel, tick-tock), 2nd and 3rd was for one socket/chipset so even when downgrading the cpu one gen with the same board its not possible to make things not work (you cant downgrade below 4th gen with just a cpu swap) one of the pitfalls can be the number of supported cpu cores (including HT), when having more "threads" then the max cpu in the kernel then it will "cut off" whats behind the max. cpu and its usually a real cpu core and after that a "HT virtual" core and those HT "virtual cores" only have ~25% of a real core in your case its only 8 threads and the 3622 has max. 24 threads (https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/) but that's "only" about the cpu performance

eigentlich sollte das automatisch gehen bei deinen schritten aber du kannst ja mal einen anderen laoder versuchen https://xpenology.com/forum/topic/63486-automated-redpill-loader/

finger for vibrations and ear for noise, even on a 2.5" hdd you will recognise if the spindle motor is running or starts to spin up config SYNO_SATA_JMB585_FIX bool "Fix JMicron issues" default n select SYNO_SATA_CONTROLLER_INFO help <DSM> #120513 Fix JMicron JMB585 interrupt issues config SYNO_SATA_JMB585_DUBIOUS_IFS_FIX bool "Fix JMicron 585 raise IFS on device error" default n select SYNO_SATA_CONTROLLER_INFO help <DSM> #127949 Fix JMicron 585 raises IFS on device error. Determine the actual error by reading disk ncq log. config SYNO_SATA_JMB585_GPIO_LED_CTRL bool "Interfaces For Jmicron JMB585 GPIO Control" default n depends on SYNO_OF help <DSM> #131900 Provides the infterfaces to operate the GPIO pins on JMB585. config SYNO_SATA_ASM116X_CONTROL bool help <DSM> No bug entry asmedia 116X register read / write function. config SYNO_SATA_ASM116X_AMP_ADJUST bool "adjust amplitude and de-emphasis for asmedia 1061 sata signal" default n select SYNO_SATA_ASM116X_CONTROL help <DSM> No bug entry adjust amplitude and de-emphasis for asmedia 116X sata signal config SYNO_SATA_ASM116X_GPIO_LED_CTRL bool "Interfaces For Asmedia 116X GPIO Control" depends on SYNO_OF default n select SYNO_SATA_ASM116X_CONTROL help <DSM> # Provides the infterfaces to operate the GPIO pins on Asmedia 116X.

https://archive.synology.com/download/ToolChain/toolchain/7.1-42661 edit: there is little more in the config files EPYC7002 = AMD EPYC Embedded 7002 https://www.amd.com/en/processors/embedded-epyc-7002-series from kernel config CONFIG_NR_CPUS=24, so its a 12 core unit and there seems to be ony one with 12 cores from AMD AMD EPYC Embedded 7272, max. 3.2GHz, base 2.9GHz, 120W ICELAKED = Intel Icelake-D https://www.intel.com/content/www/us/en/products/platforms/details/ice-lake-d.html both look like as for syno business units so nothing new as a replacement for 920+ (intel qsv support) but at least kernel 5.10.55 will add intel igc support (2.5Gbit nic) and if the "old" units get kernel 5.10 (witn dsm 7.2?) we will have better intel qsv support

did you do a pci pass trough for the controller in the vm's configuration? whats the pci id und sub id's of the controller the driver would be aacraid and that driver is part of the additional/extended extra.lzma beside pci device passtrough its also passible to use rdm mapping of the disks into the vm, that way you woud not need a extra driver

thats something synology should be answering in its spec's (for amd based units) or knowledge base as xpenology users we are not excluded from syno's web resources as long as its a generic function (things like adding nvidia support to 3615/3617 as done with 6.2.3 will not be covered by syno's kb)

the way we talked about to use wch382l with the loader was as pcie card, the other end does not matter how the serial connection is done (the part where the terminal program is running), imho you will not succeed with any usb adapter because there usb stack is not running at this point (syno's kernel loaded without any additional modules), the way you could do that is a m.2 nvme to pcie adapter with a pcie card (or a m.2 nvme card with serial port - if such a thing exists) but i guess in most cases people will use a m.2 nvme (pcie 4x) to pcie as a extension for more sata ports or to even get sata ports (as with my test notebook that did not have sata ports, just nvme) we need to use whats livable in syno's dsm kernel for the serial connection for now, i don't know if there is any way to do anything additional using the rp kernel module to inject code that would add anything useful here, thats kind of a brainteaser for the people adapt in kernel hacking

suggested driver to add (often asked/used) -aqc111 - usb adapter 2.5/5 GBbit -mlx_compat mlx4_core mlx4_en mlx5_core -aacraid -tn40xx - tehuti 10G nic's (can be tricky to have all firmware files integrated for all phy's, i do have as source that usually works for all cards as i added from different sources) -9p for virtio drivers (9pnet 9pnet_virtio 9p virtio) -ixgbevf, igbvf,,i40evf for virtio

both plex and jellyfin dont depend on serial or syno's codecs so its kind of driver/kernel/hardware related only thing that comes to mind would be to change the state of vt-d for the iGPU in bios

the driver mentioned is only usable with dsm 6.2 dsm 7.0 has a different kernel version and that will prevent the driver to work if you use tinycore rp loader and let it detect you hardware then the card should work the driver is present in pocopicos extension repository https://github.com/pocopico/rp-ext/tree/main/atlantic

driver should be ok as you have devices in /dev/dri videostation us usually usable with a patch https://xpenology.com/forum/topic/49961-synocodectool-patch-for-dsm-70/ but plex should be working with just the driver and plexpass (license needed to use hardware transcoding with plex) maybe try this instead of plex https://synocommunity.com/package/jellyfin that should also work with just the i915 driver and hardware transcoding is free ootb to use