IG-88

der lizenz check ist an die SN und mac gekoppelt und vermutlich wird das nicht nur beim installieren geprüft aber ein wechsel der hardware (andere sn/mac kombination) kommt auch bei orginal systemen vor also kannst du für dieses szenario die synology FAQ/KB checken

i added a note to the 1st post that these packages are not maintained anymore, beside this there are problems with these drivers in its latest version with kernel source 3.10.105 (3615/3617 DSM 6.2) so beside the existing driver from last year in 3615/3617 there will be only newer version in 918+ (so even with 6.2.3 and latest extra.lzma there would be no recent driver for 3617, just a older one supporting "most" r8125 cards) if the existing driver in 918+ works for your card then it will work with the 3615/17 version too as it uses the same driver version (from last year) you can update to 6.2.3 by using a new usb flash drive change grub.cfg to the usb's vid/pid and then boot the system with it (instead of the 1.02b usb) just by booting the loader nothing will happen to the installation (dsm system) on the disks if you find it in network with synology assistant and it tells you you 6.1 can be migrated to 6.2 its working properly as network and disk drivers are detecting the hardware needed to work properly (there is nor real difference in disk driver support with 6.1 and 6.2, maybe some refinement in mvsas driver in 6.2 to detect more vendors) the thing with loader 1.03b is that it needs csm/legacy mode in uefi bios and it needs to boot from the legacy usb device that might only appear after booting once with csm active, so activate csm, save bios settings, boot again, go into bios and check the bootable devices, it its name starts with uefi its the wrong one, its usually simply the name of the usb device without uefi in its name (on one of my systems i see three usb boot devices two with uefi and one without in its name for the usb flash drive) so continue here for reading about 6.2.3 (all the procedures for preparing the usb are the same as with 6.1) https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/

if all drives are on the lsi's then it will exeed the 16 port/drive limit of 918+ because the 2 sata onboard will be 1st and "block" the two drive positions connection the two cache drives to the onboard ports would be a simple solution (at least better then making changes to synoinfo.conf)

du kannst die lizenz nicht direkt auf der xpenology installieren aber es müsste gehen wenn du sie auf der 218+ installierst und über cms im netzwerk teilst solltest du sie nutzen können https://xpenology.com/forum/topic/34502-surveillance-station-lizenz/?do=findComment&comment=170511 ansonsen gibts eine alte version von ss die 4 kameras kann (-> tutorial section) und es gibt wohl auch gehacke versionen (aber die sind hier mit links usw. nicht willkommen - zumindest nach den offiziellen regeln und solche sachen können natürlich auch schadsoftware enthalten)

in theory it should work with this (they did not provide it with 6.2.2 source) https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/25426branch/broadwell-source/libhydrogen.txz/download

da habe ich mich unpräzise ausgedrückt, ist die nutzbare kapazität in summe die auf reisen dabei ist (genau genommen sind es sogar fast 2TB mit dem interen speicher der geräte) sind 2x 512GB und 2 x 400GB wobei die 512er in Telefon und Tablet stecken und die 400er be Bedarf mitgeführt werden mit einem usb-microsd adapter und usb otg adapter kann man die auch an die geräte anschließen, aber einlegen geht natürlich auch nur beim "vorbereiten" der karten muss man etwas zeit einplanen die preiswerteren karten schreiben nicht grade mit 100MB/s, eher 10-20MB/s aber ich denke der odroid ist ein nettes package und wenn man den mit 1-2TB sata ssd bestückt braucht es keinen cache, die vm's von sata ssd sollten flott sein (wenn es nur kopien vom haupt nas sind braucht es kein raid), aber wlan ist mit dsm nicht so einfach, da braucht es evtl. noch einen extra AP den man ans nas anschließt wow, ich glaube das wäre mir zu anstrendend, ich würde wohl versuchen mit der bahn oder dem flieger ans ziel zu kommen und vor ort dann ein fahrrad benutzen um von ort zu ort zu kommen wandern so zwischendurch, oder gleich fernwanderwege oder pilger pfade)

