IG-88

you might also install the synoboot fix from above as the loader does not match 100% anymore with 6.2.3 (patching on boot) and misses a portion and the fix from flyride does take care of this

most likely you will have a uefi bios and 1.03b needs csm mode to be active and also you will need to boot from the non-uefi usb boot device (might only show up when booting with csm active) the nic (realtek 8111) should work ootb you can try 1.02b if you want (dsm 6.1) this loader works uefi and legacy/csm 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/

you will find the loaders here, here are also 5.2 loaders https://xpenology.com/forum/topic/7848-links-to-loaders/ and there are still lots of older howto if you want to know how to use it (you might think about doing some documentation?) https://www.garydanton.co.uk/2017/03/diy-synology-nas/ https://josephlo.wordpress.com/tag/xpenoboot/

but its not the case, looks like the sas exander is messing around ... [Mon Apr 5 07:55:25 2021] mpt2sas version 20.00.00.00 loaded [Mon Apr 5 07:55:25 2021] scsi1 : Fusion MPT SAS Host [Mon Apr 5 07:55:25 2021] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (16447164 kB) ... [Mon Apr 5 07:55:27 2021] mpt2sas0: host_add: handle(0x0001), sas_addr(0x544a84200187ff00), phys(8) [Mon Apr 5 07:55:27 2021] mpt2sas0: expander_add: handle(0x0009), parent(0x0001), sas_addr(0x500056b37789abff), phys(26) ... [Mon Apr 5 07:55:32 2021] sd 1:0:0:0: [sdo] Spinning up disk... ... [Mon Apr 5 07:55:32 2021] sd 1:0:1:0: [sdc] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB) ... [Mon Apr 5 07:55:32 2021] sd 1:0:2:0: [sdd] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB) ... ... [Mon Apr 5 07:55:33 2021] sd 1:0:8:0: [sdj] 23437770752 512-byte logical blocks: (12.0 TB/10.9 TiB) ... [Mon Apr 5 07:55:33 2021] sd 1:0:9:0: [sdn] Spinning up disk... ... [Mon Apr 5 07:55:33 2021] sd 1:0:10:0: [sdp] Spinning up disk... ... [Mon Apr 5 07:55:33 2021] sd 1:0:11:0: [sdq] Spinning up disk... ... [Mon Apr 5 07:55:34 2021] md: created md0 [Mon Apr 5 07:55:34 2021] md: bind<sdj1> [Mon Apr 5 07:55:34 2021] md: bind<sdi1> [Mon Apr 5 07:55:34 2021] md: bind<sdh1> [Mon Apr 5 07:55:34 2021] md: bind<sdg1> [Mon Apr 5 07:55:34 2021] md: bind<sdf1> [Mon Apr 5 07:55:34 2021] md: bind<sde1> [Mon Apr 5 07:55:34 2021] md: bind<sdd1> [Mon Apr 5 07:55:34 2021] md: bind<sdc1> [Mon Apr 5 07:55:34 2021] md: running: <sdc1><sdd1><sde1><sdf1><sdg1><sdh1><sdi1><sdj1> [Mon Apr 5 07:55:34 2021] md/raid1:md0: active with 8 out of 12 mirrors ... [Mon Apr 5 07:56:05 2021] sd 0:0:0:0: Attached scsi generic sg0 type 0 [Mon Apr 5 07:56:05 2021] sd 1:0:0:0: Attached scsi generic sg1 type 0 [Mon Apr 5 07:56:05 2021] sd 1:0:1:0: Attached scsi generic sg2 type 0 [Mon Apr 5 07:56:05 2021] sd 1:0:2:0: Attached scsi generic sg3 type 0 [Mon Apr 5 07:56:05 2021] sd 1:0:3:0: Attached scsi generic sg4 type 0 [Mon Apr 5 07:56:05 2021] sd 1:0:4:0: Attached scsi generic sg5 type 0 [Mon Apr 5 07:56:05 2021] sd 1:0:5:0: Attached scsi generic sg6 type 0 [Mon Apr 5 07:56:05 2021] sd 1:0:6:0: Attached scsi generic sg7 type 0 [Mon Apr 5 07:56:05 2021] sd 1:0:7:0: Attached scsi generic sg8 type 0 [Mon Apr 5 07:56:05 2021] sd 1:0:8:0: Attached scsi generic sg9 type 0 [Mon Apr 5 07:56:05 2021] sd 1:0:9:0: Attached scsi generic sg10 type 0 [Mon Apr 5 07:56:05 2021] sd 1:0:10:0: Attached scsi generic sg11 type 0 [Mon Apr 5 07:56:05 2021] sd 1:0:11:0: Attached scsi generic sg12 type 0 ... expander makes the drives on it getting a port thats out of the 12 drive range (drive 0 is sdO, then 1-8 sdC to sdJ, 9 gets sdN, 10 and 11 get sdP and SdQ) all 12 drives are found but the gap created by the expander (sdn, sdo, sdp,sdq) will make them out of range for the 12 drive limit also sda and sdb are unused as seen with /dev/md0 (system partition) only sdc-sdj is used rest is above the drive limit of 12 in theory its possible to remap positions but the lsi sas driver is famous for doing funny stuff when drives go missing (disconnected, not working,) as it rearranges the positions (sdY->sdX) seems safer to change the max. disks to 20 (changes to synoinfo.conf that will be lost on bigger updates and needs to be redone) and leave the drives be the way dsm finds them another scenario would be to use RDM for the 12 drives instead of pass through the controller, that way they might be seen as sda to sdl and work ootb without doing anything afaik you would not see smart of temp that way for the drives but esxi would be able to monitor the drives and they would still be the same raw drives as in baremetal

