IG-88

maybe one last try? user-config-json.txt ... "SataPortMap": "6", "DiskIdxMap": "00", "sata_remap": "10\\>2:11\\>3" }, in theory it should map the two ports ata11/ata12 into the 1st dummy gap (ata3/ata4), close the gap and leave only 6 ports usable

thats normal and to expect, 6.2.3 u3 is the last that works with jun's loader 1.03b there is no data loss from that, you just can't boot the operating system aka DSM anymore, your data are on a separate partition you can undo the unfinished 6.2.4 update or mount the raid with another linux to do a backup (better late then never, and as often to read, raid is no replacement for backup) https://xpenology.com/forum/topic/42765-how-to-undo-a-unfinished-update-623-to-624-no-boot-after-1st-step-of-update/ https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/ it would also be possible to use a newer loader to update to 7.x but that would need some extra learning as its different from jun's old loader https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ its even possible to boot open media vault and access your data over network for backup (or stay with omv if you want) https://xpenology.com/forum/topic/42793-hp-gen8-dsm-623-25426-update-3-failed/?do=findComment&comment=200475

"older" hardware, sandy bridge, not working with 918+ or other types that need haswell https://xpenology.com/forum/topic/13333-tutorialreference-6x-loaders-and-platforms/ https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/ and there is also the hassle with 6.2 that you would need to boot in BIOS/CSM mode and depending on bios you need to select the right usb boot device (there can be more then one, the one with uefi in its name is usually the wrong one and would result in uefi mode as CSM is only a option that is only used when uding the old legacy usb boot device) as its a older hardware i would expect the onboard lan to be working ootb with jun's driver (drivers are in the extra.lzma file) but there is also the option to replace the extra.lzma with one that contains newer drivers thats all you will see on a monitor with jun's loader, anything after that is going to serial port (and needs a null-modem cable to be used) i'd suggest the tc rp loader for dsm 7.1 and ds3622 as system to use there is a tutorial linked above but you can also look here as alternative (older) https://xpenology.club/install-dsm-7-on-baremetal-or-vm/ or look on youtube for a video to install dsm 7.1 don't waste time with 6.x and the older loaders as you will end with a system where you can't update and you will have to look into tc rp loader for that anyway

new platforms: epyc7002 - max CPU threads 24 (Epyc has up to 128 to offer), no new hardware seen yet? r1000 - max CPU threads 16, RS422+, AMD Ryzen R1600 broadwellnkv2 - max CPU threads 24, FS3410, Intel Xeon D-1541, 8-core, not sure why splitting to a new v2 platform from broadwellnk edit: icelaked is also new whats not to be seen is a new intel base replacement for 920+/dva1622, like with J6413/J6426 (elkhart lake) -> no new i915 driver from synology to have 11th/12th gen intel qsv support new r1000 and epyc7002 seem to show that synology goes further to AMD bases systems

