Peter Suh Posted June 22, 2022 Share #151 Posted June 22, 2022 (edited) The DS920+ recommended 4 ports As Dolbycat tested, there is no problem with operation even if you increase it to six. I increased the maximum to 16 and changed it to be available. So, on dtc DS920(4 port)+, DS1621+(6 port) Jun mode, If you use the dynamic dtb mapping feature with the jumkey option, we have implemented it to extend to 16 ports so that automatic mapping is recognized. "Jumkey.qjs.dtb" ext has been modified a little to force the use of the dtb file for 16 ports. If you want to use the dts file manually, you can download it by referring to my GitHub. https://github.com/PeterSuh-Q3/tinycore-redpill After downloading and installing as shown below, Build the load again curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" --output my.sh.gz; tar -zxvf my.sh.gz; ./my.sh DS920+J jumkey noclean ./my.sh DS1621+J jumkey noclean Use the ll command to check if the model.dtb file is in the list ll /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds920p_42218 ll /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds1621p_42218 If you check once again whether the script (spoiler) below looks like the one I modified with the cat command, it will definitely be applied. cat /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds920p_42218/install_rd.sh cat /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds1621p_42218/install_rd.sh Spoiler #!/bin/sh tar -zxvf patch.tar.gz # install dtc chmod +x dtc cp dtc /usr/sbin/dtc # copy 16 ports dts file to /etc.defaults #echo $PLATFORM_ID if [ "${PLATFORM_ID}" = "ds920p_42218" ]; then echo "copy DS920+'s 16 ports ds920p_16ports.dts to /etc.defaults" ./dtc -I dts -O dtb -o model.dtb ds920p_16ports.dts cp -vf model.dtb /etc.defaults/model.dtb elif [ "${PLATFORM_ID}" = "ds1621p_42218" ]; then echo "copy DS1621+'s 16 ports ds1621p_16ports.dts to /etc.defaults" ./dtc -I dts -O dtb -o model.dtb ds1621p_16ports.dts cp -vf model.dtb /etc.defaults/model.dtb fi # copy file if [ ! -f model_${PLATFORM_ID%%_*}.dtb ]; then # Dynamic generation ./dtc -I dtb -O dts -o output.dts /etc.defaults/model.dtb qjs --std ./dts.js output.dts output.dts.out if [ $? -ne 0 ]; then echo "auto generated dts file is broken" exit 0 fi ./dtc -I dts -O dtb -o model_r2.dtb output.dts.out cp -vf model_r2.dtb /etc.defaults/model.dtb cp -vf model_r2.dtb /var/run/model.dtb else cp -vf model_${PLATFORM_ID%%_*}.dtb /etc.defaults/model.dtb cp -vf model_${PLATFORM_ID%%_*}.dtb /var/run/model.dtb fi I've installed up to 14 discs. 6 built-in sata I used the following product, external 8 ports (Marvel 88SE9215 chip 4 ports + ASM1166 chip 2 ports [unrecognized]) X2. https://ko.aliexpress.com/item/33016481933.html Edited June 22, 2022 by Peter Suh 1 2 Quote Link to comment Share on other sites More sharing options...
igbs Posted June 22, 2022 Share #152 Posted June 22, 2022 Hello team, I need the help of audience.... I've got the mobo Asrock C3558D4I-4L ... supported 9 SATA ports in different configurations.. I have tried to install many different images: ./my.sh DS920+, /my.sh DS918+, /my.sh DS3622xs+ and Syno Assist can't find any disk: for the Config.1: Found "00:13.0 Intel Corporation DNV SATA Controller 0 (rev 11)" Detected 8 ports/3 drives. Bad ports: -7 -6 -5 -4. Override # of ports or ENTER to accept <8> Found "00:14.0 Intel Corporation DNV SATA Controller 1 (rev 11)" Detected 6 ports/0 drives. Bad ports: 1 2 3 4 5. Override # of ports or ENTER to accept <6> Computed settings: SataPortMap=86 DiskIdxMap=0008 WARNING: Bad ports are mapped. The DSM installation will fail! for the config.2: Found "00:14.0 Intel Corporation DNV SATA Controller 1 (rev 11)" Detected 6 ports/1 drives. Bad ports: 3. Override # of ports or ENTER to accept <6> Computed settings: SataPortMap=6 DiskIdxMap=00 WARNING: Bad ports are mapped. The DSM installation will fail! ALSO I've tried to build the image with the disk tree mode: ./my.sh DS920+J jumkey noclean and ./my.sh DS1621+J jumkey noclean ... the same result Need your help please! Any suggestions? Thanks.. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 23, 2022 Share #153 Posted June 23, 2022 16 hours ago, igbs said: Hello team, I need the help of audience.... I've got the mobo Asrock C3558D4I-4L ... supported 9 SATA ports in different configurations.. I have tried to install many different images: ./my.sh DS920+, /my.sh DS918+, /my.sh DS3622xs+ and Syno Assist can't find any disk: for the Config.1: Found "00:13.0 Intel Corporation DNV SATA Controller 0 (rev 11)" Detected 8 ports/3 drives. Bad ports: -7 -6 -5 -4. Override # of ports or ENTER to accept <8> Found "00:14.0 Intel Corporation DNV SATA Controller 1 (rev 11)" Detected 6 ports/0 drives. Bad ports: 1 2 3 4 5. Override # of ports or ENTER to accept <6> Computed settings: SataPortMap=86 DiskIdxMap=0008 WARNING: Bad ports are mapped. The DSM installation will fail! for the config.2: Found "00:14.0 Intel Corporation DNV SATA Controller 1 (rev 11)" Detected 6 ports/1 drives. Bad ports: 3. Override # of ports or ENTER to accept <6> Computed settings: SataPortMap=6 DiskIdxMap=00 WARNING: Bad ports are mapped. The DSM installation will fail! ALSO I've tried to build the image with the disk tree mode: ./my.sh DS920+J jumkey noclean and ./my.sh DS1621+J jumkey noclean ... the same result Need your help please! Any suggestions? Thanks.. According to the MOBO guide The problem seems to be that the number of SATAports is too large. https://www.asrockrack.com/general/productdetail.asp?Model=C3558D4I-4L#Specifications 5 SATA3 6.0 Gb/s: 3 SATA3 ports, 2 SATA DOM (SATA_0, SATA_1, SATA_2, SATA_3 and SATA_12) Supports up to 8 SATA ports from 2 mini SAS HD connectors (SATA_4_7 and SATA_8_11) by BIOS setting (4 x SATA ports from each mini SAS HD connector) If you count the total number of ports in the above content, it seems to be 18. right? If you look at the script of pocopico's rploader.sh, you will find the following The default value of maxdisks is 16. It seems that diskidxmapidx exceeds this 16 by some calculation. # ports > maxdisks? [ $diskidxmapidx -gt $maxdisks ] && echo "WARNING: mapped SATA port count exceeds maxdisks" Disable the SATA ports that are not actually used There seems to be a way to slightly increase the maxdisks value in the user_config.json file, The latter method seems to have some problems. Quote Link to comment Share on other sites More sharing options...
igbs Posted June 23, 2022 Share #154 Posted June 23, 2022 Thanks Peter.. Actually the mobo has 6 different bios configuration for the SATA ports - the max supporting SATA drives are 9 only.. I found on the google: The C3558D4I-4L has 13 storage connectors, of which up to 9 can be connected at once. 7 configurations of PCI-E, SAS and Mini-SAS HD Connector are possible. They are: config1 PCI-E x4, 5x SATA 9 ports config2 PCI-E x4, 1x Mini-SAS HD (A), 1x SATA 5 ports config3 PCI-E x4, 1x Mini-SAS HD (B), 1x SATA 5 ports config4 PCI-E x8, 1x SATA 1 port! config5 5x SATA, 1x Mini-SAS HD (A) 9 ports config6 2x Mini-SAS HD, 1x SATA 9 ports config7 5x SATA, 1x Mini-SAS HD (B) 9 ports As you can see, none of the configurations lets me attach 12 drives. I switched the BIOS settings to config2 - 5ports... still Syno Assist. can't find the HD drives I connect the putty to the COM-port and check - the OS can see all drives.. Something wrong.. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 24, 2022 Share #155 Posted June 24, 2022 5 hours ago, igbs said: Thanks Peter.. Actually the mobo has 6 different bios configuration for the SATA ports - the max supporting SATA drives are 9 only.. I found on the google: The C3558D4I-4L has 13 storage connectors, of which up to 9 can be connected at once. 7 configurations of PCI-E, SAS and Mini-SAS HD Connector are possible. They are: config1 PCI-E x4, 5x SATA 9 ports config2 PCI-E x4, 1x Mini-SAS HD (A), 1x SATA 5 ports config3 PCI-E x4, 1x Mini-SAS HD (B), 1x SATA 5 ports config4 PCI-E x8, 1x SATA 1 port! config5 5x SATA, 1x Mini-SAS HD (A) 9 ports config6 2x Mini-SAS HD, 1x SATA 9 ports config7 5x SATA, 1x Mini-SAS HD (B) 9 ports As you can see, none of the configurations lets me attach 12 drives. I switched the BIOS settings to config2 - 5ports... still Syno Assist. can't find the HD drives I connect the putty to the COM-port and check - the OS can see all drives.. Something wrong.. From the console you connected to your com-port, give me the following 3 logs. These seem to be long logs. Please use the spoiler icon on the far right. cat /var/log/*rc* ls -l /sys/block ls -la /sys/class/ata_device Quote Link to comment Share on other sites More sharing options...
igbs Posted June 24, 2022 Share #156 Posted June 24, 2022 Spoiler SynologyNAS> cat /var/log/*rc* START /linuxrc.syno.impl '/etc.defaults/model.dtb' -> '/var/run/model.dtb' Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "igb.ko" for pocopico.igb (args: ) Loading kmod #0 "dca.ko" for pocopico.ixgbe (args: ) Loading kmod #1 "vxlan.ko" for pocopico.ixgbe (args: ) insmod: can't insert 'vxlan.ko': unknown symbol in module, or unknown parameter ERROR: kernel extensions "vxlan.ko" from pocopico.ixgbe failed to load Exit on error [99] rp ext init exec failure... Fri Jun 24 02:42:30 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 Spoiler SynologyNAS> ls -l /sys/block lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram0 -> ../devices/virtual/block/ram0 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram1 -> ../devices/virtual/block/ram1 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram10 -> ../devices/virtual/block/ram10 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram11 -> ../devices/virtual/block/ram11 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram12 -> ../devices/virtual/block/ram12 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram13 -> ../devices/virtual/block/ram13 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram14 -> ../devices/virtual/block/ram14 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram15 -> ../devices/virtual/block/ram15 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram2 -> ../devices/virtual/block/ram2 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram3 -> ../devices/virtual/block/ram3 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram4 -> ../devices/virtual/block/ram4 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram5 -> ../devices/virtual/block/ram5 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram6 -> ../devices/virtual/block/ram6 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram7 -> ../devices/virtual/block/ram7 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram8 -> ../devices/virtual/block/ram8 lrwxrwxrwx 1 root root 0 Jun 24 02:48 ram9 -> ../devices/virtual/block/ram9 lrwxrwxrwx 1 root root 0 Jun 24 02:42 sata1 -> ../devices/pci0000:00/0000:00:13.0/ata5/host4/target4:0:0/4:0:0:0/block/sata1 lrwxrwxrwx 1 root root 0 Jun 24 02:42 sata2 -> ../devices/pci0000:00/0000:00:13.0/ata6/host5/target5:0:0/5:0:0:0/block/sata2 lrwxrwxrwx 1 root root 0 Jun 24 02:48 synoboot -> ../devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1:1.0/host8/target8:0:0/8:0:0:0/block/synoboot Spoiler SynologyNAS> ls -la /sys/class/ata_device drwxr-xr-x 2 root root 0 Jun 24 02:52 . drwxr-xr-x 46 root root 0 Jun 24 02:43 .. lrwxrwxrwx 1 root root 0 Jun 24 02:52 dev1.0 -> ../../devices/pci0000:00/0000:00:13.0/ata1/link1/dev1.0/ata_device/dev1.0 lrwxrwxrwx 1 root root 0 Jun 24 02:52 dev2.0 -> ../../devices/pci0000:00/0000:00:13.0/ata2/link2/dev2.0/ata_device/dev2.0 lrwxrwxrwx 1 root root 0 Jun 24 02:52 dev3.0 -> ../../devices/pci0000:00/0000:00:13.0/ata3/link3/dev3.0/ata_device/dev3.0 lrwxrwxrwx 1 root root 0 Jun 24 02:52 dev4.0 -> ../../devices/pci0000:00/0000:00:13.0/ata4/link4/dev4.0/ata_device/dev4.0 lrwxrwxrwx 1 root root 0 Jun 24 02:52 dev5.0 -> ../../devices/pci0000:00/0000:00:13.0/ata5/link5/dev5.0/ata_device/dev5.0 lrwxrwxrwx 1 root root 0 Jun 24 02:52 dev6.0 -> ../../devices/pci0000:00/0000:00:13.0/ata6/link6/dev6.0/ata_device/dev6.0 lrwxrwxrwx 1 root root 0 Jun 24 02:52 dev7.0 -> ../../devices/pci0000:00/0000:00:13.0/ata7/link7/dev7.0/ata_device/dev7.0 lrwxrwxrwx 1 root root 0 Jun 24 02:52 dev8.0 -> ../../devices/pci0000:00/0000:00:13.0/ata8/link8/dev8.0/ata_device/dev8.0 Please... I connect 2 drives only for now.. Quote Link to comment Share on other sites More sharing options...
jumkey Posted June 24, 2022 Author Share #157 Posted June 24, 2022 32 minutes ago, igbs said: ERROR: kernel extensions "vxlan.ko" from pocopico.ixgbe failed to load Exit on error [99] rp ext init exec failure... It seems that the dtb extension is not loaded correctly because of this error Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 24, 2022 Share #158 Posted June 24, 2022 (edited) There are some unknowns. Jun mode is not used and seems to be one of the three Jot Modes below. Which of the three commands did you use? ./my.sh DS920+, /my.sh DS918+, /my.sh DS3622xs+ ./my.sh DS920+ looks promising, right? By any chance, do you have an additionally installed 10GB NIC? And, the built-in nic looks like Marvell 88E1543 ( I210 ), it seems that igb ext was used. Edited June 24, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
igbs Posted June 24, 2022 Share #159 Posted June 24, 2022 Hello guys, Now I'm using Intel 82576 2x1.25Gb in the PCIe-slot ... plus (you are right) the mobo has 4x Marvell 88E1543 ( I210 ) built-in.. I can't connect to any of Marvell 88E1543 4 ports (because of error??)... but Intel 82576 works fine ... I've tried also ./my.sh DS920+J jumkey - no go.. The last image is .. ./my.sh DS920+ I think .. I need to wipe out first 10..15% of the HDD space and try again... because they are not a new HDD .. I used before in the Syno .. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 24, 2022 Share #160 Posted June 24, 2022 22 minutes ago, igbs said: Hello guys, Now I'm using Intel 82576 2x1.25Gb in the PCIe-slot ... plus (you are right) the mobo has 4x Marvell 88E1543 ( I210 ) built-in.. I can't connect to any of Marvell 88E1543 4 ports (because of error??)... but Intel 82576 works fine ... I've tried also ./my.sh DS920+J jumkey - no go.. The last image is .. ./my.sh DS920+ I think .. I need to wipe out first 10..15% of the HDD space and try again... because they are not a new HDD .. I used before in the Syno .. Perhaps only pocopico can accurately answer the nic ext problem. IMHO, Intel 82576 igb is also used, and Marvell 88E1543 also seems to be sufficient with igb. I don't know why ixgbe ext is automatically added and causes an error. One way is to prevent ixgbe from being added automatically. There seems to be a way to use only igb. To do so, proceed as follows. ./rploader.sh clean ./rploader.sh ext geminilake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/igb/rpext-index.json ./my.sh DS920+ manual or ./rploader.sh clean ./rploader.sh ext geminilake-7.0.1-42218-JUN add https://raw.githubusercontent.com/pocopico/rp-ext/master/igb/rpext-index.json ./my.sh DS920+J jumkey manual 1 Quote Link to comment Share on other sites More sharing options...
igbs Posted June 24, 2022 Share #161 Posted June 24, 2022 Thanks.. will try... I need the ixgbe also ... I've got the Intel X520 10Gb PCIe-card and have a plan to use it.. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 24, 2022 Share #162 Posted June 24, 2022 1 hour ago, igbs said: Thanks.. will try... I need the ixgbe also ... I've got the Intel X520 10Gb PCIe-card and have a plan to use it.. X520 10Gb PCIe is probably dual port, When used with igb ext , there was a problem of conflict. I'm not sure if this part is completely resolved or not. How to use ixgbe ext without conflict for current X520 10Gb dual NIC you are using DS3622xs+. DS3622xs+ already includes the vanilla version of ixgbe, so if pocopico's ext is duplicated, an error will also occur. So, how to safely use ext in X520 10Gb dual NIC is as follows. Build DS3622xs+ loader without plugging X520 10Gb into PC X520 10Gb is to plug in later. https://github.com/pocopico/rp-ext/issues/103 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 24, 2022 Share #163 Posted June 24, 2022 (edited) @jumkey So far, the dtc method has been I thought it was limited to DS920+ and DS1621+, so I didn't try it at all. jumkey, Your repo has traces of preparing DS918+. { "id": "jumkey.qjs.000", "url": "https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/rpext-index.json", "info": { "name": "QuickJS Javascript Engine", "description": "QuickJS Javascript Engine", "author_url": "https://bellard.org/", "packer_url": "https://bellard.org/quickjs/", "help_url": "https://bellard.org/quickjs/quickjs.html" }, "releases": { "ds918p_42218": "https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/recipes/universal.json", "ds920p_42218": "https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/recipes/universal.json", "ds1621p_42218": "https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/recipes/universal.json", "ds2422p_42218": "https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/recipes/universal.json", "ds920p_42661": "https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/recipes/universal.json" } } So, I modified the redpill-qjs-dtb script in my repo for DS918+ and tested it with ds918+. For this purpose, sataportmap and DiskIdxMap in user_config.json have been deleted in advance. Due to the above values, there was a phenomenon that the sata port mapping that dtc had to find all was disturbed. Because quickjs does not dynamically detect ports automatically for ds918+. I made a pre-mapped dtb file forcibly and put it as shown below. 'model_ds918p_42218.dtb' -> '/etc.defaults/model.dtb' 'model_ds918p_42218.dtb' -> '/var/run/model.dtb' It seems to be working fine. I used disc 12, all recognized fine. So, I have one request. Classified as /sys/block/sd# as well as /sys/block/sata# in quickjs Can it be modified to map ports on disks as well? https://github.com/jumkey/redpill-load/blob/develop/redpill-qjs-dtb/src/dts-js/src/index.js Below are my bare metal DS918+ junior logs and The status is displayed under /sys/block. Please note. Spoiler DiskStation> cd /var/log DiskStation> ll drwxr-xr-x 2 root root 0 Jun 24 14:01 . drwxr-xr-x 9 root root 0 Jun 24 14:01 .. -rw-r--r-- 1 root root 36 Jun 24 14:01 junior_reason -rw-r--r-- 1 root root 1497 Jun 24 14:01 juniorexpansionpack.log -rw-r--r-- 1 root root 6850 Jun 24 14:01 linuxrc.syno.log -rw-r--r-- 1 root root 404943 Jun 24 14:02 messages -rw-r--r-- 1 root root 72 Jun 24 14:01 upgrade_sh.log DiskStation> cat linuxrc.syno.log START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) Loading kmod #0 "igb.ko" for pocopico.igb (args: ) Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script Checking for VirtIO *No* VirtIO hypervisor detected NOT loading kmods for thethorgroup.virtio :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "install_rd.sh" for jumkey.qjs.000->on_boot qjs hello world from qjs Ran "install_rd.sh" for jumkey.qjs.000->on_boot - exit=0 Running "install_rd.sh" for jumkey.qjs.dtb->on_boot dtc dts.js copy DS918+'s 16 ports ds918p_16ports.dts to /etc.defaults ds918p_16ports.dts:17.14-23.5: Warning (unit_address_vs_reg): /DX517/pmp_slot@1: node has a unit name, but no reg or ranges property ds918p_16ports.dts:25.14-31.5: Warning (unit_address_vs_reg): /DX517/pmp_slot@2: node has a unit name, but no reg or ranges property ds918p_16ports.dts:33.14-39.5: Warning (unit_address_vs_reg): /DX517/pmp_slot@3: node has a unit name, but no reg or ranges property ds918p_16ports.dts:41.14-47.5: Warning (unit_address_vs_reg): /DX517/pmp_slot@4: node has a unit name, but no reg or ranges property ds918p_16ports.dts:49.14-55.5: Warning (unit_address_vs_reg): /DX517/pmp_slot@5: node has a unit name, but no reg or ranges property ds918p_16ports.dts:58.25-73.11: Warning (unit_address_vs_reg): /internal_slot@1: node has a unit name, but no reg or ranges property ds918p_16ports.dts:74.25-89.11: Warning (unit_address_vs_reg): /internal_slot@2: node has a unit name, but no reg or ranges property ds918p_16ports.dts:90.25-105.11: Warning (unit_address_vs_reg): /internal_slot@3: node has a unit name, but no reg or ranges property ds918p_16ports.dts:106.25-121.11: Warning (unit_address_vs_reg): /internal_slot@4: node has a unit name, but no reg or ranges property ds918p_16ports.dts:122.25-137.11: Warning (unit_address_vs_reg): /internal_slot@5: node has a unit name, but no reg or ranges property ds918p_16ports.dts:138.25-153.11: Warning (unit_address_vs_reg): /internal_slot@6: node has a unit name, but no reg or ranges property ds918p_16ports.dts:154.25-169.11: Warning (unit_address_vs_reg): /internal_slot@7: node has a unit name, but no reg or ranges property ds918p_16ports.dts:170.25-185.11: Warning (unit_address_vs_reg): /internal_slot@8: node has a unit name, but no reg or ranges property ds918p_16ports.dts:186.25-201.11: Warning (unit_address_vs_reg): /internal_slot@9: node has a unit name, but no reg or ranges property ds918p_16ports.dts:202.26-217.11: Warning (unit_address_vs_reg): /internal_slot@10: node has a unit name, but no reg or ranges property ds918p_16ports.dts:218.26-233.11: Warning (unit_address_vs_reg): /internal_slot@11: node has a unit name, but no reg or ranges property ds918p_16ports.dts:234.26-249.11: Warning (unit_address_vs_reg): /internal_slot@12: node has a unit name, but no reg or ranges property ds918p_16ports.dts:250.26-265.11: Warning (unit_address_vs_reg): /internal_slot@13: node has a unit name, but no reg or ranges property ds918p_16ports.dts:266.26-281.11: Warning (unit_address_vs_reg): /internal_slot@14: node has a unit name, but no reg or ranges property ds918p_16ports.dts:282.26-297.11: Warning (unit_address_vs_reg): /internal_slot@15: node has a unit name, but no reg or ranges property ds918p_16ports.dts:298.26-313.11: Warning (unit_address_vs_reg): /internal_slot@16: node has a unit name, but no reg or ranges property ds918p_16ports.dts:316.15-322.4: Warning (unit_address_vs_reg): /esata_port@1: node has a unit name, but no reg or ranges property ds918p_16ports.dts:324.13-337.4: Warning (unit_address_vs_reg): /usb_slot@1: node has a unit name, but no reg or ranges property ds918p_16ports.dts:339.13-352.4: Warning (unit_address_vs_reg): /usb_slot@2: node has a unit name, but no reg or ranges property ds918p_16ports.dts:354.14-357.4: Warning (unit_address_vs_reg): /nvme_slot@1: node has a unit name, but no reg or ranges property ds918p_16ports.dts:359.14-362.4: Warning (unit_address_vs_reg): /nvme_slot@2: node has a unit name, but no reg or ranges property cp: can't stat 'model.dtb': No such file or directory 'model_ds918p_42218.dtb' -> '/etc.defaults/model.dtb' 'model_ds918p_42218.dtb' -> '/var/run/model.dtb' Ran "install_rd.sh" for jumkey.qjs.dtb->on_boot - exit=0 Running "check-e1000e.sh" for pocopico.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for pocopico.e1000e->on_boot - exit=0 Running "check-igb.sh" for pocopico.igb->on_boot Loading module igb -> Module igb loaded succesfully Ran "check-igb.sh" for pocopico.igb->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 Insert synorbd kernel module Insert synofsbd kernel module Insert sha256 kernel module Assemble args: -u 6a218281:5374c81b:05d949f7:b0bbaec7 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdh1 /dev/sdi1 /dev/sdj1 /dev/sdm1 /dev/sdn1 mdadm: /dev/sdg1 has wrong uuid. mdadm: /dev/sdh1 has wrong uuid. mdadm: ignoring /dev/sda1 as it reports /dev/sdc1 as failed mdadm: /dev/md0 has been started with 2 drives (out of 16). Partition Version=8 /sbin/e2fsck exists, checking /dev/md0... e2fsck 1.44.1 (24-Mar-2018) /sbin/e2fsck -yvf returns 0 Mounting /dev/md0 /tmpRoot ------------upgrade Begin upgrade procedure Failed to found any patch No upgrade file found ============upgrade ------------bootup-smallupdate Failed to AssertFileKeyValueEqual value1: /etc.defaults/synoinfo.conf:unique -> synology_apollolake_918+ value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_v1000_1621+ Skip bootup smallupdate, because root is not matched to junior ============bootup-smallupdate Exit on error [2] .noroot exists... Fri Jun 24 14:01:04 UTC 2022 /dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 Spoiler DiskStation> ll /sys/block drwxr-xr-x 2 root root 0 Jun 24 14:01 . dr-xr-xr-x 12 root root 0 Jun 24 14:01 .. lrwxrwxrwx 1 root root 0 Jun 24 14:01 md0 -> ../devices/virtual/block/md0 lrwxrwxrwx 1 root root 0 Jun 24 14:01 md1 -> ../devices/virtual/block/md1 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram0 -> ../devices/virtual/block/ram0 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram1 -> ../devices/virtual/block/ram1 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram10 -> ../devices/virtual/block/ram10 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram11 -> ../devices/virtual/block/ram11 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram12 -> ../devices/virtual/block/ram12 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram13 -> ../devices/virtual/block/ram13 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram14 -> ../devices/virtual/block/ram14 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram15 -> ../devices/virtual/block/ram15 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram2 -> ../devices/virtual/block/ram2 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram3 -> ../devices/virtual/block/ram3 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram4 -> ../devices/virtual/block/ram4 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram5 -> ../devices/virtual/block/ram5 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram6 -> ../devices/virtual/block/ram6 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram7 -> ../devices/virtual/block/ram7 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram8 -> ../devices/virtual/block/ram8 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram9 -> ../devices/virtual/block/ram9 lrwxrwxrwx 1 root root 0 Jun 24 14:01 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdc lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdd -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd lrwxrwxrwx 1 root root 0 Jun 24 14:01 sde -> ../devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sde lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdf -> ../devices/pci0000:00/0000:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sdf lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdg -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sdg lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdh -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata8/host7/target7:0:0/7:0:0:0/block/sdh lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdi -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata9/host8/target8:0:0/8:0:0:0/block/sdi lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdj -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sdj lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdm -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/ata13/host12/target12:0:0/12:0:0:0/block/sdm lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdn -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/ata14/host13/target13:0:0/13:0:0:0/block/sdn lrwxrwxrwx 1 root root 0 Jun 24 14:02 synoboot -> ../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/host14/target14:0:0/14:0:0:0/block/synoboot Spoiler lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata1 -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sata1 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata10 -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sata10 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata11 -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/ata13/host12/target12:0:0/12:0:0:0/block/sata11 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata12 -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/ata14/host13/target13:0:0/13:0:0:0/block/sata12 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata2 -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sata2 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata3 -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sata3 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata4 -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sata4 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata5 -> ../devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sata5 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata6 -> ../devices/pci0000:00/0000:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sata6 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata7 -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sata7 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata8 -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata8/host7/target7:0:0/7:0:0:0/block/sata8 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata9 -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata9/host8/target8:0:0/8:0:0:0/block/sata9 Edited June 24, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
jumkey Posted June 24, 2022 Author Share #164 Posted June 24, 2022 13 minutes ago, Peter Suh said: @jumkey So far, the dtc method has been I thought it was limited to DS920+ and DS1621+, so I didn't try it at all. jumkey, Your repo has traces of preparing DS918+. { "id": "jumkey.qjs.000", "url": "https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/rpext-index.json", "info": { "name": "QuickJS Javascript Engine", "description": "QuickJS Javascript Engine", "author_url": "https://bellard.org/", "packer_url": "https://bellard.org/quickjs/", "help_url": "https://bellard.org/quickjs/quickjs.html" }, "releases": { "ds918p_42218": "https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/recipes/universal.json", "ds920p_42218": "https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/recipes/universal.json", "ds1621p_42218": "https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/recipes/universal.json", "ds2422p_42218": "https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/recipes/universal.json", "ds920p_42661": "https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/recipes/universal.json" } } So, I modified the redpill-qjs-dtb script in my repo for DS918+ and tested it with ds918+. For this purpose, sataportmap and DiskIdxMap in user_config.json have been deleted in advance. Due to the above values, there was a phenomenon that the sata port mapping that dtc had to find all was disturbed. Because quickjs does not dynamically detect ports automatically for ds918+. I made a pre-mapped dtb file forcibly and put it as shown below. 'model_ds918p_42218.dtb' -> '/etc.defaults/model.dtb' 'model_ds918p_42218.dtb' -> '/var/run/model.dtb' It seems to be working fine. I used disc 12, all recognized fine. So, I have one request. Classified as device/sd# as well as device/sata# in quickjs Can it be modified to map ports on disks as well? Below are my bare metal DS918+ junior logs and The status is displayed under /sys/block. Please note. DS918+ jun mode junior log (Reveal hidden contents) DiskStation> cd /var/log DiskStation> ll drwxr-xr-x 2 root root 0 Jun 24 14:01 . drwxr-xr-x 9 root root 0 Jun 24 14:01 .. -rw-r--r-- 1 root root 36 Jun 24 14:01 junior_reason -rw-r--r-- 1 root root 1497 Jun 24 14:01 juniorexpansionpack.log -rw-r--r-- 1 root root 6850 Jun 24 14:01 linuxrc.syno.log -rw-r--r-- 1 root root 404943 Jun 24 14:02 messages -rw-r--r-- 1 root root 72 Jun 24 14:01 upgrade_sh.log DiskStation> cat linuxrc.syno.log START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module xhci-pci ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) Loading kmod #0 "igb.ko" for pocopico.igb (args: ) Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script Checking for VirtIO *No* VirtIO hypervisor detected NOT loading kmods for thethorgroup.virtio :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "install_rd.sh" for jumkey.qjs.000->on_boot qjs hello world from qjs Ran "install_rd.sh" for jumkey.qjs.000->on_boot - exit=0 Running "install_rd.sh" for jumkey.qjs.dtb->on_boot dtc dts.js copy DS918+'s 16 ports ds918p_16ports.dts to /etc.defaults ds918p_16ports.dts:17.14-23.5: Warning (unit_address_vs_reg): /DX517/pmp_slot@1: node has a unit name, but no reg or ranges property ds918p_16ports.dts:25.14-31.5: Warning (unit_address_vs_reg): /DX517/pmp_slot@2: node has a unit name, but no reg or ranges property ds918p_16ports.dts:33.14-39.5: Warning (unit_address_vs_reg): /DX517/pmp_slot@3: node has a unit name, but no reg or ranges property ds918p_16ports.dts:41.14-47.5: Warning (unit_address_vs_reg): /DX517/pmp_slot@4: node has a unit name, but no reg or ranges property ds918p_16ports.dts:49.14-55.5: Warning (unit_address_vs_reg): /DX517/pmp_slot@5: node has a unit name, but no reg or ranges property ds918p_16ports.dts:58.25-73.11: Warning (unit_address_vs_reg): /internal_slot@1: node has a unit name, but no reg or ranges property ds918p_16ports.dts:74.25-89.11: Warning (unit_address_vs_reg): /internal_slot@2: node has a unit name, but no reg or ranges property ds918p_16ports.dts:90.25-105.11: Warning (unit_address_vs_reg): /internal_slot@3: node has a unit name, but no reg or ranges property ds918p_16ports.dts:106.25-121.11: Warning (unit_address_vs_reg): /internal_slot@4: node has a unit name, but no reg or ranges property ds918p_16ports.dts:122.25-137.11: Warning (unit_address_vs_reg): /internal_slot@5: node has a unit name, but no reg or ranges property ds918p_16ports.dts:138.25-153.11: Warning (unit_address_vs_reg): /internal_slot@6: node has a unit name, but no reg or ranges property ds918p_16ports.dts:154.25-169.11: Warning (unit_address_vs_reg): /internal_slot@7: node has a unit name, but no reg or ranges property ds918p_16ports.dts:170.25-185.11: Warning (unit_address_vs_reg): /internal_slot@8: node has a unit name, but no reg or ranges property ds918p_16ports.dts:186.25-201.11: Warning (unit_address_vs_reg): /internal_slot@9: node has a unit name, but no reg or ranges property ds918p_16ports.dts:202.26-217.11: Warning (unit_address_vs_reg): /internal_slot@10: node has a unit name, but no reg or ranges property ds918p_16ports.dts:218.26-233.11: Warning (unit_address_vs_reg): /internal_slot@11: node has a unit name, but no reg or ranges property ds918p_16ports.dts:234.26-249.11: Warning (unit_address_vs_reg): /internal_slot@12: node has a unit name, but no reg or ranges property ds918p_16ports.dts:250.26-265.11: Warning (unit_address_vs_reg): /internal_slot@13: node has a unit name, but no reg or ranges property ds918p_16ports.dts:266.26-281.11: Warning (unit_address_vs_reg): /internal_slot@14: node has a unit name, but no reg or ranges property ds918p_16ports.dts:282.26-297.11: Warning (unit_address_vs_reg): /internal_slot@15: node has a unit name, but no reg or ranges property ds918p_16ports.dts:298.26-313.11: Warning (unit_address_vs_reg): /internal_slot@16: node has a unit name, but no reg or ranges property ds918p_16ports.dts:316.15-322.4: Warning (unit_address_vs_reg): /esata_port@1: node has a unit name, but no reg or ranges property ds918p_16ports.dts:324.13-337.4: Warning (unit_address_vs_reg): /usb_slot@1: node has a unit name, but no reg or ranges property ds918p_16ports.dts:339.13-352.4: Warning (unit_address_vs_reg): /usb_slot@2: node has a unit name, but no reg or ranges property ds918p_16ports.dts:354.14-357.4: Warning (unit_address_vs_reg): /nvme_slot@1: node has a unit name, but no reg or ranges property ds918p_16ports.dts:359.14-362.4: Warning (unit_address_vs_reg): /nvme_slot@2: node has a unit name, but no reg or ranges property cp: can't stat 'model.dtb': No such file or directory 'model_ds918p_42218.dtb' -> '/etc.defaults/model.dtb' 'model_ds918p_42218.dtb' -> '/var/run/model.dtb' Ran "install_rd.sh" for jumkey.qjs.dtb->on_boot - exit=0 Running "check-e1000e.sh" for pocopico.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for pocopico.e1000e->on_boot - exit=0 Running "check-igb.sh" for pocopico.igb->on_boot Loading module igb -> Module igb loaded succesfully Ran "check-igb.sh" for pocopico.igb->on_boot - exit=0 Running "install_rd.sh" for redpill-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Still waiting for boot device (waited 3 of 30 seconds) Still waiting for boot device (waited 4 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0 :: Executing "on_boot" custom scripts ... [ OK ] Extensions processed Insert net driver(Mindspeed only)... Starting /usr/syno/bin/synocfgen... /usr/syno/bin/synocfgen returns 0 Insert synorbd kernel module Insert synofsbd kernel module Insert sha256 kernel module Assemble args: -u 6a218281:5374c81b:05d949f7:b0bbaec7 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdh1 /dev/sdi1 /dev/sdj1 /dev/sdm1 /dev/sdn1 mdadm: /dev/sdg1 has wrong uuid. mdadm: /dev/sdh1 has wrong uuid. mdadm: ignoring /dev/sda1 as it reports /dev/sdc1 as failed mdadm: /dev/md0 has been started with 2 drives (out of 16). Partition Version=8 /sbin/e2fsck exists, checking /dev/md0... e2fsck 1.44.1 (24-Mar-2018) /sbin/e2fsck -yvf returns 0 Mounting /dev/md0 /tmpRoot ------------upgrade Begin upgrade procedure Failed to found any patch No upgrade file found ============upgrade ------------bootup-smallupdate Failed to AssertFileKeyValueEqual value1: /etc.defaults/synoinfo.conf:unique -> synology_apollolake_918+ value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_v1000_1621+ Skip bootup smallupdate, because root is not matched to junior ============bootup-smallupdate Exit on error [2] .noroot exists... Fri Jun 24 14:01:04 UTC 2022 /dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 DS918+ /SYS/BLOCK in junior (Reveal hidden contents) DiskStation> ll /sys/block drwxr-xr-x 2 root root 0 Jun 24 14:01 . dr-xr-xr-x 12 root root 0 Jun 24 14:01 .. lrwxrwxrwx 1 root root 0 Jun 24 14:01 md0 -> ../devices/virtual/block/md0 lrwxrwxrwx 1 root root 0 Jun 24 14:01 md1 -> ../devices/virtual/block/md1 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram0 -> ../devices/virtual/block/ram0 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram1 -> ../devices/virtual/block/ram1 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram10 -> ../devices/virtual/block/ram10 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram11 -> ../devices/virtual/block/ram11 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram12 -> ../devices/virtual/block/ram12 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram13 -> ../devices/virtual/block/ram13 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram14 -> ../devices/virtual/block/ram14 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram15 -> ../devices/virtual/block/ram15 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram2 -> ../devices/virtual/block/ram2 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram3 -> ../devices/virtual/block/ram3 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram4 -> ../devices/virtual/block/ram4 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram5 -> ../devices/virtual/block/ram5 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram6 -> ../devices/virtual/block/ram6 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram7 -> ../devices/virtual/block/ram7 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram8 -> ../devices/virtual/block/ram8 lrwxrwxrwx 1 root root 0 Jun 24 14:02 ram9 -> ../devices/virtual/block/ram9 lrwxrwxrwx 1 root root 0 Jun 24 14:01 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdc lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdd -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd lrwxrwxrwx 1 root root 0 Jun 24 14:01 sde -> ../devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sde lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdf -> ../devices/pci0000:00/0000:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sdf lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdg -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sdg lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdh -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata8/host7/target7:0:0/7:0:0:0/block/sdh lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdi -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata9/host8/target8:0:0/8:0:0:0/block/sdi lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdj -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sdj lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdm -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/ata13/host12/target12:0:0/12:0:0:0/block/sdm lrwxrwxrwx 1 root root 0 Jun 24 14:01 sdn -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/ata14/host13/target13:0:0/13:0:0:0/block/sdn lrwxrwxrwx 1 root root 0 Jun 24 14:02 synoboot -> ../devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/host14/target14:0:0/14:0:0:0/block/synoboot DS920+ /SYS/BLOCK in junior (Reveal hidden contents) lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata1 -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sata1 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata10 -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata10/host9/target9:0:0/9:0:0:0/block/sata10 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata11 -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/ata13/host12/target12:0:0/12:0:0:0/block/sata11 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata12 -> ../devices/pci0000:00/0000:00:01.1/0000:02:00.0/ata14/host13/target13:0:0/13:0:0:0/block/sata12 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata2 -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sata2 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata3 -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sata3 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata4 -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sata4 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata5 -> ../devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sata5 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata6 -> ../devices/pci0000:00/0000:00:1f.2/ata6/host5/target5:0:0/5:0:0:0/block/sata6 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata7 -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sata7 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata8 -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata8/host7/target7:0:0/7:0:0:0/block/sata8 lrwxrwxrwx 1 root root 0 Jun 24 12:21 sata9 -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/ata9/host8/target8:0:0/8:0:0:0/block/sata9 I never thought dtb would work on 918😅 jumkey.qjs.000 added 918 because I want to be able to use quickjs on this platform 1 Quote Link to comment Share on other sites More sharing options...
igbs Posted June 24, 2022 Share #165 Posted June 24, 2022 6 hours ago, Peter Suh said: X520 10Gb PCIe is probably dual port, When used with igb ext , there was a problem of conflict. I'm not sure if this part is completely resolved or not. How to use ixgbe ext without conflict for current X520 10Gb dual NIC you are using DS3622xs+. DS3622xs+ already includes the vanilla version of ixgbe, so if pocopico's ext is duplicated, an error will also occur. So, how to safely use ext in X520 10Gb dual NIC is as follows. Build DS3622xs+ loader without plugging X520 10Gb into PC X520 10Gb is to plug in later. https://github.com/pocopico/rp-ext/issues/103 My X520 10Gb PCIe is singe port ... "So, how to safely use ext in X520 10Gb dual NIC is as follows. Build DS3622xs+ loader without plugging X520 10Gb into PC X520 10Gb is to plug in later." - Yes I read this.. Thanks.. Quote Link to comment Share on other sites More sharing options...
igbs Posted June 25, 2022 Share #166 Posted June 25, 2022 15 hours ago, Peter Suh said: To do so, proceed as follows. ./rploader.sh clean ./rploader.sh ext geminilake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/igb/rpext-index.json ./my.sh DS920+ manual or ./rploader.sh clean ./rploader.sh ext geminilake-7.0.1-42218-JUN add https://raw.githubusercontent.com/pocopico/rp-ext/master/igb/rpext-index.json ./my.sh DS920+J jumkey manual Big THANKS Master Suh! I connected 4 drives and heve tried first option and ... Successful install DS920+ 7.1.. but the Storage Manager can see only 2 HDD of 4 I can see all 4 drives from the terminal: Spoiler lrwxrwxrwx 1 root root 0 Jun 24 22:32 dm-0 -> ../devices/virtual/block/dm-0 lrwxrwxrwx 1 root root 0 Jun 24 22:32 dm-1 -> ../devices/virtual/block/dm-1 lrwxrwxrwx 1 root root 0 Jun 24 22:31 dm-2 -> ../devices/virtual/block/dm-2 lrwxrwxrwx 1 root root 0 Jun 24 22:32 loop0 -> ../devices/virtual/block/loop0 lrwxrwxrwx 1 root root 0 Jun 24 22:32 loop1 -> ../devices/virtual/block/loop1 lrwxrwxrwx 1 root root 0 Jun 24 22:32 loop2 -> ../devices/virtual/block/loop2 lrwxrwxrwx 1 root root 0 Jun 24 22:32 loop3 -> ../devices/virtual/block/loop3 lrwxrwxrwx 1 root root 0 Jun 24 22:32 loop4 -> ../devices/virtual/block/loop4 lrwxrwxrwx 1 root root 0 Jun 24 22:32 loop5 -> ../devices/virtual/block/loop5 lrwxrwxrwx 1 root root 0 Jun 24 22:32 loop6 -> ../devices/virtual/block/loop6 lrwxrwxrwx 1 root root 0 Jun 24 22:32 loop7 -> ../devices/virtual/block/loop7 lrwxrwxrwx 1 root root 0 Jun 24 22:31 md0 -> ../devices/virtual/block/md0 lrwxrwxrwx 1 root root 0 Jun 24 22:31 md1 -> ../devices/virtual/block/md1 lrwxrwxrwx 1 root root 0 Jun 24 22:31 md2 -> ../devices/virtual/block/md2 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram0 -> ../devices/virtual/block/ram0 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram1 -> ../devices/virtual/block/ram1 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram10 -> ../devices/virtual/block/ram10 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram11 -> ../devices/virtual/block/ram11 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram12 -> ../devices/virtual/block/ram12 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram13 -> ../devices/virtual/block/ram13 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram14 -> ../devices/virtual/block/ram14 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram15 -> ../devices/virtual/block/ram15 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram2 -> ../devices/virtual/block/ram2 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram3 -> ../devices/virtual/block/ram3 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram4 -> ../devices/virtual/block/ram4 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram5 -> ../devices/virtual/block/ram5 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram6 -> ../devices/virtual/block/ram6 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram7 -> ../devices/virtual/block/ram7 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram8 -> ../devices/virtual/block/ram8 lrwxrwxrwx 1 root root 0 Jun 24 22:32 ram9 -> ../devices/virtual/block/ram9 lrwxrwxrwx 1 root root 0 Jun 24 22:31 sata1 -> ../devices/pci0000:00/0000:00:13.0/ata5/host4/target4:0:0/4:0:0:0/block/sata1 lrwxrwxrwx 1 root root 0 Jun 24 22:31 sata2 -> ../devices/pci0000:00/0000:00:13.0/ata6/host5/target5:0:0/5:0:0:0/block/sata2 lrwxrwxrwx 1 root root 0 Jun 24 22:31 sata3 -> ../devices/pci0000:00/0000:00:13.0/ata7/host6/target6:0:0/6:0:0:0/block/sata3 lrwxrwxrwx 1 root root 0 Jun 24 22:31 sata4 -> ../devices/pci0000:00/0000:00:13.0/ata8/host7/target7:0:0/7:0:0:0/block/sata4 lrwxrwxrwx 1 root root 0 Jun 24 22:31 synoboot -> ../devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1:1.0/host8/target8:0:0/8:0:0:0/block/synoboot lrwxrwxrwx 1 root root 0 Jun 24 22:31 zram0 -> ../devices/virtual/block/zram0 lrwxrwxrwx 1 root root 0 Jun 24 22:31 zram1 -> ../devices/virtual/block/zram1 lrwxrwxrwx 1 root root 0 Jun 24 22:31 zram2 -> ../devices/virtual/block/zram2 lrwxrwxrwx 1 root root 0 Jun 24 22:31 zram3 -> ../devices/virtual/block/zram3 Spoiler Disk /dev/sata1: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: WD20EFRX-68AX9N0 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xbcac8680 Device Boot Start End Sectors Size Id Type /dev/sata1p1 8192 16785407 16777216 8G fd Linux raid autodetect /dev/sata1p2 16785408 20979711 4194304 2G fd Linux raid autodetect /dev/sata1p3 21241856 3906824351 3885582496 1.8T fd Linux raid autodetect Disk /dev/sata1p1: 8 GiB, 8589934592 bytes, 16777216 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sata1p2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sata1p3: 1.8 TiB, 1989418237952 bytes, 3885582496 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sata2: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: WD20EFAX-68FB5N0 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xdd709823 Device Boot Start End Sectors Size Id Type /dev/sata2p1 8192 16785407 16777216 8G fd Linux raid autodetect /dev/sata2p2 16785408 20979711 4194304 2G fd Linux raid autodetect /dev/sata2p3 21241856 3906824351 3885582496 1.8T fd Linux raid autodetect Disk /dev/sata2p1: 8 GiB, 8589934592 bytes, 16777216 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sata2p2: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sata2p3: 1.8 TiB, 1989418237952 bytes, 3885582496 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sata3: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: ST2000VN004-2E4164 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x031c70b6 Disk /dev/sata4: 55.9 GiB, 60022480896 bytes, 117231408 sectors Disk model: AGILITY3 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x1e0faea9 Device Boot Start End Sectors Size Id Type /dev/sata4p1 2048 117226304 117224257 55.9G fd Linux raid autodetect Disk /dev/sata4p1: 55.9 GiB, 60018819584 bytes, 117224257 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes ... any idea how to fix it? Should I use the second option - dynamic disk tree? Thanks again.. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 25, 2022 Share #167 Posted June 25, 2022 (edited) TC now extends the DTC support model to the full model. 5 Models Known as Non-DTC Supported Models Also on DS918+, DS3615xs, DS3617xs, DS3622xs+, DVA3221 When only the model.dtb file is copied to the /etc.defaults/ and /var/run/ directories, The sataport starts working in the device tree. in the user_config.json file SataPortMap and DiskIdxMap options work with DTC. It may cause side effects. So, M shell replaces the empty values of SataPortMap = "", DiskIdxMap = "". As it is currently implemented as a unique function of the M shell, It is not possible to build using only the existing rploader.sh. before use, Please update to the latest version by executing only ./my.sh Build options for the above 5 models are listed below. [JOT Mode] ./my.sh DS918+ poco [JUN Mode] ./my.sh DS918+J poco Since @jumkey did not modify quick js for dynamic dtc patch for the above 5 models, the jumkey option is not available yet. The poco option must be used for pocopico's static dtc patch function to work. Currently, two models, DS918+ and DS3622xs+, have been tested on baremetal. All DTC models supported by M shell support up to 16 SATA disks. HBA card is recognized and operated separately regardless of SataPortMap or DTC's dtb file. DS920+ and DS1621+ appear to have broken mpt3sas ext. @pocopico I need your help. Edited June 25, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
maxime Posted June 25, 2022 Share #168 Posted June 25, 2022 On 6/22/2022 at 6:36 PM, Peter Suh said: The DS920+ recommended 4 ports As Dolbycat tested, there is no problem with operation even if you increase it to six. I increased the maximum to 16 and changed it to be available. So, on dtc DS920(4 port)+, DS1621+(6 port) Jun mode, If you use the dynamic dtb mapping feature with the jumkey option, we have implemented it to extend to 16 ports so that automatic mapping is recognized. "Jumkey.qjs.dtb" ext has been modified a little to force the use of the dtb file for 16 ports. If you want to use the dts file manually, you can download it by referring to my GitHub. https://github.com/PeterSuh-Q3/tinycore-redpill After downloading and installing as shown below, Build the load again curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" --output my.sh.gz; tar -zxvf my.sh.gz; ./my.sh DS920+J jumkey noclean ./my.sh DS1621+J jumkey noclean Use the ll command to check if the model.dtb file is in the list ll /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds920p_42218 ll /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds1621p_42218 If you check once again whether the script (spoiler) below looks like the one I modified with the cat command, it will definitely be applied. cat /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds920p_42218/install_rd.sh cat /home/tc/redpill-load/custom/extensions/jumkey.qjs.dtb/ds1621p_42218/install_rd.sh install_rd.sh (Reveal hidden contents) #!/bin/sh tar -zxvf patch.tar.gz # install dtc chmod +x dtc cp dtc /usr/sbin/dtc # copy 16 ports dts file to /etc.defaults #echo $PLATFORM_ID if [ "${PLATFORM_ID}" = "ds920p_42218" ]; then echo "copy DS920+'s 16 ports ds920p_16ports.dts to /etc.defaults" ./dtc -I dts -O dtb -o model.dtb ds920p_16ports.dts cp -vf model.dtb /etc.defaults/model.dtb elif [ "${PLATFORM_ID}" = "ds1621p_42218" ]; then echo "copy DS1621+'s 16 ports ds1621p_16ports.dts to /etc.defaults" ./dtc -I dts -O dtb -o model.dtb ds1621p_16ports.dts cp -vf model.dtb /etc.defaults/model.dtb fi # copy file if [ ! -f model_${PLATFORM_ID%%_*}.dtb ]; then # Dynamic generation ./dtc -I dtb -O dts -o output.dts /etc.defaults/model.dtb qjs --std ./dts.js output.dts output.dts.out if [ $? -ne 0 ]; then echo "auto generated dts file is broken" exit 0 fi ./dtc -I dts -O dtb -o model_r2.dtb output.dts.out cp -vf model_r2.dtb /etc.defaults/model.dtb cp -vf model_r2.dtb /var/run/model.dtb else cp -vf model_${PLATFORM_ID%%_*}.dtb /etc.defaults/model.dtb cp -vf model_${PLATFORM_ID%%_*}.dtb /var/run/model.dtb fi I've installed up to 14 discs. 6 built-in sata I used the following product, external 8 ports (Marvel 88SE9215 chip 4 ports + ASM1166 chip 2 ports [unrecognized]) X2. https://ko.aliexpress.com/item/33016481933.html 8 disks on a single pci-ex 1x slot? Aren't they too slow? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 25, 2022 Share #169 Posted June 25, 2022 27 minutes ago, maxime said: 8 disks on a single pci-ex 1x slot? Aren't they too slow? DTC is applied to the entire model of TC, which has just been completed by concentrating energy. I haven't tested the speed part. Even with 1x PCI-E, I know that there is no problem with SATA disks that are slower than this. If you want to increase speed, you can use RAID. Quote Link to comment Share on other sites More sharing options...
phone guy Posted June 25, 2022 Share #170 Posted June 25, 2022 Wait, I am confused, what is JOT mode? is that different than what we're talking about here as JUN mode? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 26, 2022 Share #171 Posted June 26, 2022 Wait, I am confused, what is JOT mode? is that different than what we're talking about here as JUN mode?It refers to the existing method that we knew before Jumkey's jun mode came out. It was named so in Flyride's new TC guide.Sent from my iPhone using Tapatalk Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 27, 2022 Share #172 Posted June 27, 2022 (edited) @jumkey I used TC to test the jun mode build for DS2422+, but the following error occurred. Can you check? sudo BRP_JUN_MOD=1 BRP_DEBUG=0 BRP_USER_CFG=user_config.json ./build-loader.sh DS2422+ 7.0.1-42218 loader.img Edited June 27, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
jumkey Posted June 27, 2022 Author Share #173 Posted June 27, 2022 1 hour ago, Peter Suh said: @jumkey I used TC to test the jun mode build for DS2422+, but the following error occurred. Can you check? sudo BRP_JUN_MOD=1 BRP_DEBUG=0 BRP_USER_CFG=user_config.json ./build-loader.sh DS2422+ 7.0.1-42218 loader.img I tested it and it's fine ./ext-manager.sh add https://github.com/jumkey/redpill-load/raw/develop/redpill-runtime-qjs/rpext-index.json ./ext-manager.sh add https://github.com/jumkey/redpill-load/raw/develop/redpill-qjs-dtb/rpext-index.json BRP_JUN_MOD=1 BRP_DEBUG=0 BRP_USER_CFG=user_config-ds2422.json ./build-loader.sh DS2422+ 7.0.1-42218 loader.img Quote Link to comment Share on other sites More sharing options...
apriliars3 Posted June 27, 2022 Share #174 Posted June 27, 2022 I have tested with DS2422+ but have issue with extensions [-] The extension pocopico.r8169 was found. However, the extension index has no recipe for ds2422p_42218 platform. It may not be [-] supported on that platform, or author didn't updated it for that platform yet. You can try running [-] "ext-manager.sh update" to refresh indexes for all extensions manually. Below are the currently known information about [-] the extension stored locally: [-] Failed to update recipe for pocopico.r8169 extension for platform ds2422p_42218. The script will terminate as you do not [-] have previously downloaded recipe which can be used if download fails. Try again later. If problem [-] persists contact the extension packer for support (displayed below) [!] Cannot continue due to previous errors (see above) *** Process will exit *** [!] Failed to update all extensions for ds2422p_42218 platform - see errors above *** Process will exit *** FAILED : Loader creation failed check the output for any errors Is it possible to use yet DS2422+ now? error ds2422+.txt Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted June 28, 2022 Share #175 Posted June 28, 2022 @jumkey, @apriliars3 Thanks again for testing my request. As jumkey said, when using build-loader.sh with DS2422+ in jun mode, I also double-checked that there are no issues. Since the DS2422+ is the same v1000 platform as the DS1621+, I am looking for a way for both models to share the v1000 ext within the ext and TCRP of @pocopico. Because all pocopico exts are statically managed by each synology model. Adding all the DS2422+ seems like a very daunting task. (I'm not sure if there is a tool that pocopico can easily register as a batch job.^^) I'll experiment further so both models can share v1000 ext without pocopico's work. thank you Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.