das mit dem transcoden be synology ist on the fly in echtzeit, man kann natürlich auch filmweise umrechnan lassen aber gedacht ist es eigentlich für streaming des films ob man das nun braucht hängt von den gewohnheiten ab, ich brauche es eigentlich nicht ich habe 1.5TB in microSD, damit kann man schon einiges auf Telefon und Tablet mitführen ohne sich gedanken über WLAN, Empfnag, Bandbreite oder Kosten zu machen wenn man eher daten sammelt und vm's bzw. dicker macht kann das interessant sein aber da bei 16 cores (inkl. HT) schluss ist hat das auch seine grenzen (zumindest baremetal) ab einem gewissen punkt fährt man mit einer dsm vm besser was die hardware nutzung angeht aber bei unterwegs dachte ich weniger an vm nutzung sondern an medien und da ist eine "kleine" cpu wie gemini lake ausreichend (als zweit NAS für unterwegs) man kann aber auch gänzlich auf nas verzichten und neben microsd karten auch usb otg einsetzen, man kann große usb sticks so anschließen aber auch ein gerät als storage von einem anderen aus nutzen, mache ich z.b. beim ebook reader (mit android) so, der hat "nur" 32GB aber man kann immer vom Telefon oder Tablet nachschlag holen (und die haben beide gruße microsd karten) und rein theoretisch kann auch handy/tablet einen hotspot auf machen und seine medien über wlan anbieten

prüf doch mal welche vid/pid der usb hat, in der grub.cfg gibt es default werte die in der realität auch vorkommen set vid=0x1908 set pid=0x0226 versuch mal "lsusb" auf der kommandozeile, das sollte dir die usb geräte inkl. usb stick auflisten

klingt eher wie ein mobiles datacenter, imho overkill und schluckt auch reichlich strom ich würde da eher zu gemini lake basierten sachen raten, geringer stromverbrauch, hardware transcoding und nicht so teuer außerdem solltest du ein paar eigenheiten von DSM kennen z.b. das m.2 nvme nur als cache geht, nicht als datenlaufwerk, ginge aber mit m.2 sata oder das du bei den amd's die gpu nicht nutzen kannst

for that reason i wrote some information about that in the 1st post post of the 6.2.3 driver thread https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ it got a little untidy over time but beside the red warnings you should find what you need when start reading from this point "... i completely removed jun's i915 drivers from the ..." as drivers are different with 6.2.1 and 6.2.2 and you use the 6.2.2 adapted extra.lzma, then for 6.2.3 you will need jun's old extra.lzma (extract with 7zip from original loader) or my new one made for 6.2.3 (if the microserver does not have any "special" added hardware the old extra from jun would be enough)

dsm uses normal linux stuff like mdadm and lvm2 to create its raid volumes and a normal recovery linux can be used if needed https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/ but the loader can easily reproduced if you have thing documented you could save the grub.cfg you modified for the loader and the single really important thing to know is that the vendor and product id of the usb used for booting needs to mach the entry's in grub.cfg often the bios settings are worth documenting too its also possible to make a copy of the usb with tools like dd or Win32DiskImager, but when using a different usb then you will need to match usb's vid/pid again to the new one so its of not that much use to have a backup of the usb, having a plan, a documentation and knowledge is more important usb's failing is a rare case more often its disk trouble and having a backup of the data is most important as in most cases the hardware used is not as reliable as the one used in a new original synology system (they migh look under powered but beside intels atom disaster the nas systems hardware is working >5 years reliable - my old 509+ is still working at its 3rd home as backup unit) you will find the information you need in the tutorial, just replace 1.02b with 1.03b and 6.1 with 6.2, the steps are the same, only important to know is with 1.03b you will need old legacy bios mode aka CSM mode in a uefi bios https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ edit: you can use synology knowledge base for most things and even they tell people to use a recovery linux if things go wrong and they need access to the content of the disks https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Storage/How_can_I_recover_data_from_my_DiskStation_using_a_PC

thats the best information about it afaik https://community.synology.com/enu/forum/17/post/54396 alsokeep in mind with the 6.x loaders from jun we are bound to use the original kernel, so even if you find out how to mod the kernel source, you can't use it only if its a loadable *.ko kernel module then it would be possible if its that important i'd suggest using omv if you can baer it, there are two 8port ahci controller with 2 pcie 2.0 lanes, beside lsi sas controller (only 8 port hba's are usually cheap) there is not much look for "IO Crest SI-PEX40137" and "SSU SA3008" for the two 8 port ahci controllers lsi 9211-8i and it mode for lsi sas (there are lots of oem controllers too) also keep in mind that xpenology is limited to 24 drives so far, quicknicks loader for 6.1 might do more but no one took the time to find out if its really working and how its done