you can try to read in https://github.com/pocopico/tinycore-redpill/blob/main/rploader.sh to see whats there beside "add" for ext (-tensions) -> https://github.com/pocopico/redpill-load/blob/develop/ext-manager.sh __action_help () { echo " RedPill Extensions Manager " echo "==============================" echo "Usage: ${MRP_SRC_NAME} <action> [arguments/options]" echo "------------------------------" echo "Actions intended for users:" echo " info" echo " Purpose: Gets information about an extension (or all of them)" echo " Arguments:" echo " [EXT_ID]: id of the extension; optional (if not specified it will list all)" echo " Examples:" echo " ${MRP_SRC_NAME} info # gets info about all installed" echo " ${MRP_SRC_NAME} info thethorgroup.virtio # gets info about thethorgroup.virtio" echo "" echo " add" echo " Purpose: Adds new extension. If exists this action will fail." echo " Arguments:" echo " URL: the url to an index file; argument is mandatory" echo " Example: ${MRP_SRC_NAME} add https://example.tld/sample-ext/rpext-index.json" echo "" echo " force_add" echo " Purpose: Adds new extension. If it exists url is verified to be the same, if not extension is removed" echo " and reinstalled from the URL provided. If extension exists with the same URL nothing happens." echo " Arguments:" echo " EXT_ID: ID of the extension; argument is mandatory" echo " URL: the url to an index file; argument is mandatory" echo " Example: ${MRP_SRC_NAME} force_add example-dev.sample-ext https://example.tld/sample-ext/rpext-index.json" echo "" echo " cleanup" echo " Purpose: Remove all platform (cache) files for an extension. If it does not exists this action will fail." echo " Arguments:" echo " [EXT_IDS]: comma-separated ordered list of extensions to cleanup; optional" echo " Examples:" echo " ${MRP_SRC_NAME} cleanup thethorgroup.virtio,thethorgroup.boot-wait # cleanup only 2 extensions listed" echo " ${MRP_SRC_NAME} cleanup # cleanup all extensions" echo "" echo " remove" echo " Purpose: Remove an extension and all its platform files. If it does not exists this action will fail." echo " Arguments:" echo " EXT_ID: if of the extension to remove; argument is mandatory" echo " Example: ${MRP_SRC_NAME} remove badcoder.unstable-ext" echo "" echo " update" echo " Purpose: Updates information about extensions; this will NOT download platform extensions itself" echo " Arguments:" echo " [EXT_IDS]: comma-separated ordered list of extensions to update; optional" echo " Examples:" echo " ${MRP_SRC_NAME} update thethorgroup.virtio,thethorgroup.boot-wait # update only 2 extensions listed" echo " ${MRP_SRC_NAME} update # update all extensions installed" echo "" echo " help" echo " Purpose: Helping you! (you're reading it right now)" echo " Arguments: takes no arguments" echo "" so there is a "remove" beside "add" also this one gives a hint when wanting to remove a extension } function removebundledexts() { echo "Entering redpill-load directory" cd /home/tc/redpill-load/ echo "Removing bundled exts directories" for bundledext in $(grep ":" bundled-exts.json | awk '{print $2}' | sed -e 's/"//g' | sed -e 's/,/\n/g'); do bundledextdir=$(curl --location -s "$bundledext" | jq -r -e '.id') if [ -d /home/tc/redpill-load/custom/extensions/${bundledextdir} ]; then echo "Removing : ${bundledextdir}" sudo rm -rf /home/tc/redpill-load/custom/extensions/${bundledextdir} fi done } looks like extensions are in /home/tc/redpill-load/custom/extensions/ and if you remove one or more and start building the loader they should not be part of the resulting config

if you got anything usable with local monitor and keyboard then it must be a pretty old dsm installation like 5.x the loader (usb flash drive) would tell more about it and there is usually some hint in the boot menu that comes after the bios settings unlikely if you have 4 drives you usually set it up in any way to have redundancy (like on drive can go missing and all will still be working) most likely would be a raid5 setup where all data are spread over all disks including redundancy information for the case one disks fails assuming is a problem, you need to know and until you do you should be very careful with the disks i'd suggest you start reading about DSM and its specifics, it not just as a normal windows or linux system, there are some specialty's you need to know about before attempting any further steps, dont try to update anything, 1st step is to understand the situation and maybe even copy off all data in a safe way before "experimenting"

where did you check for the disk, usual place would be storage manager and there hdd/ssd try to check out whats in the dmesg log with (activate in dsm and use putty to connect to the dsm system) for the controller: dmesg | grep ahci for the disks: dmesg | grep sd

its now called a extension in the new loader and its name is acpid https://github.com/pocopico/redpill-load/blob/master/redpill-acpid/rpext-index.json { "id": "jumkey.acpid2", ... "name": "ACPI Daemon v2", "description": "ACPI Daemon v2 that handles power button events", ... its also referenced in the tutorial https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ "... The examples illustrate adding ACPI and VIRTIO support. ..."

any test's i'm aware off where unsuccessful as the kernel misses parts for just "adding" the i915 modules (i915 and it's dependencies) and as we are bound to the base kernel of the unit there is no easy way to add that feature there might be way's to add the missing things in a special hand crafted module afterwards but that would need some hacking and extra code and someone willing to invest that amount of time depending on the situation it might be easier to use dva3221 as base and use a nvidia gpu if your hardware is still like that "HW: Asus H170M-Plus, Core i5-6500T" then why not user 918+ or 920+? just reconfigure the loader and ...

the links dont work anymore, its important to look what chip is used but usually because of the limited space i won't expect any port multiplier on the 4 sata version 2 ports wit one pcie lane is no problem at all with pcie 2.0 but if the 4 port version has only one pcie lane it might limit the bandwidth of the disks connected to it (pcie 2.0, one lane = 500 MByte/s) i would also suggest to care for the cable managment, those clots nd pcb's are not made for handling the force of 4 sata cables and its better to make sure it does not strain the pcb/slot to much by some cable guidance (zip ties?)

what dsm type did use, 3617 is the suggested as it has the newer lsi sas driver and its a native driver from synology the 918+ 6.2.3 is kind of dangerous (as can be seen in the place where the additional drivers are offered) i don't know if there are any issues like that with 918/920/dva1622 and dsm 7.x but when using 3622 with dsm 7.x a lsi sas controller should be as good/stable as its expected as long as it ahci compatible it should work, that one is a older 9215 and should work ootb, but with just pcie 2.0 there are limits, escecailly with this one as it only uses one pcie lane and thats just 500 MByte/s (and thats kind of thin for 4 disks and will even limit normal hdd's), if it has to be a marvell with just pcie 2.0 than one with two lanes and 4 ports i prefer newer pcie 3.0 capable chips for more bandwidth like jmb585 or asm1166

