IG-88

for me it looks like a browser problem, videostation always assumes h.265 cant be decoded and only offers a transcoded h.264 version (high, medium, low) usually i'm not using videostation, i just access the video files with the replay device by nfs or smb i'm pretty sure its between videostation and browser, if h.265 would be browser supported (and VS recognises it) it would just offer the original direct replay, dsm would not have to decode anything just send out the stream as it is, so it has nothing to do with decode, if the replay device could handle h.265 decode then VS (and dsm) would not need to care about h.265 decoding, every system even without intel quick sync support) would be able to do that

gibts min. zwei verschiedene, eins hat intel nic, das andere realtek du solltest loader 1.04b mit erweiterter extra/extra2 versuchen https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ der intel nic könnte theoretisch einen neueren treiber brauchen als der den jun bzw. synology liefern der 10G asus nic wird wohl auch die erweiterten treiber brauchen, evtl. würden auch die von synology geliefrten treiber in 6.2.3 gehen aber da müsstest du diese version erst mal installiert bekommen, für die reine installtion würde ich erst mal bei onboard nic bleiben wenn du mal mit 3615/17 testen willst dann musst du für loader 1.03b im bios csm mode aktivieren, speichern, neu booten und dann nach dem "nicht uefi" usb boot device schauen, wenn du bei aktivem csm vom uefi boot device bootest wird csm nicht benutzt und der boot bleibt hängen (was du aber nur sehen würdest wenn du ein 0-modem kabel und serielle console benutzt, am monitor sieht man keinen unterschied zwischen, syno kernel startet nicht und z.b. netzwerkkarten treiber geht nicht) für den anfang (finden im netz) musst du die grub.cfg nicht anpassen, vid/pid kommt erst ins spiel wenn du ein *.pat file (das dsm system) installierst, nur booten und finde im netz geht ohne modden, nur extra/extra2 auf der 2. partition ersetzen für mehr/neuere treiber sollte zum testen reichen wenn man es im netz findet dann macht man weiter mit grub.cfg anpasen, erst mal ei wenig erfahrung sammeln und rumspielen und wenn man rausgefzunden hat was schief ging versucht man andere versionen bzw. die version die man eigentlich haben will, 918+ klingt zwar gut aber deine cpu hat 8 core / 16 thread, entweder HT (bzw. dessen amd äquivalent) im bios ausschalten oder wenn du die cpu voll nutzen willst dann 3617 installieren (-> 2. link weiter oben) einziger 918+ vorteil bei baremetal wäre nvme cache, aber dafür muss man patchen, barucht für schreibcache zwei davon und es ist risky wenn man nicht regelmäßig backups macht

looks like Version 7.0-41882 is RC now, so might might not be that far to a 7.0 release https://www.synology.com/en-global/releaseNote/DSM beside the usual updated information about fixes and features "... DSM 7.0 for FS, SA, XS/XS+, and DVA series models are currently under development and will be available in the next quarter. ..." so it might be that 7.0 release finally is in q3/2021 also EOL for 6.2 seems to be out, might be 6/2023 https://www.reddit.com/r/synology/comments/npwo72/whats_the_plan_for_future_support_for_dsm_6/

its not clear if apollo lake can handle encoding 4k hevc 10bit, it states decoding only for 8k https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_encoding so it might only decode properly (up to 8k) and encoding might be off limit and needs gemini lake (as used in x20+ syno units) but the problem for not having "original" with hevc might be the browser only safari seems to support that https://caniuse.com/?search=hevc so it might be normal that you need to transcode all hevc to h.264 to see it in videostations webinterface as the browser you use does not support h.265 you can check different types of files with this source https://jell.yfish.us/