hängt auch davon ab was du da für ein update eingespielt hast bei update auf 6.2 wird er vermutlich immer beim hochfahren merken das es was zu updaten gibt, anfangen beim nächsten reboot wieder auf die nase fallen weil der loader nicht passt, ist ja immer noch der loader 1.02b für dsm 6.1 6.2 braucht einnen neuen loader (1.03b) entweder man setzt mit einem neuen loader das update fort oder man mountet die system partition (raid1 über alle platten) und löscht manuell das vorbereitete update, dann kann man wieder das alte system reparieren bei udpate auf 6.2.3 sollte man wissen das loader 1.03b csm mode bei uefi bios benötigt und man muss vom nicht uefi usb boot device booten (das evtl. erst sichbar wird wenn man einmal mit csm aktiv neu gestartet hat) https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ wenn an an der systempartiton basteln will oder ein backup ziehen will kann man mit einem recue linux booten und die sachen mounten, ist am ende alles nur "mdadm" und "lvm2", ganz normales linux zeug https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/ edit: btw wenn du über metzwerk sehen kannst das es einen zustand X hat (z.b. wiederherstellbar) dann funktionier netzwerk ja offensichtlich, wenn netzwerk nicht ginge würdest null info haben (es sei denn du beutzt den seriellen port als console, da gibs was zusehen)

you can access you files with a normal linux too, the raid is just made from normal linux tools like "mdadm" and "lvm2" https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/ even synology has a KB article about that for helping customers who want to recover data from a broken hardware and its pretty much the same way (using a rescue linux) in most cases its also possible to install open media vault (not to the dsm disks, use additional usb/disk for this) boot that up and find you data volume from the dsm disks ready to use (and having windows network access to the files) both ways if you need access to some files now before you restored your dsm installation - or you want to do a backup (always good to have) if you use a recovery linux to access the dsm disks you can access the dsm system partition too (raid1 over all disks) and if you mount that raid1 and delete all files there then there would be no system to recover and dsm would have to reinstall for sure - but make sure you mount and delete the right thing, kind of a disaster of you delete the wrong ting without having a backup, also if reinstalling read twice whats written there, you dont wand you data deleted as a whole, if it says all data will be lost you should reconsider and stop