you won't have the ability of intel quick sync video with a 11th gen cpu as the best thats possible now is 10th gen (with a extended driver, https://xpenology.com/forum/topic/59909-i915ko-backported-driver-for-intel-10th-gen-ds918-ver-701-up3/) transcoding would still be possible as long as there is enough raw cpu power, if all cores hit 100% then you have maxed out whats possible that way hardware assisted with intel qsv will only work if there is a proper kernel driver loaded and you see devices in /dev/dri if that a deal breaker then you might be better off with a system that uses a normal recent kernel (5.x), like open media vault, depends on what you are looking for but a lot of things that are possible with dsm will work on omv too (you can even get you existing mdadm/lvm2 raid mounted in omv (https://xpenology.com/forum/topic/42793-hp-gen8-dsm-623-25426-update-3-failed/?do=findComment&comment=200475)

the serial usually has no effect when installing, the usb vid/pid needs to mach the values of the usb used for installing/starting so check usb's vid/pid in the grub.cfg that was created from the user_config.json (when building and using "./rploader.sh identifyusb" it should match the usb's hardware) check the hardware usb id with another computer and compare that to whats in the grub.cfg (that one is used when starting the loader, that the part where the "rp" of the tc rp loader kicks in, the tc part is to configure the loader that is later used when booting up dsm) serial only comes into play when it comes to some licensing stuff like multimedia codec's or camera licenses (like default two and more on some systems like dva) a invalid serial should not prevent the system from booting up into dsm