you did that yourself (the DDNS)? then you should only have expose one or two ports/services (like photostation) or more? (usually you dont expose everything and with it the admin gui) you would need to check if there are know attacks or vulnerabilities on the thermostat or its infrastructure (home base in you network or cloude base) - unlikely that you would not be the first to hit with a 0-day exploit/attack that seems the most likely source, beside malware, he might have tried a probing or scriptkid's tool (answers from "users" are not always honest or covering every aspect, there can be different reasons for this) you already see your problem here, its called IT forensic, the task of evaluating the damage and finding the reason gets more important with complex environments, it gets more and more challenging when the only plan is to reinstall or buy new things, you need to pin down what was hitting you to evaluate the measures to take, it can bind some resources when assuming the max. capability attacker was at work you just panicked, 1st thing to do would be disconnecting things from network, disabling a potential attackers ability's to remote access and also disabling installed softwares capabilities to spread or doing harm in the network next would have been to access the nas arp cache and dhcp server to check on the IP's mac address, the 1st half of that is the vendor ID, often giving you a clue what device it was, even if its not one of yours (like your neighbor lurking in your wifi unknowingly), a phone, a tablet a pc, that system would be next to check you would also have checked the win10 pc's log and make scan of the system with a system separately booted up (like a different computer booted from a safe media or using a computer that was offline at the time of the events) anyway, not much you can do now after removing most of the evidence you might think about segmenting the internal network with vlan's and even might use internal firewall(s) to limit access from one segment to another (like your son only havong access to the dsm videostations port to access movies instead of exposing the nas to a unsafe user/system lots of home network have grown into small/media company scale networks without people realizing it and not thinking about risks, planing for desasters or doing proper backup - its not a attack problem, its a lack of planning ahead (i guess you did plan for fire or other things by having smoke detectors and having insurance), sadly its pretty normal to get attacked on the internet, ultimate freedom can also mean ultimate evil is possible people tend to forget a nas or even a "simple" mobile phone is a full scale computer that can do anything if used in the right way (and especially mobiles are not getting enough security updates and are highly exposed) you should see this as a warning, nothing serious seemed to be happened right now and even ransomware (with just encrypting files) is no real thread when having backups, there is much more of a problem when your online accounts, cloud resources and bank accounts get involved

not supported as we build on kernel drivers (dsm uses pretty old kernels) and the drivers that come with dsm best (newest) driver would be in 3617 (from synology) and that one does not support Fusion-MPT Tri-Mode chips one gen lower is supported afair last time we tried the drivers from newer avago/broadcom source compiled against synology kernel source crashed, the have modded source of the kernel and i guess also to the newer lsi driver too so its not just slapping in some new driver source when it comes to scsi/sas (as we can see with 918+, there are some parts missing when compiling just new drivers from synology's kernel, like not having s.m.a.r.t. support) if using not supported hardware its still possible to use virtualization (as flyride pointed out) with dsm 6.2 "aging" it gets more important to choose the right hardware,its not a normal linux distribution with recent kernel (and hardware support), its kernel 3.10.105 (3615/17) and 4.4.59 (918+) also possible is to use "similar" free nas distributions like open media vault (my fall back if things go south with dsm), the gui might not be as flashy as dsm's but it offers much better hardware support and with its docker support a lot of things can be done

hp stellt schon eine ewigkeit pc's her und i5 gibt es seit ~13 jahren, immer noch ungenügend ein wenig mehr einsatz deinersets braucht es schon, wenn du es nicht mal schaffst das typenschild des pc's abzulesen oder mal im bios nach dem genauen typ der cpu zu schauen ... ok, ich bin raus, vieleicht findest du ja jemand anderen der mehr zeit und geduld hat (ich empfehle damit zu beginnen meine vorherige antwort zu lesen, dem link zu folgen und den loader 1.02b zu versuchen) https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/

https://xpenology.com/forum/topic/30552-transcoding-and-face-recognitionpeople-and-subjects-issue-fix-in-once/ erst sollte man mal nachsehen ob man etwas in /dev/dri hat, wenn es das nicht gibt stimmt schon was mit hardware und treibern nicht und ohen das wird das mit dem transcoding nicht gehen, selbst wenn man alles richtig freigeschaltet hat

mehr gibt auf dem monitor nicht, ab dem punkt läuft alles auf die serial console, die du nur mit einem comport und einem programm wie putty (mit nullmodem kabel) sehen kannst, da wäre dann mehr zu sehen u.a. welche treiber laden oder ob der kernel abstürzt ansonsten sind deine angaben zum loader, zur hardware usw. etwas dünn, schwer da ohne glaskugel etwas zu sagen aber es gibt bei der nutzbaren hardware (für 1.04b/918+) und den bios einstellungen (uefi mit csm und das nicht uefi boot device bei 3615/17) https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ generell ist loader 1.02b für 3615 und dsm 6.1 ganz gut zum üben, wenn man das im griff hat kann man es nochmal mit dsm 6.2 versuchen (unter beachtung der dann zusätzlich zu beachtenden sachen -> link weiter oben)

there is no other pci id of that class (0200 = network) shown in your list, no pci id, no hardware present, no driver loaded the intel X520-DA2 SFP+ would be ixgbe.ko and its possible that the one in jun's original extra/extra2 is to old, so you might try my extended version that also has newer drivers you can look for supported hardware in this list its still valid for 6.2.3 https://xpenology.com/forum/topic/12859-driver-extension-jun-103a2dsm62x-for-ds918/ be2net.ko for emulex will be the same as jun's (from kernel 4.4.x) i did not find a pci vendor and device id for oce11102, so i can't check if its sopported by the driver we have (you can check yourself, look for vermagic in the driver and you will find the list of id's, modinfo would be the propper tool but afaik its not part of dsm) also keep in mind the 918+ has a max default of 2 nic's so even whern divers are loader for nic 3 and above there will be nothing in the gui, you would need to check the dmesg to see if they are there, you can extend synoinfo.conf to support more https://xpenology.com/forum/topic/21663-driver-extension-jun-103b104b-for-dsm622-for-3615xs-3617xs-918/ look for "!!! still network limit in 1.04b loader for 918+ !!!"

