IG-88

just a warning, looks like synology retracted 6.2.3, i updated the 1st post

zum einen ist das in sachen funktion unnötig da 918+ ein default von 16 disks hat, es ist also egal welche ports du an den controllern belegst, es werden immer alle disks sichtbar sein zum zweiten hat der lsi sas controller (bzw. dessen treiber) die eigenschaft alle disks immer hintereiander zu reihen, egal an welchem der 8 ports sie hängen, lücken werden einfach entfernt, was u.a. dazu führt das beim ausfall einer disk (oder entfernen) die anderen disks dahinter "aufrutsuchen" and sie ihre slot position in der gui wechseln, was du ja eigentlich nicht willst - solange du dafür keine lösung hast ist die ganze idee mit dem anordnen der ports für die füße - meine lösung dafür ist damit zu leben und akribisch SN's and anodnung der plattten (und ports) im gehäuse zu dokumentieren (wenn eine platte "fehlt" und es unodnung in der gui gibt kann man die fehlende SN ermitteln) oder beim controller auf ahci umsteigen, allerdings gibts keinen wirklich guten 8port ahci controller https://xpenology.com/forum/topic/19854-sata-controllers-not-recognized/?do=findComment&comment=122709 aber eigentlich brauchst du ja nur einen 4port controller wenn du mechanisch nur 8 slots für platten hast

i looked a little into the differences in devices supported by synology's and jun's i915 driver and there seems only to be differences in never produced ice lake gpu's planed in 2018 (gpu gen 10/11) gpu's from i3 9100 is still the same device id as for i3 8100 (gpu gen 9.5, up to coffee lake and gemini lake) anything new that comes out in a few weeks/month is presumably not supported by the driver so if hardware transcoding is to be used nothing newer then a 9th gen cpu is to use (new 10th gen desktop cpu's announced lately might not work with synology's driver) this can be used to have a look about cpu gen's and gpu gen's from intel https://en.wikichip.org/wiki/intel/microarchitectures

its a file in /var/log but you can also type it as a command in the console (you can try to find things in a search engine like google)

so if you cant say if /dev/dri was there with 6.2.2 (same driver from jun as for 6.2.0) you cant be sure if its possible to work at all with your cpu difference to 6.2.3 is that it uses synology's new own i915 driver that is a few month older from the source then jun's bur your xenon device ID 0x191D - Xeon E3-1245v5 is in synologys i915 driver, so it should show up with 6.2.3 anything in the log (dmesg), what does lspci show?

maybe try to take out some network stuff just connect the board and a windows pc with a rj45 cable and run a dhcp server on the windows machine (https://www.dhcpserver.de) also its possible to connect a nullmodem cable to the board and using the serial console to see whats happening

it was meant for a test, using a new usb and a empty disk you did not say anything about your update path and it was working an a lower DSM version number

to lazy to read just 5 posts above? there is not that much need as the original driver from jun are working again, just some people with newer hardware and some 10G nic's will really need this beside, there where no additional drivers for 6.2.2 for about one year ...

try loader 1.04b with jun's original extra/extra2 and dsm 6.2(.0) https://archive.synology.com/download/DSM/release/6.2/23739/DSM_DS918+_23739.pat and see if you get /dev/dri (as long as you don't have it you might not try to activate any codecs, without /dev/dri hardware transcoding is not working)

nothing in terms of functionality to gain but if you do it you can unplug your usb as 6.2.2 is still runing, put the new extra/extra2 to the usb replacing the old, plug it back and install 6.2.3 through the gui (its also possible to mount the usb, while still plunged in, on dsm 6.2.2 running, copy the extra/extra2 to it, unmount the usb and then do the update to 6.2.3)

yes, 1st was to install the main version (6.2.2) and 2nd was for the latest update (u6) there is 6.2.3 already and if you update to this you will need a new extra/extra2 https://xpenology.com/forum/topic/28321-driver-extension-jun-104b-for-dsm623-for-918/

not really, when it comes to use ssd only (sata based) then mpt based controllers are still mandatory, when using hdd with added ssd for cache or a smaller fast volume ahci can be a alternative (ssd would be connected to onbard sata and hdd to added ahci controllers) atm a JMB585 based (5port) card would be my favorite as it supports pcie 3.0 and should have two times the throughput of a marvell 92xx based cards (pcie 2.0) sadly its still on delivers because of the corona crises i also intend to test a M.2 bases card of that type and M.2 to pcie 4x adapter (for using normal pcie cards) i run a micro atx board with 1xpcie 16x, 1xpcie 4x, 2xpcie 1x and one M.2 (pcie 4x) the 8port controller might be ok'ich for 1 GBit network but for 10G or even SSD based systems the outdated marvell 92xx wont do it still a safe bet are lsi/broadcom mpt controllers, plenty of bandwidth with pcie 8x and with the new released kernel source from synology a got a working mpt2sas (27.0.0.1) driver that will support most of the mpt controllers (dont know yet about mpt2/mpt3 for 3615/17 but synology them self had a better mpt3sas driver with 24992 (now 22.0.2.0, they started dsm 6.2.0 with v13.0.0.0) i had no time to really test the ahci controllers with 4-5 ssd's to see if there is a difference as the numbers suggest and i still wait for the JMB585 controllers (use the forum search with jmb585 to find some infos about products and estimated performance values) so no hard facts, just more ideas and things to test

