IG-88

should also be fine with 6.2.3 when the new extra for 6.2.3 is used https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ when the system is up you would remove the usb (its only mounted when booting), replace the extra.lzma, put the usb back in and then update normally with the webgui to 6.2.3 (it will be 2 steps/reboots as there is already a u3 for 6.2.3)

to complete it you could now also change the mac in grub.cfg to the real one, needed for WOL but also convenient when the system always has the same mac in network you use a wrong editor? any reason you found why the old grub.cfg did not work? did you use a wrong editor?

save your grub.cfg and replace it with the original from the *img file (can be opened with 7zip to extract) only edit the usb vid/pid (keep in mind you need unix aware editor with LF instead of CR/LF - like notepad++ or ultraedit) and then try to boot with it

hier mal die asm1166 die es zu geben scheint 1. die karte die ich habe pcie 4x karte (der chip kann aber nur 2 lanes pcie 3.0) 2. die gleiche karte aber als pcie 1x karte (A02 statt A01 im Aufdruck auf der Platine) - ich glaube das wäre im moment die pcie 1x karte mt den meisten ports ohne sata multiplexer 3. die "alternative" Karte pcie 4x

war da dsm installiert? was ist mit der platte passiert das die "wiederherstellen" sagst dsm erzeugt grundlegend sachen die man mit einem normalen linux auch wieder zugänglich machen kann (mdadm und lvm2) https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/ also mit fertig installirten usb/platten kombo auf das system das nichts im netz angezeigt hat? wird der 8125 nic erkannt (im bios aktivieren)

na sowas, da hat sich auf dem bild auf der homepage beim hersteller ein slot getarnt ok ,dann brauche ich kein dmesg, da passiert offensichtlich der gleich murx wie bei mir wenn die platten auf 39-42 funktionieren und in ein raid eingebunden sind läuft es scheinbar, da hatte ich angenommen das dsm da schwierigkeiten macht bei bedarf müsste ich das eigentlich nachbilden können, genug verschiedene controller habe ich ja rumliegen (in kürze auch einen mit jmb582 als pcie 1x karte) wäre also noch zu sehen was das deine asm1166 karte ist, ein link mit foto wo du sie online estanden hast sollte auch reichen, der aufdruck ist bei mit auf der vorderseite in der nähe des slotblechs neben dem kühlkörper, eigentlich nicht zu übersehen

there should be a proper ffmpeg version in the DVA3219 image or at least in the DVA version of the SurveillanceStation package (the dva version of SurveillanceStation uses nvidia features for tracking)

ist ein uefi bios, loader 1.03b 3615/17 geht nur im CSM mode ist hier dokumentiert https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ nach csm mode aktivieren muss man einmal booten und dann im bios dafür sorgen das das nicht uefi usb device gebootet wird (legacy usb boot device) das tacht unter umständen eben erst auf wenn man einmal mit csm eingeschalten gebootet hat

das ist zum boote/installieren unwichtig, die braucht es nur für WOL nicht mal die usb vid/pid ist zum booten und finden im netzwerk notwendig, die "braucht" man erst wenn man das *.pat file auf die hdd installiert so lange man nichts im netzwerk findet muss man sich nicht mit der grub.cfg rumschlagen, da get es nur um bios einstellugen (csm mode), welche cpu man hat und treiber (in extra.lzma)

kannst du in den laptop testweise eine leere sata platte einbauen da dsm installieren und dann usb + disk an den rechner bringen der probleme macht?

nein, es gibt einuge die eine 10th gen cpu verwenden ohne das irgendwas komisches passiert

https://xpenology.com/forum/topic/28183-running-623-on-esxi-synoboot-is-broken-fix-available/ i dont know what controller you are using but there are newer lsi sas drivers in 3617

