IG-88

das video ist über dsm 5.2 da war das eine oder andere noch anders, ich rede vom aktullen dsm 6.2 wenn du unbedingt willst versuchs erst mal mit einer frischen mini installtion und wenn du das hinbekommst und ausreichend performace hast dann kannst du über eine migration deiner installtion nachdenken (soweit ich mich erinnere scheitert es u.a. am netzwerk, der vNIC geht nicht und legacy war nur ein steinalter 100MBit adapter) such doch mal hier nach hyper-v, da gibts das den einen oder anderen der das versucht hat https://xpenology.com/forum/topic/7973-tutorial-installmigrate-dsm-52-to-61x-juns-loader/?do=findComment&comment=119947

that would be e1000e.ko and that driver is recent, version 3.6.0 as you can see here, its the latest version https://sourceforge.net/projects/e1000/files/e1000e stable/ but there are more options to consider maybe read what i wrote one post above your's about boot problems

that was my point it would even slow down normal/old fashioned disks (under best condition you might reach 200-250MB/s with a 4TB disk) and you should not dare to add ssd for caching (this could be connected to the onboard sata, that usually have full speed) if you only use 1GBit network you won't but if you use 10G nic and push 20-50GB video files you will the blockage of multiplexers in dsm was introduced around 2014/2015 from synology (afair) so the one complaining it does not work anymore might have installed the update that introduced it in original synology systems it only affected people using external (non synology) boxes the used multiplexing to connect more disks that the one i bought myself and was in the thread you linked above (with the 2 different 8port ahci controllers and the explanation of why/how to choose) the description (marvel 9215) and board layout match, 4 x 9215 and one (bigger) pcie bridge price point does match too, price scales as its more exotic and has lower production numbers if you only have one pcie slot to spare and a 8port controller is to small it might be a option, you might find a 16 port lsi sas controller for 200-250 too and that one will have betterperformance for sure (if it matters)

die daten sind zum allergrößten teil noch da, die frage ist wie vile verlust man in kauf nehmen kann/will jede raid platte hat einen sequenz counter, im normalzustand sind die alle gleich, werden daten nicht auf die platte geschrieben weicht der ab und die platten fallen aus dem raid man kann sie mit den richtigen befehlen wieder in das raid "zwingen" aber es gehen dann eben diese nicht geschriebenen daten verloren bzw. haben falschen inhalt, was dann zu logischen fehlern in (wenigen) dateien führt, das sind evtl .nur ein paar hundert kB erst mal wichtig ist die ursache zu ermitteln, an einem instabilen system sowas reparieren zu wollen geht meist schief dann ermittelt man den sollzustand, layout der platten im mdadm raid, SHR bedeutet meist unteschiedliche platten waren in nutzung, was dann in mehreren raid sets endet die mit LVM zusammengefügt sind - SHR ist nicht so "speziell" es "nur" eine kombination auf linux standard sachen wie mdadm und lvm nach dem dokumentieren ermittelt man die sequenz nummer und schiebt grade so viele platten wieder zurück in das raid wie nötig unf nimmt die platten mit der höchsten sequenz nummer, in deinem fall würde man von den 2 "freien" platten die sequenznummer ermitteln und nur eine mit der höchsten nummer wieder zum raid hinzufügen, da die chunk size meist 64k ist kann man am unterschied der plattten die noch synchron sind und der "besten" die man noch hat den verlust ermittlen, wenn man btrfs mit checksummen hat kann man evtl. sogar rausfinden welche dateien betroffen sind lies mal hier rein und in den verlinkten englischen thread, da gab es noch bestehende hardware probleme was die reparatur (unter datenverlust) am ende doch verhindert hat ist eigentlich nicht so schwer, flyride hat das in dem englischen thread sehr gut parallel zur reparatur erklärt, kann man fast als tutorial nehmen (setzt aber ein paar kenntnisse über linux und raid/lvm voraus) https://xpenology.com/forum/topic/24767-asrock-j4105-itx-sata-controller-defekt/

