IG-88

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

log is switched to serial port https://xpenology.com/forum/topic/9394-installation-faq/?tab=comments#comment-81097 without informatin about loader you use and what hardware (cpu, board) ... most likely not a driver problem so read faq and maybe this https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

does syno's VMM support to hand over pci(e) devices to a vm? (pass through) i'm not going to do this for just one person and one purpose that might not even work i wrote a tutorial on how to make your own drivers (i started all this by just wanting a button.ko), you can try making your own driver you just need to compile it and you can load it manually (insmod) before creating a new extra.lzma

thats the same as a clean install to one disk, so the problem must be something else did you read my question about the hardware transcoding working with former versions of dsm? https://xpenology.com/forum/topic/28321-driver-extension-jun-104b-for-dsm623-for-918/?do=findComment&comment=142841

even if the controller would have a driver, you just can't install a software package like on a normal linux, its a appliance how would you work with your camera to get any date to disk?

mpt3sas.ko

on what dsm version did you had this working`? with what additional software package (just a driver won#t do it) participating here is part of the fun but it will be discussed here (open) so we all can learn from it information about the hardware and a complete dmesg log would be useful 8111f is just the normal realtek can you be more precise, that might help other people did you try loader 1.03b with juns extra.lzma? sfc.ko from the extra.lzma 0.10 is the one from kernel 4.4.59 and supports SFC9120 10G Ethernet Controller (Virtual Function) SFC9120 10G Ethernet Controller SFL9021 10GBASE-T Ethernet Controller SFC9020 10G Ethernet Controller SFC4000 rev B [Solarstorm] SFC4000 rev A net [Solarstorm] the nic you wrote about seems to be 9021 so it might mot with the driver we already have did you try? if it does not and you have a link to linux driver source ... yes, you could even use 6.2.3 when you change (back) to jun's extra.lzma (in 6.2.3. the change that made new drivers necessary was reverted so the old packages work again)

what did you have before you updated to 918+ 6.2.3 and did /dev/dri worked before the update? i did not see any indications in your log that 915 was loaded before the 6.2.3 update and the only messages that i saw where when you updated to 6.2.3 and still used juns i915 driver, what resultet in messages about missing symbols when the i915 driver loaded its a xeon chipset and theb oard does not have video out like hdmi/dvi as usual or intel desktop chipset/cpu, maybe the board is not ale to use the gpu of a desktop cpu?

you might read this to understand PHY? https://en.wikipedia.org/wiki/PHY how did you loose it? igb v5.3.5.3 is the "normal" driver version used by synology and i'd expect them to use a driver that supports there own hardware so maybe your 4port onboard nic died? btw. the INTEL Atom C2538 soc already contains the network 4 port chip it just need the PHY for the physical interface, so the netwerk part in the soc is the one found by the igb driver

its usually on a single empty disk to make sure everything is ok and its possible to try things without doing anything to the system in use its also possible to use the normal system and reset it by installing with the 2nd option in grub, that keeps the data/raid but does a factory install of dsm it should overwrite the system partition and it should be the same as a clean/fresh install not sure, is that a question or did you already use the 2nd option in grub to reinstall dsm?

yes, i used the same new intel source code as for the 6.2.2 drivers, it should be igb.ko

you will have panty of trouble when using raid0 volumes as single disks, you will not see serial numbers in dsm, smart will not work, and if a "raid0 disk" fails it might be hard to find out what real disk it is - plenty of things that can go wrong leaving you with a damaged raid you might never get repaired just invest the sub 100 bugs for a "old" sas controller with it firmware or look into ahci multiport controllers (5 port JMB585 based looks nice but not tested yet)

should work that way send me a dmesg (complete) you could also try a clean install with your usb to a single empty disk to check if its related to your installation or hardware the usb is already at 6.2.3 so nothing can change by a clean install, when you have your result you can reconnect the "old" disks and boot as usual

that might be the problem, the mac address is set in grub.cfg and it should be unique, also in virtualbox the mac of the grub.cfg and the one set for the vm's nic need to be the same

you should be able to read/write both partitions on linux (dsm) mkdir -p /mnt/synoboot1 mkdir -p /mnt/synoboot2 echo 1 > /proc/sys/kernel/syno_install_flag mount /dev/synoboot1 /mnt/synoboot1 mount /dev/synoboot2 /mnt/synoboot2 if windows 10 is to "new" and does not show any driver letters then you can try "Ext2Fsd" 0.69 (Ext2 Volume Manager) to access 2nd partition by assigning a drive letter and overwite files there you also can create new usb, use osfmount to do whatever is needed (grub.cfg, extra/extra2, zImage, rd.gz) and the write it to a usb with win32diskimager (there are other tool able to handle boot images like rufus, WinUSB, UNetbootin, i have not tried yet one one these to read runs loader from usb)

cant see why doing a overcompensated approach like this, just run syn-b and win10-lite as vm in vmware workstation if isolation is needed then use virtual nic's or vlan

https://xpenology.com/forum/topic/14122-trouble-with-install-on-hp-compaq-8300-sff/?tab=comments#comment-106362 https://xpenology.com/forum/forum/98-member-tweaked-loaders/

you could also look in the section where people reporting about installed updates, there are details about the hardware in use https://xpenology.com/forum/forum/78-dsm-updates-reporting/ btw. your controller might be a limiting factor 9215 is only pcie 2.0 1x, ~500MB/s for 4 disks is not much i'd suggest at least a marvell 9235 with pcie 2x (on a 2x/4x card) like SI-PEX40062 atm i'm favoring a JMB585 based card as it comes with pcie 3.0 and 2 lane, like SI-PEX40139 https://sybausa.com/index.php?route=product/product&path=64_181_85&product_id=1027 i did order a JMB585 based controller but have not received it yet that alone limits you choices a lot braswell, appololake and geminilake based cpus are reported to work with 6.2.3 and trancoding but i guess most will only have 2-4 sata ports ASUS H61M-A would be no good choice as it only supports 2nd/3rd gen intel and 918+ needs at least a 4th gen intel same goes for you Gigabyte GA-C1037UN-EUCELERON1007U, ivy bridge, 3rd gen cpu you might also have a look of at the capabilitys of cpu's when it comes to trancoding https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video

das ist eine eher lose struktur von leuten die sachen in ihrer freizeit machen, kein projekt in dem sinne das es da eine leitung gibt und arbeit verteilt wird

yes, Modell: PCE6SAT-M01 https://www.amazon.de/Bewinner-SATA3-0-Erweiterungskarte-Express-Erweiterungskarte-Riser-Karte-Kompatibel-default/dp/B082VFSYTP -> in description marvell 88SE92xx (4 port ahci) + ASM 1092 (port multilier) https://www.asmedia.com.tw/eng/e_show_products.php?item=141&cate_index=138 "ASM1092 is Serial ATA port multiplier controller, supporting one host ports and two device drives" so forget about it as 6port with dsm, its 4 what you can use and dont forget about it being pci1x, it will result in a bad performance

falls man das so nenen will dann ist es im moment immer noch https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ 6.2.3 wäre schon gut, diese version ist zwar neu aber auch wieder treiber komatibel zum ursprünglichen treiber satz der mit jun's loader kommt (6.2.2 war da speziell aber die sit jetzt geschichte) ersteres ist ganz normlal direk auf einer hardware installieren, esxi meint das auf der eigentlichen hardware esxi (hypervisor) läuft und darauf als VM dsm/xpenology