kannst du mir mal ein dmesg davon schicken, würde mich mal interessieren bei dir auch 32 hdaX devices vom asm1166 produziert werden (so lange die karte "hinten" ist macht das nichts aber wenn sie zwischen drin sitzt und 32 statt 6 hadX belegt rutschen die anderen sogar hinter die 24er grenze und dann hilft vermutlich nicht mal manuelles anpassen der synoinfo.conf) wäre auch gut zu wissen welche karte mit asm1166 du genau hast, auf der plaine meienr karte gibts zumindest etwas (die karte gibts von verschiedenen chinesischen vertreibern, meist sind es nur 2-3 wirklich verschiedene karte die verkauft werden) PCE6SAT-A01 VER006S außerdem frage ich mich grade wir du drei pcie karten in das Asrock J4105M bekommst das ja nur 2 pcie slots hat, hast du den M.2 key E mit einem adapter zu einem pcie slot gemacht?

afaik these are are dummy devices made present to fool dsm about being on the original hardware, dsm checks the presence of some pci device id's to make sure its running on a synology hardware, thats part of the "magic" in jun's loader (and one of the reasons a loader is specific for a certain dsm type like 3615, 3617 or 918+) that was the reason for the link and my comment about 5th gen cpu not having much gain over the 4th gen cpu you already use you did not specify h265 as needed for you project or i would have marked that explicitly a problem with your plan to use a 5th gen cpu you file system (with its underlying raid) might not be up to the task to deliver a constant 4k file stream to transcode, just having the cpu/gpu does not make it work, the system as a whole needs to be seen and i'm not sure the low iops of a raid from conventional hdd's can do this, you should read about that or ask people with more experience before assuming it will work (imho) GPU Nvidia is not supported and the last experiment with that and a plex owner did not work https://xpenology.com/forum/topic/22272-nvidia-runtime-library/ just making a kernel driver is possible but the whole driver construct around it with its libs and dependencies in a appliance with all its limitations ... its no like on a normal (maintained) linux where you can use apt and you are done you can join the effort and find out whats possible (like above), i already lined out what can be tested (driver and ffmpeg) without compiling anything new if you thinking about a new systemboard anyway, you could just use a gemini lake to have h265 support (or skylake or newer cpu), no need for nvidia at all with a intel qsv h265 capable cpu

schon mal dazu im internet gesucht? scheint ja eher kein xpenology/dsm spezifisches problem zu sein, auch andere z.b. mit OMV haben das problem http://forum.asrock.com/forum_posts.asp?TID=6159&title=cannot-start-up-from-the-network-with-wake-on-lan https://www.technikaffe.de/forum/index.php?thread/1360-wake-on-lan-mit-asrock-j4205-itx/ https://www.elefacts.de/test-57-asrock_j4105_itx_im_test__mini_itx_mit_4_kern_gemini_lake_prozessor "Auf Wunsch lässt sich mit der Option PCIE Devices Power On einstellen, dass das System sich mit einem WOL-Paket aufwecken lässt." prüf mal zu sicherheit ob der nic auch mit seiner echten adresse in dsm zu sehen ist und check die auch noch mal auf übetragungsfehler (z.b. im bios nach der mac schauen, die meisten uefi systeme haben das auch im bios einsehbar) auf meinem system habe ich nach aktivieren in der gui folgendes wenn ich den nic abfrage (ethtool eth[x]) Supports Wake-on: pumbg Wake-on: g

9100 works ootb with synologys i915 driver from 6.2.3 918+ https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ open "iGPU device ID's supported by synology's i915 driver (Reveal hidden contents)" and you can check the id's of supported devices, with a patched driver it will even work up to 10th gen lowend cpu's

