IG-88

hallo, ich nehme mal an du hast so eine hp storage works kiste noch nicht in natura gesehen zum einen braucht man für jede platte einen hp spezifischen wechselrahmen, den bekommt man natüelich automatisch wenn man hp platten kauft aber das wird nicht billig, evtl. bekommet man die rahmen auch einzeln oder mit extrem alten platten bei ebay aber das kostet halt wieder außerdem ist es eine SFF enclosure, SFF = "small form factor" = 2,5" (deine 8 tb platten sind 3,5" die passen da nicht) die hp sachen sind fast immer extrem custom, da kann man nicht so leicht ein board (itx?) reinsetzen, da braucht man unter umständen viel enthusiasmus incl. einer flex um platz zu schaffen, schon allein die netzteile anzuzapfen kann eine herausforderung werden ich rate dazu sich mal bei hp die unterlagen (am besten das service manual) anzusehen um was über den aufbau zu erfahren, dann wirst du sehen was ich meine btw. die dinger sind laut, weil für serverräume vorgesehen man könnte sich natürlich einen SAS controller kaufen (mit externem anschluss) und so ein enclosure über kabel an einen server anschließen aber in summe kostet das so viel da kann man auch diesen (in der regel LSI) controller direkt nehmen und intern in einem größeren gehäuse alles direkt verkabeln falls man hardware gestützes video transcoding der intel cpu nutzen will dann muss man genau sehen ob das wurklich geht, das 916+ image kann das zwar aber nur für bestimmte cpu's und dann auch nur den synology eigenen weg (der weder ffmpeg noch plex beinhaltet) ich hatte da mal was im englischen bereich zu geschrieben (vor kurzem scheint sich da evtl. beim nachinstallierbaren 3rd party plex was getan zu haben aber ob das jetzt wirklich hardware transcoding unterstützt und unter welchen bedingungen sollte man da noch mal nachlesen) je nach zielausbau (8, 10 oder 12 platten?) und den anforderungen an den geräuschpegel sind 700€ incl. gehäuse usw. sehr sportlich bis unrealistisch, vor allem wenn man wirklich funktionssichere hardware will, wenn man sich so einen super billigem 4 oder 8 port controller kauft der aus 1-2 echten sata anschlüssen mit multiplexer basiert dann ist die performance murx und der bitsalet garantiert wenn man mal an ein xeon boad denkt, den xeon und einen 8 Port LSI controller dann dürfte das budget schon locker ausgeschöpft sein, fehlen noch ram, netzteil und gehäuse (+kabel) und evtl. sollte man sich einen pcie platz für einen optionale 10Gbit karte freihalten PS: und Wakü - vergiss das mal schnell wieder bei so einem system mit vielen platten, wirklich passiv geht das nicht, man braucht auf jeden fall lüfter da lohnt sich das Wakü zug nicht und es wird auch zu teuer, lieber ordentlcihens board, controler und ecc ram, solcher eye candy kram ist was für leute die geld übrig haben (imho) PSS: wenns wirklich leise bei 10-12 platten sein soll ist ein eigenbau (mit mittelmäßiger optik) vermutlich das beste (ich habe hier 11 platte wohnzimmertauglich verpackt) - hägt aber auch ein wenig vom angestebten form faktor des gehäuses ab, fast alle kaufbaren gehäuse haben kein wirklich gutes lüftungskonzept für so viele platten und sind entsprechend inefektiv oder laut )oder beides)