there are some exceptions on boards like apollolake, geminilake, usually 2 real onboard (soc) and when 2 more are added with a asm1061 then its one pcie lane with pcie 2.0, limiting the 2 ports to ~500MB/s together - not usable for SSD

there is a working r8125 driver already in my extra.lzma, there might be very few newer cards that need a newer driver (possible for 918+) but the chip on that odroid is older for sure

yes with a patched i915.ko (i do provide that in my 6.2.3 driver thread) but your systemboard is only ok for 8th and 9th gen cpu's, i use a i3-9100 on a B365M board from Gigabyte 8086:3E92 => iGPU UHD 630, Low End Desktop 9 Series (original driver) -> 8086:9BC8 => iGPU UHD 630, Low End Desktop i5-10500, i5-10600T and lower there are higher tier 10th gen that might not work, only had one feedback -> one user negative feedback for a i9-10900 (8086:9BC5) system does not boot anymore - seems to be a solid hands off?

also dsm supports 2nd factor, that might be useful too https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Management/How_to_add_extra_security_to_your_Synology_NAS#t6 hiding it behind a firewall and using vpn to access it might be even better

https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ !!! still network limit in 1.04b loader for 918+ !!! atm 918+ has a limit of 2 nic's (as the original hardware) If there are more than 2 nic's present and you can't find your system in network then you will have to try after boot witch nic is "active" (not necessarily the onboard) or remove additional nic's and look for this after installation You can change the synoinfo.conf after install to support more then 2 nic's (with 3615/17 it was 8 and keep in mind when doing a major update it will be reset to 2 and you will have manually change this again, same as when you change for more disk as there are in jun's default setting) - more info's are already in the old thread about 918+ DSM 6.2.(0) and here https://xpenology.com/forum/topic/12679-progress-of-62-loader/?do=findComment&comment=92682 I might change that later so it will be set the same way as more disks are set by jun's patch - syno's max disk default for this hardware was 4 disks but jun's pach changes it on boot to 16!!! (so if you have 6+8 sata ports then you should not have problems when updating like you used to have with 3615/17)

not sure if that will help, if thats limiting i'd expect to see a high cpu load when using the raid system to copy data from my own systems i had the impression the lsi sas controller did not perform as good as the ahci pcie 3.0 controllers i used later what you can try for free is to use all 6 onboard sata and see if the performance is any better when the disks are connected to a ahci controller (and write cache for the disk is on)

you should try the forum search, it can be helpful https://xpenology.com/forum/topic/39706-installation-on-iomega-px4-300r/

then you should continue here https://xpenology.com/forum/topic/24864-transcoding-without-a-valid-serial-number/

no NCQ (sata native command queuing) https://en.wikipedia.org/wiki/Native_Command_Queuing also try to disable VT-d in bios, might have effects too

1st check if something in /dev/dri is present after booting if not check /var/log/dmesg if that woks out and the driver is working properly you can continue

QLC drives, if the cache is filled up you will see a terrible write performance, imho QLC is the equivalent of the shingled recording but for SSD's (and why only read cache if you have two)

the files are named like that /var/log/dmesg /var/log/messages there are tons of corrected and uncorrected btrfs errors also two docker crashes you should have a backup and you should backup whatever you still need and is not recent on your backup check the hardware, there might be ram problems or something else, the file system should not break down like this i use a very similar hardware, gigabyte b365m-hd3, i3-9100, JMB585 added, no problems like that a few days i found out that you can have NCQ problems with WD disks and jmb585 but there where so problems visible beside some log entries

as the cpu seem ivy bridge or earlier forget about loader 1.04b and 918+ this will be your read for starting https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/ loader 1.02b 3617 dsm 6.1 would be a good start, if you get this installed you can try loader 1.03b 3617, that one needs CSM mode and the usb boot device also needs to be legacy (non-uefi) that one need to be in IT mode (aka HBA mode) you can google that and will find lots of tutorials on how to flash it, like this one https://www.taste-of-it.de/flash-dell-perc-h310-mit-lsi-9211-8i-it-mode/