power consumption i that area will lead you to apollo lake / gemini lake type cpu's, you should not just look for intel, there might be other interesting units from asus, gigabyte, msi, ... biggest problem with these UCFF units is that you wont get them with 2 x sata (for a nas you usually will use raid1 or you would need to run two units syncing all the time) they usually come with one sata and a m.2 slot (nvme & sata capable), as dsm cant handle nvme as data drive (only cache) you wild need to use 2xsata and at least one would need to be ssd, resulting in lower capacity as ssd is still more expansive when it comes to 2 - 4 TB drives, usb drives cant be used as data volumes in a raid with dsm (at least not without manually tweaking and some risks) maybe look for "normal" mini itx boards and smaller housings being able to have 2 x 2.5" or 2x3.5" hdd's maybe ODROID H2+, ASRock J4125B-ITX, ASRock J4125-ITX, ASRock J5040-ITX ULV CPU based notebooks can go lower but will be more expansive and might lack a 2nd sata or might not even have sata at all in general is xpenology is bound to intel x64 cpu's and that will always have a higher consumption compared with arm based systems like a raspi, if low power is more important then you might be looking for another nas system (omv?) yes but with bigger updates the file you need to tweak will be reset and your raid will break and will have to rebuild, also prone to mishandling like unplugging usb drive, maybe usn as 2nd drive and one sata so at least one drive is safe nothing for linux beginners, wimps, people wanting it easy to handle and not suggested to do if you want to compile your own kernel drivers, dive into the way synology handles this stuff in dsm and want to tweak things in dsm manually and might need to redo it after uddates ... possible yes but as long as a fan control of cpu, board and psu are working by themself there is nor real need and even if the fan run's full speed, its much easier to fix that with hardware seeing the cpu temp is just cosmetics as, you will hear it if you system runs full power because of the fan's and cpu's overheating isn't a thing for over 15 years, they throttle themself when overheating, its pretty much like the package/tweak where you can see the real cpu you used for xpenology (dsm usually has a static display of the cpu that is in the original unit) - might be nice for a few minutes but how often you look at the name of the cpu or cpu temp. the temp feature of the hdd/ssd is a standard value in s.m.a.r.t and does not depend that much on drivers (at least for ahci)

no and no the "NVIDIARuntimeLibrary" pack is more or less the nvidia driver as kernel/base-dsm only comes with kernel drivers (*.ko) the "SurveillanceStation-x86_64-8.2.8-6335_DVA" is pretty much the same as the normal SurveillanceStation without the DVA in the name but has a directory "iva" that makes the difference in size and contains libs for things like object and pedestrian detection the more interesting part of that package could be the ffmpeg version in it, that needs to support nvidia drivers in its binary version along with the driver and the NVIDIARuntimeLibrary package it might be possible to test gpu based decoding/encoding, the normal version in 918+ lacks support for nvidia (i have not checked the ffmpeg in the DSM_DVA3219*.pat, at least the ffmpeg in the special SurveillanceStation DVA package should have nvidia support, might be interesting to throw that stuff together in a 918+ installation and replacing the system version of ffmpeg with the one from SurveillanceStation anyone willing to try that? ???

der gen10 (plus) microserver ist auf den ersteb blick interessant aber zu teuer wenn man es mit den vorherigen modellen wie gen7/gen8 vergleicht (vor allem wenn man iLO mit dabei haben will) außerdem ist durch das bios der weg zur intel gpu verschlossen, sebst wenn die cpu eine gpu hat kommt man nicht dran und muss auf hardware transcoding verzichten und das unnötigerweise nur ein pcie slot vorhanden ist ..., den iLO hätte man besser onboard verbaut und einen 2. pcie slot gelassen in summe kommt da eher ein no go raus hätten die beim schrumpfen für das plus modell 6 disk slots draus gemacht, 2 x pcie und iLO onboard wäre der extrem interessant (and vieleicht 1-2x 10G statt 4x1G ?) dafür würde man eher >500€ einwerfen und die bittere pille mit der gpu schlucken wenn es zeitnah einen loader gibt ist das nicht unbedingt so (nic treiber kann man vermutlich auch aus einem kernel von kernel.org erzeugen wenn es von synology keinen source gibt) aber die inkompatibilität bei den spk's kann für einige ein showstopper sein im grunde haben wir schon recht lange eine pause, der 6.2 loader kom vor >2 jahren raus

no, there are drivers in extra but you would need to define a raid set in the controller dsm would only see a big drive or you define every disk ans a single raid set ad the use these to form a raid set in dsm in both scenarios you cant see anything about the physical disks , no SN or smart values and you will not see if a disks fails, to dangerous if raid mode has to be used i'd suggest esxi and handling disks and stuff there and let use dsm a single virtual disk in the vmfs volume (that is raid protected by the controller) because a driver for raid exists and most of the controllers can be flashed to a IT firmware, some newer (sas93xx/94xx chips?) even have a switch in the firmware to have hba mode so no flashing needed, btw. thats also the case for hp sa p420 ond newer (but i've not heard of a user successfully using the hpsa.ko driver, i now own a p410 so i can at least try in raid mode and maybe we find a user who can test the hba mode) there is only my list of devices supported from a driver, thats no compatibility list, lots of drivers where never tested or we never got feedback someone would need to do a lot of work collecting and reworking these data, that would need a lot of time and constant work as there are new drivers or driver versions and even lots of loaders and dsm versions as stated above the controller in IR mode can be used but its kind of pointless as its dangerous and one looses a lot of comfort, the mdadm raid is one of the plus points as it helps on recovery and can make the array available with different controllers and even nas systems (omv can use the data volumes of dsm) so its more a case for a design guide about hardware to choose edit: i found this link, that indicates that there is no official IT firmware for this controller https://www.reddit.com/r/homelab/comments/6c3jj3/lsi_9286cv8e_it_mode/ edit2: seems to be possible after all https://forums.servethehome.com/index.php?threads/lsi-9270-8i-it-mode.16085/ https://mywiredhouse.net/blog/flashing-lsi-2208-firmware-use-hba/