what are your plans on how to use it? synology loads cpufreq* modules by itself but how are you intent to use the new module?

yes, in the next days

here is one positive report https://xpenology.com/forum/topic/12867-user-reported-compatibility-thread-for-dsm-62/?do=findComment&comment=139518 maybe try loader 1.04b, mod it with the rd.gz and zImage from DSM_DS918+_25423.pat (DSM 6.2.3, use 7zip to extract the files) and also copy the extra/extra2 0.10 (overwrite old files) https://xpenology.com/forum/topic/28321-driver-extension-jun-104b-for-dsm623-for-918/

the board say's SU-SA3004 and if i look that one up at amazone i find that it is a ASM1061 + 1093 Chipset ASM1061 is a 2 port controller and 1093 is a port muliplier, so its exactly what your results imply, you will only see the ports of the asm1061 https://www.asmedia.com.tw/eng/e_show_products.php?cate_index=166&item=118 https://www.asmedia.com.tw/eng/e_show_products.php?cate_index=138&item=141

it DOES, if someone is impatient he can create his own extra/extra2 until i upload 0.11 (later this evening) you will get the new mpt3sas.ko with 0.11

ich meinte schon DSM, es gibt ja auch andere Systeme wie open media vault usw. da kann man auch hardware transcoding nutzen und wäre nichr mal auf intel qsv beschränkt innerhalb dessen was mit DSM geht ist hardware transcoding nur mit 918+ möglich wenn man auf aktuellem stand installieren will (6.2.3) also meinem avatar nach bin ich voll synthetisch, eine KI, nicht solche halben sachen wie die Borg😁

as a newer mpt3sas.ko made no difference and jun's mpt3sys did not work i assumed the difference might be on level lower so i kept the new mpt3sas v27.0.0.1 and replaced my own new complied version (synology kernel source 24992) of scsi_transport_spi.ko, scsi_transport_sas.ko, raid_class.ko with the files from jun's original extra/extra2 test looks good, no problems loading mpt3sas and there are smart infos now

the bios of the controller usually shows it its IR or IT firmware, in case of IT there is no need to activate anything to get the disks show up

maybe you have a controller using multiplexing and that is not supported in dsm whats the added controller? might be a 2port sata chip plus multiplexer chip

tried this yet too and found out why i had smart status - i accidentally used the similar looking 8 port ahci controller that uses even the same cable as my mpt2 sas controller after changing and trying i could reproduce your error with the mpt3sas from jun's extra (does not load) i made a new mpt3sas from the latest source i had around and the driver at least works with my old sas9211-8i mpt3sas version 27.00.01.00 loaded mpt3sas 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control mpt3sas 0000:01:00.0: enabling device (0000 -> 0002) mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (16339516 kB) mpt2sas_cm0: IOC Number : 0 mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 126 ... mpt2sas_cm0: port enable: SUCCESS still no smart but it would be a improvement for some people with newer sas controllers with SAS33xx, SAS37xx cips here are the device id's that would be supported (vendor 1000) 0064 SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] 0065 SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] 006e SAS2308 PCI-Express Fusion-MPT SAS-2 0070 SAS2004 PCI-Express Fusion-MPT SAS-2 [Spitfire] 0072 SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] 0074 SAS2108 PCI-Express Fusion-MPT SAS-2 [Liberator] 0076 SAS2108 PCI-Express Fusion-MPT SAS-2 [Liberator] 0077 SAS2108 PCI-Express Fusion-MPT SAS-2 [Liberator] 007e SSS6200 PCI-Express Flash SSD 0080 SAS2208 PCI-Express Fusion-MPT SAS-2 0081 SAS2208 PCI-Express Fusion-MPT SAS-2 0082 SAS2208 PCI-Express Fusion-MPT SAS-2 0083 SAS2208 PCI-Express Fusion-MPT SAS-2 0084 SAS2208 PCI-Express Fusion-MPT SAS-2 0085 SAS2208 PCI-Express Fusion-MPT SAS-2 0086 SAS2308 PCI-Express Fusion-MPT SAS-2 0087 SAS2308 PCI-Express Fusion-MPT SAS-2 0090 SAS3108 PCI-Express Fusion-MPT SAS-3 0091 SAS3108 PCI-Express Fusion-MPT SAS-3 0094 SAS3108 PCI-Express Fusion-MPT SAS-3 0095 SAS3108 PCI-Express Fusion-MPT SAS-3 0096 SAS3004 PCI-Express Fusion-MPT SAS-3 0097 SAS3008 PCI-Express Fusion-MPT SAS-3 00aa 00ab SAS3516 Fusion-MPT Tri-Mode RAID On Chip (ROC) 00ac SAS3416 Fusion-MPT Tri-Mode I/O Controller Chip (IOC) 00ad 00ae SAS3508 Fusion-MPT Tri-Mode RAID On Chip (ROC) 00af SAS3408 Fusion-MPT Tri-Mode I/O Controller Chip (IOC) 00c0 SAS3324 PCI-Express Fusion-MPT SAS-3 00c1 SAS3324 PCI-Express Fusion-MPT SAS-3 00c2 SAS3324 PCI-Express Fusion-MPT SAS-3 00c3 SAS3324 PCI-Express Fusion-MPT SAS-3 00c4 SAS3224 PCI-Express Fusion-MPT SAS-3 00c5 SAS3316 PCI-Express Fusion-MPT SAS-3 00c6 SAS3316 PCI-Express Fusion-MPT SAS-3 00c7 SAS3316 PCI-Express Fusion-MPT SAS-3 00c8 SAS3316 PCI-Express Fusion-MPT SAS-3 00c9 SAS3216 PCI-Express Fusion-MPT SAS-3 00d0 SAS3716 Fusion-MPT Tri-Mode RAID Controller Chip (ROC) 00d1 SAS3616 Fusion-MPT Tri-Mode I/O Controller Chip (IOC) 00d2 02b0 Virtual Endpoint on PCIe Switch

