IG-88

there was a old list when we tried to find out what was working with 918+ we know it needs 4th gen intel to boot for the lowers possible specs you can look here https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ when it comes to new cpus there is just a core limit ( see link above) and as long as you dont want to use hardware transcoding even the latest intel and ryzen are ok for hardware transcoding (intel quick sync video) there is some kind of list in my driver for 6.2.3 thread https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ up to 10th gen lower tier cpu it can be made working 10600K and above seemed not to work

the 918+ loader makes sure its 16 disks check the disks you confugured and count the availible sapce properly every disks hold 2.4GB as system partiton plus 2GB as swap both raid1 over all disks so if you configured 5GB then 4.4GB are already taken by "initializing" the disk for use (dsm system is a raid1 over all disks, usb is just the kernel to start loading from disk) maybe try thin disks and make them bigger (as long as you dont copy data to the new raid volume the thin disks will only take very little real disk space)

you cant know for sure without a serial console - and i know for sure that the realtek r8168 driver is working especially if 6.1 is working it seems likely to be a uefi csm problem manual says its uefi so look for l http://content.etilize.com/User-Manual/1016571086.pdf page 102 "Set the legacy boot order" best is to use F9 to select the boot device manually and it needs to be the usb from the legacy section

mal zu erinnerung https://xpenology.com/forum/announcement/2-dsm-serial-number-must-read/ "... Posts or topics discussing how to abuse Synology's servers by the use of Quickconnect for example will be locked or deleted without prior notice. Posts or topics discussing how to crack Surveillance Station and/or providing links to patched/cracked SS will be deleted without prior notice." https://xpenology.com/forum/topic/9392-general-faq/?do=findComment&comment=82390

du meinst reparieren aka raid wiederherstellen? von hand müsstest du da nichts machen nur die wiederherstellung des SHR anstoßen ist evtl. nicht notwendig, wirst du ja sehen wenn die wiederherstellung durch ist

wenn eine mit der vm läuft kannst du die 2 löschen (partitionen entfernen), sie reinhängen (auf den boot kann sie ja keinen einfluss mehr haben) und dann das volume reparieren, dann sollte system/swap und auch die volume partition drauf kommen ich bin mir im moment nicht im klaren was dein endziel ist also am ende nur die 2 disks der 216j in der vm und keine virtulelle platte mehr wenn der restore der 2. 216j platte fertig ist und sich die system partition der 1. platte nicht reparieren lässt wäre auch möglich diese partitionen (1. und 2. aka system und swap) zu löschen und dann noch mal reparieren zu versuchen, imho müsste er die partitionen neu anlegen

was eigentlich bedeutet die platten der 216j werden früher gefunden bzw. liegen vor der ursprünglichen boot platte also rein theoretisch könntest die partitionen auch entleeren, also die 216j platten mit einem rescue linux booten, das raid1 der ersten partition zusammenfügen und dann formatieren wenn nichts drin ist kann auch nichts (altes) gefunden werden wenn es ein shr mit 2 platten ist dann stimmt das soweit, es fehlt ja eine platte aber du könntest deine daten so zumindest umkopieren wie sieht es denn bei speicherpool und volume aus?

1.03b for 3615/17 are the only one for 6.2 you can use and they need CSM/legacy mode if its uefi bios (and also you need to boot from the non uefi usb boot device) https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ when in legacy mode you might need the loader in mbr (default is gpt), so if the above does not work you can try the loader from here https://xpenology.com/forum/topic/20270-dsm-62-loader-with-mbr-partition-table/

check mal die größe der partitionen auf der 216j platte, ich meine mich zu erinnern das system and swap da kleiner sind so das man nicht einfach x86_64 drauf installieren kann normal sind 2.4 + 2.0 GB aber wenn 918+ lief und man 2 andere dazu gibt (folgende sata ports oder 2. sata controller) hätte ich ja erwartet das die system vom 918+ hoch läuft versuch mal ohne die 216j platten zu booten (918+) und hänge die zwei 216j platten rein während 918+ läuft