this stuff is 7 years old, kernel 3.10.102 (base of dsm 6.1) already contains it (i've checkt the pata_via.c) but as the driver compiled for dsm 6.1_15047 does not work for newer dsm 6.1 builds (synology further modded kernel with no source availible) ... see my comment here

i found this list of kernel optins to activate hyper-v CONFIG_HYPERVISOR_GUEST: Processor type and featueres > Linux Guest Support CONFIG_PARAVIRT: Processor type and features > Linux Guest Support > Enable paravirtualization code CONFIG_PARAVIRT_SPINLOCKS: Processor type and features > Linux Guest Support > Paravirtualization layer for spinlocks CONFIG_HYPERV: Device Drivers > Microsoft Hyper-V guest support > Microsoft Hyper-V client drivers CONFIG_HYPERV_UTILS: Device Drivers > Microsoft Hyper-V guest support > Microsoft Hyper-V Utilities driver CONFIG_HYPERV_BALLOON: Device Drivers > Microsoft Hyper-V guest support > Microsoft Hyper-V Balloon driver CONFIG_HYPERV_NET: Device Drivers > Network device support > Microsoft Hyper-V virtual network driver CONFIG_HYPERV_STORAGE: Device Drivers > SCSI device support > SCSI low-level drivers > Microsoft Hyper-V virtual storage driver CONFIG_HYPERV_KEYBOARD: Device Drivers > Input device support > Hardware I/O ports > Microsoft Synthetic Keyboard driver CONFIG_FB_HYPERV: Device Drivers > Graphics support > Frame buffer Devices > Microsoft Hyper-V Synthetic Video support CONFIG_HID_HYPERV_MOUSE: Device Drivers > HID support > Special HID drivers > Microsoft Hyper-V mouse driver unfortunatly the first three options are no drivers that can be loaded as module they are kernel options, as they will have to be compiled directly into the kernel (provided by jun including the nice tricks to start on non synology hardware) they are not present so having the hypery-v drivers might/will be of no use also in kernel 3.10.102 (synology dsm 6.1) there was so option for "Microsoft Synthetic Keyboard driver" the resultung drivers are like this LD [M] drivers/hv/hv_balloon.ko LD [M] drivers/hv/hv_utils.ko LD [M] drivers/hv/hv_vmbus.ko LD [M] drivers/scsi/hv_storvsc.ko LD [M] drivers/hid/hid-hyperv.ko LD [M] drivers/net/hyperv/hv_netvsc.ko LD [M] drivers/video/cfbcopyarea.ko LD [M] drivers/video/cfbfillrect.ko LD [M] drivers/video/cfbimgblt.ko LD [M] drivers/video/hyperv_fb.ko but imho are useless atm and beside this i will not try/experiment with hyper-v and xpenology, i use barematal and for testing virtual box, no need for hyper-y from my side (there goes another hour of my time without a useful result)

looks like there are some hyper-v drivers in kernel source 3.10.102 like in drivers/net/hyperv/ i will try to compile it and test if it will load in newer 6.1 versions then 15047

i compiled the module but as the sata_via it does not load on newer 6.1 kernel revisons then the original 15047 (from what we have the kernel source availible) it might only be used with that version but then you cant update to newer 6.1 versions (kind of pointless as there will be lots of security and other fixes missing) # insmod /lib/modules/update/pata_via.ko insmod: ERROR: could not insert module /lib/modules/update/pata_via.ko: Unknown symbol in module

if the network driver does not work it's only logical that there will be no webinterface over network the tg3.ko is alredy part of the original extra.lzma from jun if you google your error you will find that this is no synoloy specific error "inserting the broadcom module before tg3 makes things appear to load" as there is no broadcom.ko in the extra.lzma from jun and in the kernel source of 6.1_15047 there is nothing to find in the drivers/net/ethernet/broadcom makefile that would create a broadcom.ko so

lies dich mal hier im forum zur nutzung von hyper-v und dsm ein, denn ich denke nichts anderes wird der Virtual Machine Manager sein, hyper-v vm's verwalten was ich so im hinterkopf habe besagt das es nicht oder nicht richtig geht, esxi ist aber an sich keine so schlechte "alternative" und gut erpobt, wenn du unbedingt win10 als basis willst bleibt dir aber noch oracle virtual box unter win10 um dsm in einer vm laufen zu lassen, das geht auf jeden fall (mache ich selbst für tests)

hi, vermutlich gehts um den: Silicon Image SATA support sata_sil.ko ich hatte den in eine extra.lzma mit zusätzlichen treibern eingebaut aber wieder entfernt da er nur mit der originalen 6.1 (build 15047, dafür geht es bis update2, mitte mürz) lief wenn du dir die als 6.1 installierst und bei der "ersten" version bleibst könnte es gehen (also keine 6.1.1 oder 6.1.2 solange es keinen neueren/passenden kernel source von sysnology gibt) hab das hier noch liegen und kann es dir zum testen rüberschieben, aber wenn man voll auf sicherheit steht ist das natürlich nix, da sysnlogy nur updates für die letzte 6.1 liefert und das ist die 6.1.2 wäre also die hier mit der du das testen könntest http://download.synology.com/download/DSM/release/6.1/15047/DSM_DS3615xs_15047.pat plus das was hier steht (bei juns loader die extra.lzam ersetzen) aber mit der alten version in der noch der treiber für sil mit drin ist (link würde ich die per pm schicken)

if hotswap is optional then a Streacom F12C might be an option as i decided for my build hotswap is optinal and low noise and size is more important (depth had to be <40cm), i use a modyfied desktop case Silverstone SST-GD09B, 10 disks was start with the option of 2 additinal disks (11 installed yet) - its a very tight fit and if a disk is to change it takes a littel effort but as this happens 1 or 2 times in 5-6 years (HGST drives are riliable) its ok as the desktop case is mini-itx for the board and one pcie slot is to expect the storage or 10gbit has to be onboard, i useed a ASRock C2550D4I (12xsata), but as you are planing for a i7 (or its xeon counterpart) it has to be something different

youn dont have to, the howto does only discribe the way how to compile a driver/kernel module for the kernel you alredy use i dont know how amd support was implemented on 1.01 loader, i expected it to be a special kernel with fixed/build in options linux as base system has the kernel, the "main" file (compiled kernel) is loaded by the boot loader and contains the most important stuff to get the base running (like prozessor support), if everything would be in the kernel (one file) it will be big and harder to handle/load as most of the theoretical hardware is not peresent in the system (kernel precompiled by the distributor) so there ist the additioal option to have kernel parts (drivers) as modules and load them later (if done manual like "insmod driver_xyz.ko") kernel come in different versions and as this versions are not compatible everry driver/kenel module hast to be compilied for the kernel from the source of that kernel as 1.01 is for synology dsm 6.0.2 based on kernel 3.10.77 (synology modify's the kernel and give them a internel number counting up so dsm 6.0.2 is 8451) and dsm 6.1 is based on kernel 3.10.102 it will not be possible to mix driver/kernel modules as they are for different kernels (based on kernels from www.kernel.org) in one "line" (dsm 6.0, dsm 6.1) usualy sysnology stays with a kernel but modify's it so the synology intenal build numer rises like seen in 6.1 -> 6.1.1 -> 6.1.2 that can also have consequences if you use a kernel module from 6.1 for 6.1.1 or 6.1.2 as it is the same linux kernel it might work but as seen in my howto with the extra.lzma there where some kernel modules not working anymore for 6.1.1 and it might be more with 6.1.2 as there ist no kernel source for the sysnology internal builds for 6.1.1 and 6.1.2 i can not compile directly for this version, if seen dogmatic the only version my extra.lzma is good for is 6.1 build 15047 as for this version i have kernel source (https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/) for newer versions synologhy does not provide the modifyed kernel source (as they should if it comes to GPL ?) synology dsm is something like a closed source or walled garden system and they do not embrace the open source / GPL thought, they dont like the efforts of xpenology (as they might see it as "hacking" there IP) but as they use open source for dsm they are also bound to the GPL and other open source licenses they use and have to share (but thats just my point of view)

i guess you should specify the max. dimensions you hahe in mind (if there are any) maybe it hast to fit somewhere and there is a mx high or depth does it have to be quiet (living room), does it have to look good - most 19" rack server are good for the das but will be no fit for the livingroom dependent on that it will deduce the options for the mobo size (no full atx?) also to keep in mind is the option for a 10 gbit nic, together with a lsi 8port sas controller you may need a board with 2 pcie slots or one of the two options has to be onboard, if going with a 8port controller the sata onboard count has to be 4 to reach the 12 ports maybe just google a little for nas builds (some portals have a hardware section where people show/describe there hardware) maybe try freenas you will get a idea and imagination of what is possible and what the costs are up to 8 is usualy easy 12 is much more chalanging it has to be compact or hot swap and silent

as amd support is not a driver/kernel module that can be compiled additionaly (thats what my extra.lzma is) - no and guess if it was just "easy" jun would havealready have done it with the 1.02b

did you tryed with my extended extra.lzma? (for details how to use see my comment above about the c600 chipset)

just uninstall and install the package, its just a script that copy's files on installing the script and after replacing the content of the root file system the files are missing a complete new/big version like 6.1.1 and 6.1.2 replaces the content of /dev/md0, so modificacions like changed scripts, changed configs - like max. disks if you open the *.pat with 7zip you will find a hda1.tgz, the content of the root file system aka the new dsm version so if you have modifyed the synoinfo.conf you also have to redo the changes would be intresting to know what experiance people have that user more then 12 disks after such update as the count of disks is restet to 12 and the actual raid in place contains a more disks (i'd expect a crashed raid after update if you boot with the new version without modyfiening it before the first boot)

you mighjt start improving by using the search function or just readt the first page of the board, just 2 threads below your new post Juns Loaders support : Asrock C2550D4I ?

in theory the c600 chipset should work with my extra.lzma and the 3615xs image (loader 1.02a or 1.02b) Intel(R) C600 Series Chipset SAS Controller isci.ko

thats not what i wrote, dsm brings some drivers within itself (usualy for the hardware used for original synology boxes) and jun (additional to make dsm work on non synology hardware) also provided drivers within the file extra.lzma with the bootloader as i don't know exactly under what conditions it happend (in some cases people might not had seen the effect because the hardware was working with the drivers synology provides directly in dsm) the drivers additionaly provided by jun in the extra.lzma seem not to work when updating a 6.x version with a complete new/full *.pat file (like 6.1 -> 6.1.1, 6.1.1->6.1.2) where the complete boot partition is inside the file, on the other hand fresh installs always worked when you search "/lib/modules/update" then you will find a lot like tis

"its an old script bug due to my oversight, I am uploading a new version to fix it, hopefully without introduce new bugs"

yes the files to download are for all three images (thumbs up to jun for also doing 3615xs) depends on your point of view, technicaly it's still the same kernel in 6.1.2 so it works but as 1.02a2 still has the bug to not load the modules added by the extra.lzma (all drivers not provided by synology, as vmware and so on) its likely it will prevent the system from booting after the backup. can be fixed by copying the drivers as mentioned before i would recommand to first using the running installation with 1.02b und update dsm after that (thats what i did and it worked)

just migrated from 10.2a to 1.02b (only had to recover on 1st boot with synology assistant, took just a few seconds) and did update from 6.1.1 u4 to 6.1.2 - no problems, the fix for loading the modules from lib/modules/update seems to work as intended bare matel , Asrock C2550D4I, ds3615xs

just replaced my usb image jun 1.02a with jun 1.02b (had to repair with synology assistant after first boot, took a few seconds, boot after this was ok) and then updated from 6.1.1 u4 to 6.1.2, no problems (as expected, the kernel/drivers are still the same, the problem that rhe drivers in /lib/modules/update are not loaded should be fixed with 1.02b - seems to work for me)

versuch doch mal den 1.02a ob damit etwas gefunden wird (nur mal so zum testen ohne update der installierten dsm version)

bare metal with just the extra.lzma that comes with jun's loader 1.02a, i only added a evdev.ko for acpi button shutdown (now a availible as part of a spk package someone made for that purpose) btw. you could haven known earlier, i already reported this in april, the search function can be useful

atl1c.ko ist das kernel modul zu dem chip und der ist bei jun 1.01 mit dabei, sollte also theoretisch gehen versuch mal den lokalen "Synology Assistant" den man sich bei Synology herunterladen kann

hi, it does 1.02a, DS3615xs, 6.1.1 15101 U4 all 12 sata ports working, onboard nic also working