thats the way it should work, its just serial console output comming the parameters are shown in the grub.cfg of the loader console=ttyS0,115200n8

synology removed that ~2013 from dsm in a way that only there own units work (like checking the firmware of the external unit) its not about missing drivers, its a feature to prevent unsave hardware, you also can't make usb or esata drive part of a raid for the same reason the most technical i cant remeber about it was this https://community.synology.com/enu/forum/17/post/54396 and even if you find out about it, it most likely sits in the kernel and the way the loader works we are bound to use the original synology kernel way easier to use 4lane sas connectors ans sas controller to connect to a enclosure (rarely seen) if you really want to use that then try open media vault, its a normal linux and not a hacked appliance like xpenology

the usb boot dom of the original synology is still working and needed and i'm pretty sure extrnal usb disks will still work the loader is there same in the same way as the original one, it gets the same usb vendor and device id (f400:f400) and even updates work the same way i dont think these are related, they started pulling back much earlier (like not supporting wifi usb) synology just want to ged rid of the small clatter and there is to much problems using older kernels and having support for newer usb devices they want to be in the SMB market and consumer is more of a less important thing i guess i would predict the nas consumer part will be sold at some point or be transferred to a new spin off company

that does not look like the system got stuck an boot (12:08), that indicates it started , so the content from ~12:0x to 12:08 would be the interesting part to see what happened when the qlogic driver was supposed to load/start the thing here you can use at boot is the serial console if the system has a serial port or a virtual serial port (like HPE iLO does), you would see the drivers loading or fail and see if a kernel panic happens , i case of a real serial port it needs a null-modem cable

not many people test that afaik bur 26 did work here https://xpenology.com/forum/topic/8057-physical-drive-limits-of-an-emulated-synology-machine/?do=findComment&comment=78160 no any extranel (usb or sata) can't be made into a raid in DSM imho the limit is not hard at just single digit sdX, i've had working config with a asm1166 where the controller "blocked" 32 ports and the disks after that got sdXX and where part of a max 16 disk array (918+ has 16 as default), as long as real number kept below the max 16 it worked even with two digit sdXX numbers imho the way beyond 24/26 is to follow quicknicks lead (see link to the thread above)

you could check the /var/log/dmesg for errors when you can access the system after the failed attempt with the hpe nic

if using esxi and vmxnet in the vm you can use any IEEE 802.3bz, NBASE-T nic as long as it has a vmwae driver the vmxnet does support up to 10G and dsm's extra.lzma (jun's default and other) has a driver

there is only a driver in 5.x kernel (that dsm does not use, its 3.10 and 4.4) and intel has no intentions to release a independent driver for older kernels (its name would be "igc") it would need a specifically backported driver and i can't do that as i'm not a coder go with a realtek 2.5G nic or any 2.5/5/10G capable nic's (IEEE 802.3bz, NBASE-T, MGBASE-T) the 2.5G realtek is the cheapest to have better network speed