summery for the sata config looks like this 1st controller AMD B350 chipset: 4 x SATA 6Gb/s (from manual) Advanced Micro Devices, Inc. [AMD] 300 Series Chipset SATA Controller [1022:43b7] [ 0.361853] ahci 0000:01:00.1: AHCI 0001.0301 32 slots 8 ports 6 Gbps 0x33 impl SATA mode [ 0.362887] ata1: SATA max UDMA/133 abar m131072@0xf6880000 port 0xf6880100 irq 39 [ 0.362889] ata2: SATA max UDMA/133 abar m131072@0xf6880000 port 0xf6880180 irq 39 [ 0.362889] ata3: DUMMY [ 0.362890] ata4: DUMMY [ 0.362891] ata5: SATA max UDMA/133 abar m131072@0xf6880000 port 0xf6880300 irq 39 [ 0.362893] ata6: SATA max UDMA/133 abar m131072@0xf6880000 port 0xf6880380 irq 39 [ 0.362894] ata7: DUMMY [ 0.362894] ata8: DUMMY 2nd controller 2 x SATA 6Gb/s, The M.2 Socket shares bandwidth with the SATA6G_5/6 ports, therefore the SATA6G_5/6 ports cannot be used when a SATA/PCIE mode M.2 device is installed (from manual) Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] [ 0.363029] ahci 0000:0a:00.2: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0xc impl SATA mode [ 0.363574] ata9: DUMMY [ 0.363575] ata10: DUMMY [ 0.363577] ata11: SATA max UDMA/133 abar m4096@0xf6d08000 port 0xf6d08200 irq 41 [ 0.363578] ata12: SATA max UDMA/133 abar m4096@0xf6d08000 port 0xf6d08280 irq 41 the prevent the "gaps" (dummy) for installing it looks like this might work SataPortMap=20 DiskIdxMap=0002 2nd controller it set to 0 ports and counting for the 1st controller it should only be the first two ports it might also be possible to have all ports defined as seen by the ahci driver and in addition do some port swapping (with syno's kernel parameters) to line up the working ports as the 1st 6 ports used by dsm

more precises gemini lake refresh, J4125, same cpu as in 920+, the "old" i915 driver source synology uses since 6.2.3 would still support that hardware and i checked the i915.ko in DSM_DVA1622_42661.pat, its still 20171222, so its just a 920+ with only two disk slots and more cam licenses from "our" point of view it would make 920+ loader version obsolete (as long as dva1622 supports more disks then its default) and just for documentation, there are no nvidia drivers in dva1622, its just the normal gemini lake image (kernel) as used for the 920+ and with the i915 driver source patch from above it should be usable up to 10th gen cpu's it might be possible to just use the already existing i915 binary modules made for 920+ also for dva1622 as it will use the same (platform based, in this case geminilake) kernel settings for compiling kernel/drivers edit: as its the same platform as 920+ it has the same base kernel config and that will limit the possible cpu threads to 8, kind of unpleasant for "non minimal" cpu configs, disabling HT in bios should be considered for cpu's with more then 4 cores to at least use max. 8 physical cores of a cpu dva3221 vs. dva1622 https://nascompares.com/2022/06/16/synology-dva1622-2-bay-ai-surveillance-nas-now-available/ 918+ vs. 920+(ds1520+ is also the same as 920+ just 5 disk slots instead of 4, same as 918+ vs DS1019+, same thing just o a slot more) https://nascompares.com/2020/05/08/synology-ds920-vs-ds918-nas-drive-comparison/

i used "MiniTool Partition Wizard Free 12.0", but there are also other tools you can use the other way around is kind of common when it comes to windows uefi native or <2TB disks, so you should find a lot of way's to do it i general its just about the parttion table, the partitions are usually not effected by the conversion i guess you could also use gparted as live linux but i have not tested it, the way i tested used is with the (windows) tool above but there should be working links to already converted loaders here: https://xpenology.com/forum/topic/7848-links-to-loaders/ you could just use a older 6.1 version and after writing it to usb replace all files in the 1st and 2nd partition with the files of the newer (6.2) loader

ist für einen karte mit 120€ recht teuer, du brauchst ja eigentlich kein dualport eher sowas oder als bundle mit dac kabel bzw. lwl tranceivern es gibt noch günstiger ConnectX oder ConnectX-2 die würden auch funktionieren ConnectX MT254xx ConnectX-2 MT264xx ConnectX-3 MT275xx schau das es kein InfiniBand ist sondern sfp+ DAC ist von der stange billig bis 7,5m kabel möglich, dahinter ist es immer lwl aber sfp+ noname tranceiver gibt es auch für wenig geld

you would usually delete the partition table with fdisk, cfdisk, sfdisk (sfdisk --delete /dev/sdb) also one way is to just overwrite that area in question with zero's for /dev/sdb dd if=/dev/zero of=/dev/sdb bs=512 count=2 but keep a eye for the device you choose, you dont want to kill your boot disk there are also rescue linux images you can boot to use graphical tools like gparted https://gparted.org/ might be safer as you can better see what you do

die Chips sind dann Aquantia oder Tehuti bei der Asus ist recht klar was man bekommt, bei den anderen kann es unter dem gleichen Namen auch mal sein das zwar der "cpu" Chip der gleiche ist aber der Phy-Chip ein anderer so das man evtl. einen neueren Treiber braucht Asus/Edimax/TP-Link/TRENDnet/StarTech/DeLOCK wären so die günstigen (verglichen mit intel karten) gibt es in der Regel auf SFP+ oder RJ45 und es sind PCIe 4x Karten (von 1x karten würde ich die finger lassen, so was käme nur unter speziellen bedingungen in betracht, wenn man z.b. nur einen 1x pcie 3.0 slot und mit etwas weniger als max. speed leben kann) die sollten dann auch 5G und 2.5G als Verbindung können (bei Base-T/RJ45), falls man das braucht https://geizhals.de/?cat=nwpcie&xf=14063_ASUS~14063_Allnet~14063_DeLOCK~14063_Edimax~14063_StarTech~14063_TP-Link~14063_TRENDnet~14065_LAN-Adapter~14066_PCIe-Karte~14067_PCIe~19524_Marvell~19524_Marvell%2FAquantia~19524_Marvell%2FQLogic~19524_Tehuti wenn man mit ebay kann und sfp+ will dann kann man nach mellanox connectx-3 karten schauen, die sind günstig zu haben, auch im bundle mit dac kabel oder lwl modulen je nach dem wie wichtig das ist kann man auch auf dem stromverbrauch der chips/karten schauen, große kühler haben meist einen grund und auf längere zeit gerechnet kommt da auch was zusammen, ein grund warum man unter umständen lieber einen modernen desktop adapter nimmt statt einem alten gebrauchten server chipsatz kann also lohnen genauer nach dem verbauten chip zu schauen und im datenblatt die tdp nachzuschauen PS: nur angekleber kühlkörper kann sorgen machen wenn er (einfach so) abfällt, meist hat meinen keinen passenden wärmeleit kleber rumliegen und kaufen kann teuer werden, also finger weg wenn der kühlkörper recht kleine ist und man keine befestigung sieht z.b. so was ist mist

you would need at least to change the usb vid/pid in grub.cfg to install maybe look up a video of a dsm 7.x install based on tinycore, might help to see how its done and understand the tutorial better, looks sometimes more complex then it is later like the step with the usb vid/pid you needed to find out with the old loader, that just a command now, no extra tools or massing with the grub.cfg maybe read this one, not recent but interesting too https://xpenology.club/install-dsm-7-on-baremetal-or-vm/ just to mess around you can use any usb flash drive and a old empty disk, just disconnect the stuff you use now and play around with the test usb and disk you can reconnect the old stuff at any time to use the system you have now, if you end with a (new) usb config working for you then you could just use the old disks with the new usb and migrate to the tested configuration its suggested to try out the packages with the new dsm 7 test install to see whats working and whats not or if you can find a source for a 7.x compatible version of a package should be available that might be more of a problem, there is a manual way based on installing java package https://support.jdownloader.org/Knowledgebase/Article/View/synology-nas-installation i guess this old one will not work anymore for 7.x (?) and i have not seen anything newer https://luenepiet.de/public/Synology/JDownloader/ i guess thats because not its more common to use docker https://registry.hub.docker.com/r/jlesage/jdownloader-2/ docker might also often used for plex or emby a backup of the data on your nas, just in case, there are more things that can go wrong then trying to install a new version broken raid's or (logical) volumes have been seen with dsm

if you look up the pci id of that iGPU its 0x3184 https://www.intel.com/content/www/us/en/products/sku/197304/intel-pentium-silver-j5040-processor-4m-cache-up-to-3-20-ghz/specifications.html and if you look into the list i made for synology's driver (its still the same version for 7.0./7.1, no newer backport) then you will find that its already supported, i made a lost of the pci id's in the driver here ("iGPU device ID's supported by synology's i915 driver"): https://xpenology.com/forum/topic/28321-driver-extension-jun-103b104b-for-dsm623-for-918-3615xs-3617xs/ the i915.ko driver (and other *.ko files belonging to it, aka dependencies) is part of dsm itself, no need to add anything and as long as the firmware file are available it will support all the hardware that the driver is capable of if there is nothing in /dev/dri then check the log for the missing firmware files and place them in /usr/lib/firmware/i915/ where the default files from sysnology should already be present

you can use 3622 instead of 3615 if you want 3615 is still supported by synology but updates might not come for longer then 2 years as its expected that 7.1 was the last version for it and synology plans to only support the recent and last dsm version and if 7.2 comes out then 7.1 will be that last/only supported version for 3615 the last two digits are the release year of the original hardware unit and the minimum is 5 years support so 3622 will get support for some time from synology where 3615 is coming to its end

kind of thin description, no dsm type (918+ uses intel quick sync what others like 3617 cant), there are a lot of "carbon" products from msi (guess how many people will invest time to find out what exaxtly you "might" have) also most boards come with up to 6 onboard sata (like Z370 GAMING PRO CARBON), and as you have at least 7 sata drives (8th ssd drive can be sata or nvme - also not clear) you might have a additional controller also important would be to read up about 3rd party packages in dsm, as synology changed the format you should check if all packages you need are available and for the howto, that one is about baremetal and there is no "one fits all, no brain needed" solution, you might even run into trouble with the sata controllers and need to handle some values manually (SataPortMap, DiskIdxMap) https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ in general, when using any cache (ssd/nvme) disable it before migration, if things work out you can re-enable it later, also it suggested to have a backup

that's not really the pci id you you use to look in up in the driver "lspci -vvn" would give you "8086:15b7" plus u subsystem id that would be the thing you look for but you dont need to as i already told you the driver you need is e1000e and thats the extension you need to look for, if its not added then there is something wrong but as dsm for a lot of units comes with a e1000e driver itself it might work ootb without any additional driver, depending on the nic's hardware (there might be newer revisions/phy's not working with syno's default driver), the driver in 918+ seems to be at least 3 years old (v3.4.2.4) but the "latest" i've seen is 3.8.7 from 10/2020 my goal was to enable you (or anyone interested) to find out by themself if the driver needed is there even before installing/using tc loader and it can be done with the pci id of the device and the json file or the correct driver file from tc's source on github

imho nein, das ist syno spezifisch und im kernel eingebaut (oder wbwn nicht drin wie bei den consumer modellen) hast du das mal probiert? SataPortMap=24 DiskIdxMap=0400 wenn der 2er vorn ist sollte das die reihenfolfe wie dsm sie benutzt umkehren und die ersten 4 ports sollten dann vom 4er sein alternativ kannst du auch das versuchen das sollte die zwei ports ignorieren SataPortMap=04 DiskIdxMap=0400