das 918+ image kann die intel quick sync video funktionen nutzen und es gibt einen patch den check über die seriennummer zu entfernen du hast spezifisch nach 3615 gefragt und auch nicht weiter erläuter was du vor hast dann führt wohl kein weg an 918+ vorbei (zumindest wenn du dsm nutzen willst), 3615 hat keine treiber für hardware transcoding und da bleiben nur die normalen cpu befehle (keine gpu unterstützung) safe bet wäre imho ein 8th gen intel für hardware transcoding wie ein i3 8100, jemand meinte bei ihm würde 9th gen cpu/gpu nicht mit 6.2.3 (neue i915 treiber von synology) gehen, habe ich noch nicht verfifizieren können da mein i3 9100 noch immer darauf wartet verbaut zu werden, in 1-2 wochen wird man mehr wissen (entweder habe ich was oder jemand andees schreibt darüber) hardware transcoding beim 918+ kann man auch abschalten, wäre also sinnvoll 918+ zu nehmen wie viel cpu power man für reines cpu transcoding braucht weiß ich nicht aber eine G5400 cpu (2core) war zu scchwach für 1920x1080 transcoding bei reiner cpu nutzung wird also min. ein 8100/9100 für 4k cpu transcoding brauchen schätze ich (sollte ich die 9100 verbaut haben weiß ich mehr)

on most (all?) pictures i've seen the flash module seemed to be removable and was plugged to a usb onboard connector it looks like this for you unit from this photo https://tpucdn.com/review/synology-ds1815plus/images/in_flash_small.jpg in fact the usb boot media we are using for xpenology is used the same way as the original, the update process (in dsm) stores its new kernel for booting there the same way it would on a original unit, for dsm all looks like a valid original units an all the update process is running the same way as on a original unit on 2nd thought you can unplug it for sure, it uses f400 for usb vid and pid, i cant remember it you need to have this vid/pid for booting (the bios might look for it) its possible to change the vid/pid with some tools and the right flash controller (the same way they do it in "factory's" in china) there are 1 or 2 threads about this but afaik it was more about replacing the original dom with a usb and still use the original firmware for this unit in question https://xpenology.com/forum/topic/9897-flash-transplant/ https://xpenology.com/forum/topic/12264-ds1511-running-xpenology/ https://xpenology.com/forum/topic/9787-%D0%B2%D0%BE%D1%81%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D0%BB%D0%B5%D0%BD%D0%B8%D0%B5-%D0%B7%D0%B0%D0%B3%D1%80%D1%83%D0%B7%D0%BE%D1%87%D0%BD%D0%BE%D0%B9-%D1%84%D0%BB%D0%B5%D1%88%D0%BA%D0%B8-%D0%BD%D0%B0-ds1511/ https://xpenology.com/forum/topic/13264-trying-to-fetch-dsm-60-on-a-ds1010/

if you already opened it you can also try to unconnect the usb dom and boot a live linux or even try to boot xpenology loader to check the network