if that refers to a asrock board, there are others with it and it does work for them had one tester with this board, he was able to boot and install dsm 6.2.2 but had stability problems, but as he also had this problems with jun's original loader and dsm 6.2.0 so it must have been something else that produced stability problems in general "not booting" in most cases is not the correct term, that would be the case if you dont see jun's message or no menu (3 options from grub boot manager) and that would have nothing to do with the drivers, maybe "it does not finish booting" comes near please describe your steps, and that means not cut and paste my description, describe what you really have done, when unsure redo the steps you about to write down, in some cases people might see by themselves that they missed a step just by writing it down and rereading the guide don't make assumptions when there are no data, the only thing you can usually say, if you see jun's message and don't have a serial console connected, is that you can't find it in network after booting, that can have a lot of reasons, starting with a loose or "wrong" network cable (uups wrong switch), general network config problems (vlan's, more then one dhcp server, ...) to crashing driver on loading kernel that halt's the system

nein, xpenology verwendet den orginal kernel von synology und der unterstützt kein hyper-v, kann man auch nicht wie treiber "nachladen" im gegensatz zu vmware anderen gibts bei hyper-v keine vernünftigen alternativen emulations treiber wie e1000e oder sata/ahci, lsi scsi/sas controller entweder der kernel kann es (unser kann es nicht) oder man ist ... wenn du das wie oben beschrieben machen willst wäre evtl. ESXi eine option, da laufen dann windows 2019 und xpenology je als vm

in general i'd say 2 x pcie for 10 ports just from the numbers not good for SSD (maybe not even for normal disks) same controller as https://www.amazon.com/Ableconn-PEX10-SAT-Port-Express-Adapter/dp/B0177GBY0Y/ https://www.kuroutoshikou.com/product/interface/ata_sata/sata3i10-pcie/ -> Chipset: ASMedia ASM1062 + 2x JMicron JMB575 ASM1062 is a pcie bridge https://www.asmedia.com.tw/eng/e_show_products.php?cate_index=166&item=151 JMB575 is the sata/ahci controller https://www.jmicron.com/file/download/893/JMB575.pdf "... With proper setting, the chip can be configured as 1 to 5- ports Serial ATA III Port Multiplier ..." -> i'd expect you would only see 2 sata ports with DSM, one port from every JM575 chip not a good option as it seems unlikely to be usable with 10 ports as i stated in the other thread(s) always look for the chips and specs, if it does not make sense don't expect it to be usable

your Xeon D-1521 CPU does not support intel quicksync video so no hardware transcoding when using 918+ if you plan to make use of the M.2 nvme slot then 918+ is your choice, all other aspect are not important and you could always "migrate" be swapping loader and installing the other type 918+ uses a newer kernel 4.4.59 (instead of 3.10.105 for 3615/17) but atm that does not make i difference when it comes to additional drivers the only case that comes to mind is the 918+ not booting with older cpu's

HPE uses smart array raid controllers, thats not AHCI it might work if you confugure the controller for IT mode (hpsa 410 and newer might support this - never tried this as i dont have this hardware) or maybe for testing you can configure one or more drives as hpe raid set, this raid sets might show up when the (hpsa.ko) driver is working (try this before putting to much work into findung out if IT mode work) - my advice is to forget about the HPE SA controllers, use a AHCI 4 or 8 port controller or a lsi mpt fusion SAS 2.0 controller in IT mode (8 sata ports with the propper cable)

6 ports are usually 4 port controllers using sata multiplexer for the 2 added ports, dsm can't use multiplexer (that are not from synology) in this case you will find only the real sata ports, so 4 is to expect in your case

reinstall the package, overwrite the files (old file date) with the new as you did before, reboot try the shutdown by button, check the log (dmesg) for errors during boot (drivers loading) and the (attempted) shutdown you can also look for whats in /dev/input/ and /sys/class/input/ there should be something if the drivers are loaded properly

your cpu should be able to boot with it and it supports bios and uefi so bios should be not be the problem can you disable the onboard 10G lan and add a different nic for testing? no step by step, 1st find out the reason why its not visible in network, your braswell cpu is kind of exotic and untested for the 0.8 driver pack, recovery is the safe choice when trying out things, i915 driver problems will be no reason that way, you need to reduce possible problems to find out whats wrong (at least when not having serial connection to monitor the boot process)

no, not with 0.8_recovery and with 3615/17 its no problem at all you can try 0.8_std if you want, if its not working you can just copy the files from recovery to usb and try again no, you need to have real serial port, the usb2serial is for the computer with the terminal in case that one has no com port or you want a more flexible handling like connecting to a fron usb port you supermicro x10sdv-4c-tln2f does have a com port, you just need a matching cable and a bracket, can be found an amazon or ebay https://www.amazon.com/StarTech-com-1U-Rackmount-LCD-Console/dp/B001Y1F0HW/

did you install the "POWERBUTTON_6.2-0002.SPK" does shutdown from the web gui work properly?

the 0.5 extra does did you also copy the new zImage and rd.gz? beside activating CSM legacy mode in bios and a reboot did you also choose the right boot device, the usb might show up 2x as uefi and 1x as legacy maybe try loader 1.04b 918+ with 0.8_recovery extra/extra2 that loader supports legacy and uefi

update or fresh install? what "does not work"? does not boot, no /dev/dri, ... you should at least be able to boot with recovery and after being able to log into your system by ssh you can delete the the i915 firmware and drivers in "update" folder as in the description, shut down, copy the extra/extra2 "syno" type to the usb and boot again

uploaded and changed the link

you should use recovery for your N3050 CPU i'm sure wrote about that in the explanations about the tree 0.8 variety's for 918+ (as i had a case where a tester with a N3xxx was unable to boot and only the trick with the 0byte long files got the system back booting - thats the reason its named "recovery") thats explained in the FAQ, maybe (re-)read the faq https://xpenology.com/forum/topic/9392-general-faq/?do=findComment&comment=82390

what driver would that be? where did you get it for 6.1? what exactly did you install? whats the source of the packages? you need to provide proper information, maybe a log (of 6.1) where drivers are loaded

sound like as if there is a mismatch between kernel and modules/drivers loaded maybe mismatch in extra/extra2.lzma? your log snippet does not say anything about what loader or dsm version you used redo the step about copying the right extra/extra2 (in case of 3615/17 just extra.lzma) from the rigt zip file, check the version of the loader not by guessing, look at the screen when booting, them menu (3 options) from grub.cfg tells you what dsm loader you use (3615/3617/918+), use the zip files i uploaded, the are named properly (drivers will be copied automatically from usb to disk if there is a difference, what comes from usb win's)

you usually dont have to but if you want to ... its the number of ports of every controller in the system in a row, one after another, so 62 in your case

not sure what feature you need that for, can't be hardware transcoding as it will not work with the recovery variety that would be the alternative https://xpenology.com/forum/topic/24864-transcoding-without-a-valid-serial-number/ no

are you sure you can do legacy BIOS with this asus nas? that might explain why you cant get 3615/17 loader 1.03b to work -> https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ maybe try loader 1.04b (supports uefi) for 918+ and try the 0.8 recovery extra/extra2 (+ zImage, rd.gz from 918+ 24922 *.pat file)

you dont say what loader you used, 1.04b for 918+ will not work for you hardware if its loader 1.03b (dor DSM 6.2.x) then it has to be legacy BIOS and you need to select the legacy usb device, if CSM is aktive you often see 3 usb devices, two for uefi and one for legacy iven if, you should at least see the system after booting from usb (no dsm installed on disks), the vid/pid will be important when installing the *.pat file (the error for this is documented in the tutorial) i cant see any reason why it should be a problem for a 3615/17 installation

then you should be able to check /var/log/dmesg about what happens when the realtek r8168 driver is loaded