it is, picture and manual show its realtek and there is only one 2.5G chip, 8125 how will you fit a normal pcie card in a mini slot? you would need a additional adapter like this https://www.amazon.de/Diyeeni-Express-Adapterkarte-Konverter-Karten-default/dp/B07ST256GJ/ there is a 8125 driver in additonal drivers for 6.2.3 if the card is one of the newer hardware revisions it might need a newer driver but at least for 918+ that can be done, for 3615/17 the latest driver from realtek does not compile against the old 3.10.105 kernel maybe a usb 3.0 2.5/5G nic is a option too?

just to make sure, you know your i5-4460 can be used with 918+ and hardware transcoding, just for this you dont need a newer cpu, 4th gen haswell is the minimum and the i5-4460 is 4th gen (the last thin in my post was about that, your 4th gen can do the job and a 5th gen might not be that much better) maybe just make a test install on a single disk, copy e few movies to it and test transcoding (before buying a new cpu you might not need for what you want)

the original dsm kernel files on the loader (the parts that get updated) are 6.2.0 if you installed 6.2.3 u3 you will have these files on the loader no problem if you want to install 6.2.3, as long as you dont want to install a earlier version you could install with this its also no problem to bring the loader to the dsm version you need (as long as its 6.2.x) just replace rd.gz and zImage with the files stored in the dsm *.pat file you want to install (*.pat can be opened with 7zip) 1.04b as it comes has the kernel files the first 6.2 aka 6.2(.0) there is one specialty in the 6.2 line 6.2.0 and 6.2.3 are driver compatible and 6.2.1 and 6.2.2 are, the "driver" means the extra.lzma where additional drivers are stored you could "downgrade" you already 6.2.3 updated usb by just replacing rd.gz and zImage from jun's original *.img file (that can be opened with 7zip to extract the files), but you dont have to because when installing 6.2.3 the newer kernel files will be there anyway after installing

does not look like there is much difference between these cpu's, even when it comes to the gpu its the same (both GT3e) https://en.wikipedia.org/wiki/Intel_Graphics_Technology#Broadwell should be supported with the i915 of 918+ dsm 6.2.3 i listed all the supported gpu pci device id's here https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ click on "iGPU device ID's supported by synology's i915 driver" to open the list the i7 device 0x1622 is in that list and as the xeaon is also GT3e i would expect it to be supported too you might get the same tdp when you underclock the i7, the i7's official tdp-dowm mode @2.2GHz is 37W, the thin you would need to find out is if that lower core clock has influence on the gpu https://ark.intel.com/content/www/us/en/ark/products/88040/intel-core-i7-5775c-processor-6m-cache-up-to-3-70-ghz.html when it comes to features of video decoding the 4th and 5th gen cpu's are not that different https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_encoding

ich bezog das eher auf selbstbau server, im heim bereich setzt ich eher auf günstige leise desktop hardware ohne backplanes und im job wird nicht mehr gebastelt, das sind es eher hpe server mit 5 jahre carepack, gibt da genug andere sachen, da ist keine zeit mehr für schrauben und rumprobieren