thats a big fat NO, updates usually is a "it depends" and for now dsm 6.2.3 update3 is the last version you can install (6.2.4 and 7.0 beta do not work with the current loader and there is no sign for a new loader), accidental update can be a lot more trouble then you can handle (or might willing to handle) if some command line for linux and bios settings are "geeky" then i'd suggest a original unit from synology or qnap, in most cases a 4 drive unit with 2-3 big enough disks should do it (there are 16TB disks available) i'd also suggest just reading the synology faq/knowledge base, they have good information and schematics about things like SHR or raid in general not sure if it has to be synology - qnap has also reliable hardware and nice looking easy to handle gui with plugins/packages if you just want to USE a nas and don't want to learn about linux, hardware and the inner workings of a nas then imho you are batter off using a original unit

the file name only shows its a update to a minor version, if you choose a wrong one (like from 6.2.2 or 6.2.3) it will not match you can check with 7zip, open the *.pat fiel with it and check the "DSM-Security.json" file, there will be the dsm version the update file is made for looks like this: (24922 is 6.2.2, 25426 is 6.2.3) { "builddate": "2020/03/12", "dsmversion": 24922, "smallupdate": [ for updating you would install 6.2.3 (full *.pat file with 200-300MB) https://global.download.synology.com/download/DSM/release/6.2.3/25426/DSM_DS3615xs_25426.pat and then update3 for that version https://global.download.synology.com/download/DSM/criticalupdate/update_pack/25426-3/synology_bromolow_3615xs.pat (6.2.4 is not working with the loader anymore so dont use it)

could you post the /var/log/dmesg? we would see how dsm is seeing and counting the drives, generic to H310 are two sas ports resulting in 2 x 4 sata ports, to be 12 it would need a sas expander (backplane) with Serial ATA Tunneling Protocol (STP) two possible reasons in can think of 1. 3615/17 is max 12 disks, if a sata controller is 1st found and blocks 4 ports then disks above 12 will not show in the gui, so only 8 ports from sas will show up 2. problems with the expander and drivers prevent disks showing up (similar to sata multiplexer not working in dsm, but as its completely different tech that seems not likely)

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/ https://xpenology.com/forum/topic/26723-network-down-after-dsm-login/?do=findComment&comment=137953

das ist die netzwerkkarte und die ID ist im bereits verwendeten treiber in der extra/extra2 0.13.3 drin also wäre die frage https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ davon abgesehen wird auch ohne das hardware transcoding nicht gehen und für deine cpu brauchst du auch noch zusätzlich den modifizierten i915 treiber da der i915 treiber wie er von synology kommt die gpu so nicht erkennt (zu neu, der treiber den die verwenden ist von ende 2017, aber zu glück hat intel an der gpu nicht viel gemacht, die ist intern immer noch gen 9.5 wie beim vorgänger coffee lake)

ok wir bauchen die vollen angaben also "lspci -k" 0000:00:1f.6 Class 0200: Device 8086:xxxx das wäre die netzwerkakrte und die xxxx ist das device auch "Subsystem: Device" wenn vorhanden

that what i'm not so sure about, as its still gpu gen 9.5 in comet lake https://en.wikichip.org/wiki/intel/microarchitectures/comet_lake#Architecture intel has no new DMC (Display Microcontroller) firmware for CML only GUC (Graphics microController) and HUC (HEVC/H.265 microController) and synology only uses DMC firmware with its driver (firmware files in *.pat) https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 the i915 driver itself references to more kbl firmware files then just the DMC file (kbl_dmc_ver1_04.bin) kbl_guc_ver9_39.bin kbl_huc_ver02_00_1810.bin they where not needed for i3-9100 cpu's to have transcoding working so not to expect that it will be the case for the same gen gpu in comet lake

this gpu is different 9bc5 and thats the same as the already confirmed non working from 10900 for the 10100 you can try if it make a difference when you disable vt-d in bios and if the video out is connected to a monitor or not i dont know if newer i915 driver iterations might have a separate firmware for the comet lake's gpu's, if so we could try to load these dmc firmware instead of the old kaby lake we are using now (i'm not sure about the cnl firmware already in the driver and where that one is used) maybe "cnl_dmc_ver1_07.bin" or "icl_dmc_ver1_09.bin" could be used https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 i would need to read a little about the newer gpu's

looks like as if the 1st sata controller you are using for the loader has 32 ports instead of just on i'm not sure about esxi but in virtualbox the number of ports con be configured

that it happens with all 3 versions makes it odd, only one version containing the right device id should do anything the other should just just pass as it has no device 9bc8 in the driver to lock on it does work that way with synology's original i915.ko or you would not be able to boot at all the version you used is from/for U3 (not tested if it makes a difference when using it with plain 6.2.3), check if you have 6.2.3 u3 installed the "older " version are for original 6.2.3 and u2 (as in the description of the downloads)

loaders for 5.x and 6.x are very different and you need the different loader when changing dsm version as every loader is specific to the main dsm version (6.0, 6.1, 6.2) you can do "migrations" between dsm types (like 3615, 3617, ...) but having a fresh install with out any settings with 5.2 does not make sense to upgrade, start over with 6.1, might be easier and if you master this and still willing to try the do a fresh install with 6.2 i's suggest reading the faq and the 6.1 tutorial

no it say's "Connection failed. Check your network settings." there is no "on all HD", please be precise when handling error messages i'd also suggest you switch the dsm wbe gui to english before making screenshots what is odd in you picture is the the underlying windows that say's volume size 1GB take a screenshot of "Overview" and "HDD/SSD" in the storage manager also make clear if its baremetal or vm and what loader and dsm version you use now

wäre in dem fall denkbar (10th gen cpu, also sehr neues board) könne eine neuere revision des i219 sein die vom treiber in meiner extra/extra2.lzma noch nicht dabei ist hast die denn die letzte extra/extra2 probiert? boote mal eine live linux und schau mal mit lspci nach welche device id der netzwerkkontroller hat (vendor id sollte je 8086 sein (device class 0200 für netzwerkkontroller) generell sollte 1.04b 918+ damit gehen wenn die eine pcie netzwerkkarte greifbar hast steck die mal rein und versuche es damit

you can do this, to undo the started update process https://xpenology.com/forum/topic/41473-dsm-624-25554-install-experience/?do=findComment&comment=195970

cpu is ivy bridge, to old for 1.04b 918+ loader 1.03b needs csm mode in uefi bios and the boot device needs to be the non uefi usb boot device hp desktops often need mbr version of the loader to work https://xpenology.com/forum/forum/98-member-tweaked-loaders/ you can also try loader 1.02b for dsm 6.1, that one works uefi and csm/legacy, bur would still need to be mbr version

as long as you cant have your own boot image (loader) in don't see how that will be possible i do remember there where some discussions in the german section about using cloud based virtual servers might have been this one https://xpenology.com/forum/topic/27798-xpenology-auf-einem-root-server-kvm-qemu/

bevor man einen neun usb erzeugt ist es gut zu wissen welche dsm versio man hatte also erst mal sehen ob der usb am pc noch erkannt wird auf der ersten partition die grub.cfg prüfen (am unteren ende sieht man die menü einträge die grub sagen was man vor sich hat (6.0. 6.1,6.2, also die zuordnung welcher loader wenn man einen neuen usb erzeugen will) man kann auch ganz genau bestimmen was man hatte wenn man die rd.gz. der 2. partition auspackt da findet sich unter /etc dann das VERSION file das ganz genau aufschlüsslet welche dsm version man auf disk installiert hat aber normalerweise sollte es reichen die main line mit dem richtigen loader zu treffen und wenn man dann bootet und feststellt das der kernel auf dem usb zu alt ist sollte eigentlich eine reperatut vorgeschalgen werden bei der der kernel von disk wieder auf den usb kopiert wird (setzt aber voraus das der loader grundlegend zur installierten dsm version passt, als z.b. 1.02b für dsm 6.1) wichtig bei einem neuen usb ist sich daran zu erinnern das man ab dsm 6.0 und jun's loader die vid/pid des usb's den man verwendet in die grub.cfg eintragen muss

that sounds like the driver is producing a kernel panic, you would be able to monitor it with iLO and the virtual com port (dsm does all the things on serial console) i only can test with what i have and p410 was the best i got for free lately (and its kind of hard to use on a non HPE system as it needs the bios to support switching off storage bios extension to boot the system at all) we are struggling with the p4xx for a long time and gave up about 2 years ago and i just added the driver from the kernel (that should at least give some basic support and it did with the p410 in raid mode) maybe a newer driver from external source can do the trick, it will be in the next extra.lzma if it passes the test with the p410 in raid mode no if its working it should just recognize the drives without configuring anything (beside the hba mode), if it does not the driver is not working properly

the driver in 0.13.3 supports the following 1000:0064 1000:0065 1000:006E 1000:0070 1000:0072 1000:0074 1000:0076 1000:0077 1000:007E 1000:0080 1000:0081 1000:0082 1000:0083 1000:0084 1000:0085 1000:0086 1000:0087 1000:0090 1000:0091 1000:0094 1000:0095 1000:0096 1000:0097 and here is the list https://pci-ids.ucw.cz/read/PC/1000 your is this one https://pci-ids.ucw.cz/read/PC/1000/00c4 ? the lsi sas drivers in 918+ are problematic as you can see in the 1st post, i would recommend using 3617 as it comes with newer drivers from synology this would be whats supported in 3617 right now (and with smart and serial and without problems about that it might kill your raid if disk hibernation in on) so you 1000:00c3 would be supported in 3617 1000:0064 1000:0065 1000:006E 1000:0070 1000:0072 1000:0074 1000:0076 1000:0077 1000:007E 1000:0080 1000:0081 1000:0082 1000:0083 1000:0084 1000:0085 1000:0086 1000:0087 1000:0090 1000:0091 1000:0094 1000:0095 1000:0096 1000:0097 1000:00AA 1000:00AB 1000:00AC 1000:00AD 1000:00AE 1000:00AF 1000:00C0 1000:00C1 1000:00C2 1000:00C3 1000:00C4 1000:00C5 1000:00C6 1000:00C7 1000:00C8 1000:00C9 1000:00D0 1000:00D1 1000:00D2 1000:02B0 please use the forum search to find the attempts in that direction, its not that easy, its more then just a driver (*.ko file) that would be needed i have this one on my list but there might bo one or two more threads https://xpenology.com/forum/topic/22272-nvidia-runtime-library/ it looked like it was possible to just use the drivers from a "compatible" dsm version but as already stated it gets way more complicated as ffmpeg and other are involved,way more then i'm willing to do as i don't need that, i provided drivers and ways on how to build them, so other people with enough time to spare can push this forward if there is enough will to do it every case where it does not match the installed version (on disk, raid1 over all disks) it a issue usually dsm will not boot and offer a repair that usually copy's the kernel files from disk back to the loader i do mention this i the 1st post (afaik), as i'm only offering the extra/extra2 its up to the user to copy the (6.2.3) files to the loader, before using it how would you want to do that automatically? in theory its possible to offer pre-made (modded) loader with newer kernel files and matching extra/extra2 i'm not doing this for legal reasons, any one is free to offer this, either jun nor me have copyrights on that stuff and as long as there is a decent description with that loader making clear in what way its different from jun's original and giving the version of the extra/extra2 thats used i dont think there is anything to complain about i dont mind if anyone uses the extra/extra2, i would prefer to see a version number, not my name, to be used with it to give people a way to see if its the recent version and being able to read about problems and quirks i've seen my extra/extra2 been used in some stuff from china (like 1019+ loader) and i dont mind that, its free to use for everyone and if anyone tells people its his work then i dont mind too at some point i started to add checksums to the download to make sure people can check if its the version from me or anything modded and i may add some version text file to the extra/extra2 to make it easier to check what version is in use (extra/extra2 can easily be unpacked with 7zip to check a text file) so if you feel the need to offer loaders for pre configured for 6.2.3 feel free to do so and open a thread in the loader section (might need to be approved by a mod so it can be a few days before everyone can see it) btw before doing so PM me, i have a way to overcome the read/write problems in win10 so the offered loader would also be easier to handle as both partitions could be used freely in win10, auto mount drive letters and working without "as administrator" (as in older win10 version)