just suggestions based on spec and from the page a found about tweaking the t620 for one you could have 500mA from the internal usb connector and if you take a closer look at the pictures from the link above the power of the disk in the picure and near thr usb port and in another picture with the systemboard you can see that its the unsoldered connector right beside the usb right beside this there is something that looks like a fan connector, that might be a option too (the pictures are not highres so i cant read what written on the board, but you can and you can take some mesurements where is ground and 5V

no, if the voltage or current is not stable the system can crash at any time depending on temp. and current drawn https://en.wikipedia.org/wiki/Capacitor_plague https://www.memtest.org/ https://www.amd.com/en/support/kb/faq/gpu-104 psu is not so easy to test as things depend on how much power is drawn easiest usually is to use a psu from another computer to check if the problem is still there with a different psu just use a search engine, this are basic things and there are ton's of information

to use usb for baremetal is not supported and if you mangle the config files in a way doing it you will loose that on bigger updates giving serious headaches and loss of convenience you can have two sata drives, one in the m.2 and 2nd in mSATA slot (or soldered manually if its missing) https://www.parkytowers.me.uk/thin/hp/t620/ https://www.parkytowers.me.uk/thin/hp/t620/mods.shtml if msata is present and you want o use a normal sata connector for a 2.5" hdd/ssd https://www.startech.com/en-us/hdd/msat2sat3 https://www.sybausa.com/index.php?route=product/product&path=64_181_184&product_id=888 the sata part of the m.2 slot can be used with this https://www.sybausa.com/index.php?route=product/product&path=64_181_184&product_id=889 there are also minipcie sata controllers to replace the wifi card https://www.sybausa.com/index.php?route=product/category&path=64_181_183 and m.2 pcie controllers https://www.sybausa.com/index.php?route=product/product&path=64_181_184&product_id=1070 https://www.sybausa.com/index.php?route=product/product&path=64_181_184&product_id=1044 https://www.sybausa.com/index.php?route=product/product&path=64_181_184&product_id=969 ps: and as you seem new to xpenology, sata multiplexer are not supported so using a enclosure with that tech also does not work

as nuc's usually only have 1 sata and no room for 2x 2.5" hdd/ssd its not a good platform m.2 ssd can only be used as cache (one just read, two r/w) and with a 1GBit nic and its limit to 112MB/s its kind of pointless to sink money into that as the nic will be the bottleneck most of the time maybe a barebone with 2x2.5"? https://www.shuttle.eu/en/products/slim/xh310r/ https://www.shuttle.eu/en/products/slim/xh310rv/

spielt keine große rolle, 1.04b 918+ geht uefi (3615/17 braucht csm, das bereitet manchen probleme) und alle gängingen onboard nic's werden unterstützt die upates für 6.2.3 kannst du alle installieren, da bleibt im moment nichts zu anzeigen übrig

from my experience thats not typical, its most often capacitors (swelling or already blown, inspect the board) or RAM problems (use memtest from a bootable linux media), psu problem might be up next in line with dsm's lack of a normal console over video out its hard to tell if its a network problem or the system is frozen/crashed it would be possible with serial console (null-modem-cable) to check if a local login is still possible

das sind nur updates die werden automatisch nachgezogen, du musst die volle version installieren https://archive.synology.com/download/Os/DSM/6.2.3-25426 bei cpu für 918+ ist 4th gen (haswell) das minimum https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/

you would need to look into log files in /var/log/ like messages or other files with a recent file date

you can rename the img files as you like, the vmdk is just a text file so its easy to change namens

loader 1.04b 918+ dsm 6.2.3 ??? falls du transcoding meinst (da wird aber nicht ffmpeg gepatcht) https://xpenology.com/forum/topic/24864-transcoding-without-a-valid-serial-number/ https://xpenology.com/forum/topic/30552-transcoding-and-face-recognitionpeople-and-subjects-issue-fix-in-once/

habe vergessen den link zum pdf hinzuzufügen https://global.download.synology.com/download/Document/Software/DeveloperGuide/Firmware/DSM/7.0/enu/DSM_Developer_Guide_7_0_Beta.pdf

das letzte an das ich mich erinnere ist das https://xpenology.com/forum/topic/37322-dsm-7/?tab=comments#comment-183691 aller notwendiger code müsste im git sein und die doku im developer 7.0 pdf so lange ich keinen bedarf habe werde ich da keine zeit versenken, gibt genug anderes zu tun, aber wenn du ein wenig lesen willst ...

dsm 7 benutzt neue kernel versionen so das der preboot kernel der alten loader nicht mehr passt und die treiber würden auch nicht mehr passen, also nein kein loader bis jetzt und keine ankündigung oder test version ich würde vor einem release der 7.0 auch nichts erwarten, wenn synology schon vorher einen neuen loader in fie finger bekommt könnten sie noch vor dem release gegenmaßnahmen ergreifen, sowas wird nach einen release ohne beta phase unter umständen zu aufwendig/gefährlich

jun delivered a vmdk file with 1.02a that is a wrapper to to img file, you can use the vmdk file for virtual box that way you leave the img file the way it is and can easily mod or replace it i still use vmdk this for loader 1.03b/1.04b with virtual box

no its no good, JMB575 is a 1 to 5 multiplexer 88se9215 has 4ports and one port will we multiplexed to 5 so its 3+5=8 but with dsm and no multiplexer the max, you would be able to use is 4 ports (one of the 5 "added" will be usable) that depends on the pcie slot (1x or 4x+) and the number of ports you need, if a 4 ports card is not enough and jmb585 is no option then there are pcie 2x cards with 8 usable ports https://xpenology.com/forum/topic/19854-sata-controllers-not-recognized/?tab=comments#comment-122709 bit are limited to 1000MB/s because of pcie 2.0 and 2 lanes, in theory a lsis sas controller is possible too (also 8 sata ports) but there are problems with 918+ maybe two 4port marvell based controller in 2 slots (4x slot or wieder)? when its 88se9230/9235 the its 2 pcie 2.0 lanes for 4 ports and with 250MB/s per disk that would be ok as long as its not ssd when its 88se9215 based then its 4ports with one 2.0 lane (500MB/s) when using 88se92xx based controllers it depends on you disks (hdd vs ssd) the limit to pcie 2.0 is a problem when it comes to ssd's

i did try to outline the "how" above, analyze how its done in qucknicks loader and we will try to replicate that in jun's loader (he never released it, a beta tester released it and he withdrew, so there is no extensive documentation or help and that the release was without his consent is also the reason i do not support anyone using it - even its a really good peace of work and would have deserved more attention)