you would not have to when using this method, you do a fresh install and loose all settings of the old one, you could downgrade to any dsm version as long as you have a loader for it, the only part you are reusing is the data partition(s) you created after installing dsm you do boot from the usb you newly created and the new disk and with it you have a new raid1 set, you dont migrate anything (you loose all settings like users, shares, ...) because you just fill up your new raid1 with the system and swap partitions of your old drives (raid repair of the new raid1 from the new disk) and deleting the content of the 1st two partitions (system and swap) of your old disks on the way depending of the complexity of your installation it might be worth the effort to try another way and keep the settings or have a backup of the system and packages for the dsm version you use (like with hyperbackup from synology), then you can (fresh) install the dsm version you had before and restore the system state after the default system is back and running that can be helpful but when using a new usb to boot from, you will still need to mod the grub.cfg for the new vid/pid of the usb flash drive (and might still need some documentation to remind you of that) when using different hardware for recovery there can be added things, like when using 918+ that needs a 4th gen intel (haswell) as minimum and then using the loader at hand (1.04b) with a older hardware you might have around will not work if the cpu is to old a documentation is suggested in parallel as it's often not that simple as it looks in some youtube videos

check usb vid/pid of the usb flash drive and compare with the one in grub.cfg, that would be the usual with that error

usb wird nur as externes medium ootb unterstützt und viel performance würde ich bei usb für disks auch nicht erwarten das ding hat immerhin 2 sata anschlüsse so das du deine 2 disks theoretisch anschließen kannst die gpu ist aber nicht als unterstützung nutzbar, außerdem kannst du nicht einfach von ssd booten, so funktioniert dsm nicht lies mal die faq und im tutorial bereich https://xpenology.com/forum/forum/83-faq-start-here/ 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/ gen8/9 coffee lake hardware ist für xpenology am besten geeignet wenn man hardware transcoding über die gpu nutzen will https://xpenology.com/forum/topic/24864-transcoding-without-a-valid-serial-number/ mehr infos zu gpu support mit bis zu gen10 (teilweise) findest du hier https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ wenn du was "kleines" billiges willst schau mal nach gemini lake basierten mini-itx sachen

nein, für diesen nic gibts keine compilierbaren treiber für kernel 3.10 oder 4.4, ist nur bestandteil von kernel 5.x der aber von synology nicht benutzt wird intel developer haben letztes jahr auch schon gestreut das es keine pläne gibt einen extra treiber für ältere kernel bereitzustellen der prozessor ist an sich kein problem aber die gpu ist die neue Xe architektur, keine treiber, nicht mit 918+ nutzbar und um die 16 threads zu nutzen müstest du 3617 benutzen, da gibts ohnehin kein gpu (hardware transcoding) support und nvme gibts da auch nicht für 918+ ist 8 threads max im kernel und wenn du nicht 4 echte und 8 HT cores nutzen willst müsstest du HT abschalten und hast dann "nur" die echten 8 cores, aber dann ginge immerhin nvme (das aber nur als cache nutzbar ist) um diese hardware voll zu nutzen müsstest du eher open media vault nehmen, das nutzt zumindest kernel 5.x, aber ob da auch Xe GPU suport bei ist weiß ich nicht, zumindest würden cpu und nic voll nutzbar sein, die nas basics gehen damit alle und durch docker kann man auch viel von dem haben was mit dsm geht

maybe this does it? https://www.brainattic.org/download/hpe-spp/

I've read it twice but can't see where he made anything different then usual, the hardware is from 2011 (nehalem) and has uefi bios, doesn't make it special in any way any chance to get more information or a dmesg log from that system?

maybe your topic isn't right, from my point of view blaming drivers is not the best starting point as lack of documentation, reading or experience is more often the case, so phrasing more cautiously is advisable, pointing a finger into the direction of coders or maintainers without even a shred of proof ... not a good starting point in theory the driver for jmicron would be jme.ko and thats even available in jun's default driver set (i had to look, can't remember ever seen such nic irl, kind of exotic) so it seems not likely that it is a driver problem because the loader comes with a matching driver (1.02/1.03/1.04) you already ruled out cable problems as win10 works over network (i guess the system was rj-45 connected when testing) cpu is a Cedarview from 3/2011, to old for 1.04b 918+, definitely not a problem with the nic with this loader as the kernel does not start to even load a driver thats not going to work as the loader uses dhcp and most people dont run a dhcp server on there laptops (should work directly connected with this one https://xpenology.com/forum/topic/12422-xpenology-tool-for-windows-x64/) as the bios seems not to be uefi (1.03b is not working in uefi mode) and 1.02b seems not to wok too (can do old bios and uefi) i'd suggest trying the mbr version of the loader https://xpenology.com/forum/forum/98-member-tweaked-loaders/ for just testing if its found in network you can just use the loader as it comes (vid/pid in grub.cfg is only needed when really installing dsm to disk) - makes things faster when testing with different loaders i'd suggest loader 1.03b (mbr) as 1st try (doesn't matter if its 3615 or 3617)