pocopico Posted April 16, 2022 Author Share #2626 Posted April 16, 2022 (edited) 2 minutes ago, Peter Suh said: Below is the result of logging as you told me. SynologyNAS> cat /sys/block/sata1/device/syno_block_info pciepath=00:1f.2 ata_port_no=0 driver=ahci And that's what the rploader found automatically ------------------------ internal_slot@1 { protocol_type = "sata"; power_pin_gpio = <0x14 0x0>; detect_pin_gpio = <0x23 0x1>; led_type = "lp3943"; ahci { pcie_root = "00:1f.2,"; ata_port = <0x0>; }; led_green { led_name = "syno_led0"; }; led_orange { led_name = "syno_led1"; }; }; ------------------------- I don't think there's a problem with this part It looks OK, i dont know why its not working. Is your /etc/model.dtb and etc.defaults/model.dtb the one you've modified ? Edited April 16, 2022 by pocopico Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2627 Posted April 16, 2022 2 minutes ago, pocopico said: It looks OK, i dont know why its not working. Is your /etc/model.dtb and etc.defaults/model.dtb the one you've modified ? I already finished checking as below. However, as shown in the attached image, 1f.2 is followed by a , Is there no problem with this? ------------------------------------------------- [Tinycore] SynologyNAS> cat /var/run/model.dtb 6,( Synology synology_geminilake_920+ + CtrueXfshDX517 Synology synology_dx517pmp_slot@1libatapmp_slot@2libatapmp_slot@3libatapmp_slot@4libatapmp_slot@5libatainternal_slot@1sa#lp3943ahci 00:1f.2,led_green syno_led0led_orange 00:13.0,00.0led_greent@2sa$lp3943ahci syno_led2led_orange syno_led3internal_slot@3sa%lp3943ahc00:12.0led_green syno_led4led_orange syno_led5internal_slot@4sa&lp3943ahc00:12.0led_green syno_led6led_orange 00:13.0,00.0usb_slot@1vbuusb21-1usb32-1usb_slot@2vbuusb21-2usb32-2nvme_slot@00:14.1 ssdcachenvme_slot@00:14.0 ssdcache compatiblemodelversionsyno_spinup_groupsyno_spinup_group_delaysyno_hdd_powerup_seqsyno_cmos_reg_secure_flashsyno_cmos_reg_secure_bootEMIDpmp_linkprotocol_typepower_pin_gpiodetect_pin_gpioled_typepcie_rootata_portled_namesyno_gpiousb_portport_typeSynologyNAS> Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2628 Posted April 16, 2022 (edited) 2 minutes ago, Peter Suh said: I already finished checking as below. However, as shown in the attached image, 1f.2 is followed by a , Is there no problem with this? ------------------------------------------------- [Tinycore] SynologyNAS> cat /var/run/model.dtb 6,( Synology synology_geminilake_920+ + CtrueXfshDX517 Synology synology_dx517pmp_slot@1libatapmp_slot@2libatapmp_slot@3libatapmp_slot@4libatapmp_slot@5libatainternal_slot@1sa#lp3943ahci 00:1f.2,led_green syno_led0led_orange 00:13.0,00.0led_greent@2sa$lp3943ahci syno_led2led_orange syno_led3internal_slot@3sa%lp3943ahc00:12.0led_green syno_led4led_orange syno_led5internal_slot@4sa&lp3943ahc00:12.0led_green syno_led6led_orange 00:13.0,00.0usb_slot@1vbuusb21-1usb32-1usb_slot@2vbuusb21-2usb32-2nvme_slot@00:14.1 ssdcachenvme_slot@00:14.0 ssdcache compatiblemodelversionsyno_spinup_groupsyno_spinup_group_delaysyno_hdd_powerup_seqsyno_cmos_reg_secure_flashsyno_cmos_reg_secure_bootEMIDpmp_linkprotocol_typepower_pin_gpiodetect_pin_gpioled_typepcie_rootata_portled_namesyno_gpiousb_portport_typeSynologyNAS> If you've usb jumkeys redpill-dtb, the dtc binary should be copied to your DSM so you can also read it using the dtc binary. Yes i think the "," is a problem .... i need to see that can you please run the following from TCRP ? udevadm info --query path --name sdx udevadm info --query path --name sdx | awk -F "\/" '{print $4 ":" $5 }' | awk -F ":" '{print $2 ":" $3 "," $6}' Edited April 16, 2022 by pocopico Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2629 Posted April 16, 2022 3 minutes ago, pocopico said: If you've usb jumkeys redpill-dtb, the dtc binary should be copied to your DSM so you can also read it using the dtc binary. Yes i think the "," is a problem .... i need to see that can you please run the following from TCRP ? udevadm info --query path --name sdx udevadm info --query path --name sdx | awk -F "\/" '{print $4 ":" $5 }' | awk -F ":" '{print $2 ":" $3 "," $6}' tc@box:~$ udevadm info --query path --name sda /devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda tc@box:~$ udevadm info --query path --name sda | awk -F "\/" '{print $4 ":" $5 }' | awk -F ":" '{print $2 ": " $3 "," $6}' 00:1f.2, Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2630 Posted April 16, 2022 Just now, Peter Suh said: tc@box:~$ udevadm info --query path --name sda /devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda tc@box:~$ udevadm info --query path --name sda | awk -F "\/" '{print $4 ":" $5 }' | awk -F ":" '{print $2 ": " $3 "," $6}' 00:1f.2, Yes the output is not right, i need to fix the logic in patchdtc function. Your pci device does not require a comma. Remove it from your dts and rebuild loader. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2631 Posted April 16, 2022 Just now, pocopico said: Yes the output is not right, i need to fix the logic in patchdtc function. Your pci device does not require a comma. Remove it from your dts and rebuild loader. I've already built it and I think the results will come out soon. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2632 Posted April 16, 2022 6 minutes ago, Peter Suh said: I've already built it and I think the results will come out soon. YES !!!! I finally succeeded. I definitely changed the dts of port number one, but I still can't get rid of the ' I tried moving the HDD to port number 2 that looks like the contents below. Then the conclusion was recognized. Thank you, Pocopico ^^ SynologyNAS> cat /var/run/model.dtb 8 ( Synology synology_geminilake_920+ + CtrueXfshDX517 Synology synology_dx517pmp_slot@1libatapmp_slot@2libatapmp_slot@3libatapmp_slot@4libatapmp_slot@5libatainternal_slot@1sa#lp3943ahci 00:1f.2,led_green syno_led0led_orange syno_led1internal_slot@2sa$lp3943ahc00:1f.2led_green syno_led2led_orange syno_led3internal_slot@3sa%lp3943ahc00:1f.2led_green syno_led4led_orange syno_led5internal_slot@4sa&lp3943ahc00:1f.2led_green syno_led6led_orange syno_led7internal_slot@5sa'lp3943ahc00:1f.2led_green syno_led8led_orange syno_led9internal_slot@6sa(lp3943ahc00:1f.2led_green syno_led10led_orange 00:13.0,00.0usb_slot@1vbuusb23-5usb32-1usb_slot@2vbuusb21-2usb32-2nvme_slot@00:14.1sata_ssdcachenvme_slot@00:14.0 ssdcache compatiblemodelversionsyno_spinup_groupsyno_spinup_group_delaysyno_hdd_powerup_seqsyno_cmos_reg_secure_flashsyno_cmos_reg_secure_bootEMIDpmp_linkprotocol_typepower_pin_gpiodetect_pin_gpioled_typepcie_rootata_portled_namesyno_gpiousb_portport_typeSynologyNAS> 1 Quote Link to comment Share on other sites More sharing options...
Bose321 Posted April 16, 2022 Share #2633 Posted April 16, 2022 Can someone help me with disk mapping? I now have index 00 and map to 6. I've got one virtual disk in Qemu and the loader as USB. When I do fdisk -l in DSM I get this: DiskStation> fdisk -l Disk /dev/sdd: 200 GB, 214748364800 bytes, 419430400 sectors 26108 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdd1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sdd2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors 622544 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors 524272 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md1 doesn't contain a valid partition table The 200GB /dev/sdd in this case is the right disk. I assumed it would be 00 and 1, but that doesn't work. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2634 Posted April 16, 2022 9 minutes ago, Peter Suh said: YES !!!! I finally succeeded. I definitely changed the dts of port number one, but I still can't get rid of the ' I tried moving the HDD to port number 2 that looks like the contents below. Then the conclusion was recognized. Thank you, Pocopico ^^ SynologyNAS> cat /var/run/model.dtb 8 ( Synology synology_geminilake_920+ + CtrueXfshDX517 Synology synology_dx517pmp_slot@1libatapmp_slot@2libatapmp_slot@3libatapmp_slot@4libatapmp_slot@5libatainternal_slot@1sa#lp3943ahci 00:1f.2,led_green syno_led0led_orange syno_led1internal_slot@2sa$lp3943ahc00:1f.2led_green syno_led2led_orange syno_led3internal_slot@3sa%lp3943ahc00:1f.2led_green syno_led4led_orange syno_led5internal_slot@4sa&lp3943ahc00:1f.2led_green syno_led6led_orange syno_led7internal_slot@5sa'lp3943ahc00:1f.2led_green syno_led8led_orange syno_led9internal_slot@6sa(lp3943ahc00:1f.2led_green syno_led10led_orange 00:13.0,00.0usb_slot@1vbuusb23-5usb32-1usb_slot@2vbuusb21-2usb32-2nvme_slot@00:14.1sata_ssdcachenvme_slot@00:14.0 ssdcache compatiblemodelversionsyno_spinup_groupsyno_spinup_group_delaysyno_hdd_powerup_seqsyno_cmos_reg_secure_flashsyno_cmos_reg_secure_bootEMIDpmp_linkprotocol_typepower_pin_gpiodetect_pin_gpioled_typepcie_rootata_portled_namesyno_gpiousb_portport_typeSynologyNAS> This is the last successful log. 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 "e1000e.ko" for PeterSuh-Q3.e1000e (args: ) Loading kmod #0 "igb.ko" for PeterSuh-Q3.igb (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot - exit=0 Running "check-igb.sh" for PeterSuh-Q3.igb->on_boot Loading module igb -> Module igb loaded succesfully Ran "check-igb.sh" for PeterSuh-Q3.igb->on_boot - exit=0 Running "install_rd.sh" for jumkey.misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for jumkey.misc->on_boot - exit=0 Running "boot-wait.sh" for redpill-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) Still waiting for boot device (waited 5 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0 Running "install_rd.sh" for redpill-dtb->on_boot 'model_ds920p.dtb' -> '/etc.defaults/model.dtb' 'model_ds920p.dtb' -> '/var/run/model.dtb' Ran "install_rd.sh" for redpill-dtb->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 Assemble args: -u cacc41ce:446846f1:05d949f7:b0bbaec7 /dev/sata1p1 mdadm: /dev/md0 has been started with 1 drive (out of 16). Partition Version=9 /sbin/e2fsck exists, checking /dev/md0... e2fsck 1.44.1 (24-Mar-2018) /sbin/e2fsck -yvf returns 0 Mounting /dev/md0 /tmpRoot mount: mounting /dev/md0 on /tmpRoot failed: Invalid argument mount /dev/md0 fail, returns Exit on error [3] no init exists... Sat Apr 16 12:35:24 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 Quote Link to comment Share on other sites More sharing options...
Bose321 Posted April 16, 2022 Share #2635 Posted April 16, 2022 (edited) 1 hour ago, Bose321 said: Can someone help me with disk mapping? I now have index 00 and map to 6. I've got one virtual disk in Qemu and the loader as USB. When I do fdisk -l in DSM I get this: DiskStation> fdisk -l Disk /dev/sdd: 200 GB, 214748364800 bytes, 419430400 sectors 26108 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdd1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect /dev/sdd2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors 622544 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors 524272 cylinders, 2 heads, 4 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/md1 doesn't contain a valid partition table The 200GB /dev/sdd in this case is the right disk. I assumed it would be 00 and 1, but that doesn't work. Booting as SATA now for the loader, and using 01 and 6, that boots and installs, but it keeps saying I've changed disks and wants to restore/migrate in an endless loop. This is with 02 and 6: DiskStation> fdisk -l Disk /dev/synoboot: 1024 MB, 1073741824 bytes, 2097152 sectors 130 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/synoboot1 * 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux /dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux /dev/synoboot3 15,205,63 130,138,8 253952 2097151 1843200 900M 83 Linux Disk /dev/sdd: 200 GB, 214748364800 bytes, 419430400 sectors 26108 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/sdd doesn't contain a valid partition table During installation it says data on 4 disks will be erased, but I can't find the right index... And this is my Unraid Qemu setup for disks <disk type='file' device='disk'> <driver name='qemu' type='vmdk' cache='writeback'/> <source file='/mnt/user/domains/dsm/tinycore-redpill.v0.4.6.vmdk' index='2'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/dsm/vdisk2.img' index='1'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> Edited April 16, 2022 by Bose321 Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2636 Posted April 16, 2022 52 minutes ago, Peter Suh said: This is the last successful log. 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 "e1000e.ko" for PeterSuh-Q3.e1000e (args: ) Loading kmod #0 "igb.ko" for PeterSuh-Q3.igb (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot Loading module e1000e -> Module e1000e loaded succesfully Ran "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot - exit=0 Running "check-igb.sh" for PeterSuh-Q3.igb->on_boot Loading module igb -> Module igb loaded succesfully Ran "check-igb.sh" for PeterSuh-Q3.igb->on_boot - exit=0 Running "install_rd.sh" for jumkey.misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for jumkey.misc->on_boot - exit=0 Running "boot-wait.sh" for redpill-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) Still waiting for boot device (waited 5 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0 Running "install_rd.sh" for redpill-dtb->on_boot 'model_ds920p.dtb' -> '/etc.defaults/model.dtb' 'model_ds920p.dtb' -> '/var/run/model.dtb' Ran "install_rd.sh" for redpill-dtb->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 Assemble args: -u cacc41ce:446846f1:05d949f7:b0bbaec7 /dev/sata1p1 mdadm: /dev/md0 has been started with 1 drive (out of 16). Partition Version=9 /sbin/e2fsck exists, checking /dev/md0... e2fsck 1.44.1 (24-Mar-2018) /sbin/e2fsck -yvf returns 0 Mounting /dev/md0 /tmpRoot mount: mounting /dev/md0 on /tmpRoot failed: Invalid argument mount /dev/md0 fail, returns Exit on error [3] no init exists... Sat Apr 16 12:35:24 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 Can you try to build again ? the dtc patching process has been enhanced to include the loader usb patch and remove the trailing comma Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2637 Posted April 16, 2022 (edited) 46 minutes ago, pocopico said: Can you try to build again ? the dtc patching process has been enhanced to include the loader usb patch and remove the trailing comma Rploader re-build to version 0.7.0.2 and all problems are gone. I am currently struggling with the problem of stopping at 55 percent of dsm installations. After cleaning the disc, I will try again. Anyway, I'm going to continue with the TSU of ds920+. As soon as your ds920p-42218 is restored, I will proceed with it. Please give me feedback when it is restored. I will take the TSU test as soon as I get feedback tomorrow. Edited April 16, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2638 Posted April 16, 2022 16 minutes ago, Peter Suh said: Rploader re-build to version 0.7.0.2 and all problems are gone. I am currently struggling with the problem of stopping at 55 percent of dsm installations. After cleaning the disc, I will try again. Anyway, I'm going to continue with the TSU of ds920+. As soon as your ds920p-42218 is restored, I will proceed with it. Please give me feedback when it is restored. I will take the TSU test as soon as I get feedback tomorrow. I've added 42218 although i dont know if it anyone will ever build a ds920p 7.0.1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2639 Posted April 16, 2022 1 minute ago, pocopico said: I've added 42218 although i dont know if it anyone will ever build a ds920p 7.0.1 Isn't TSU necessary to make a loader for 7.1? Can I just build 7.1 from scratch? Because of TSU, I had no choice but to continue building 7.0.1 Have I been wrong all this time? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2640 Posted April 16, 2022 34 minutes ago, pocopico said: I've added 42218 although i dont know if it anyone will ever build a ds920p 7.0.1 I'll ask you one last place. There is no ds920p-42218 here either. https://github.com/pocopico/redpill-load/blob/master/redpill-misc/rpext-index.json Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2641 Posted April 16, 2022 49 minutes ago, Peter Suh said: Isn't TSU necessary to make a loader for 7.1? Can I just build 7.1 from scratch? Because of TSU, I had no choice but to continue building 7.0.1 Have I been wrong all this time? you can build the 7.1 loader from scratch Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2642 Posted April 16, 2022 3 minutes ago, pocopico said: you can build the 7.1 loader from scratch Oh, I need to rewrite the new guide for 7.1. ㅜㅜ And, there is an error in the dtc patch function. I tried making test.sh as below. The fifth usbvid is taking the pid #!/bin/sh loaderdisk=$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3) localdisks=$(lsblk | grep -i disk | grep -i sd | awk '{print $1}' | grep -v $loaderdisk) localnvme=$(lsblk | grep -i nvme | awk '{print $1}') usbpid=$(cat user_config.json | jq '.extra_cmdline .pid' | sed -e 's/"//g' | sed -e 's/0x//g') usbvid=$(cat user_config.json | jq '.extra_cmdline .pid' | sed -e 's/"//g' | sed -e 's/0x//g') loaderusb=$(lsusb | grep "${usbvid}:${usbpid}" | awk '{print $2 "-" $4 }' | sed -e 's/://g' | sed -s 's/00//g') echo loaderdisk: $loaderdisk echo localdisks: $localdisks echo localnvme: $localnvme echo usbpid: $usbpid echo usbvid: $usbvid echo loaderusb: $loaderusb result : tc@box:~$ ./test.sh Protocol spec without prior Class and Subclass spec at line 23281 loaderdisk: sdb localdisks: sda localnvme: usbpid: 5567 usbvid: 5567 loaderusb: Quote Link to comment Share on other sites More sharing options...
TomY Posted April 16, 2022 Share #2643 Posted April 16, 2022 39 minutes ago, pocopico said: you can build the 7.1 loader from scratch Hi, I tried to build it, disks are not detected, still. 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 "e1000.ko" for pocopico.e1000 (args: ) Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-e1000.sh" for pocopico.e1000->on_boot Loading module e1000 -> Module e1000 loaded succesfully Ran "check-e1000.sh" for pocopico.e1000->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 "boot-wait.sh" for redpill-boot-wait->on_boot Still waiting for boot device (waited 1 of 30 seconds) Still waiting for boot device (waited 2 of 30 seconds) Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0 Running "install_rd.sh" for redpill-dtb->on_boot 'model_ds920p.dtb' -> '/etc.defaults/model.dtb' 'model_ds920p.dtb' -> '/var/run/model.dtb' Ran "install_rd.sh" for redpill-dtb->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 :: 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 Exit on error [1] DISK NOT INSTALLED... Sat Apr 16 16:22:20 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 Quote Link to comment Share on other sites More sharing options...
Enigel Posted April 16, 2022 Share #2644 Posted April 16, 2022 I would like to update a baremetal DS918+ from 6.2.3-25426 Update 3 to 7.0.1 but i can't find when to swap the old USB (with Jun's loader) with the new one (RedPill Tinycore). The new USB stick is working, it tested on a PC with same hardware configuration but I don't know the exact steps for migrating to 7.0.1. - DSM version : DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS918+ - Using custom extra.lzma - Hardware: CPU: Intel Core i5-4460 CPU @ 3.20GHz MB: ASUS H97M Plus RAM: 16 GB DISKS: 3X 3TB (Raid 5) Onboard LAN : Intel I218-V Quote Link to comment Share on other sites More sharing options...
rojoone2 Posted April 16, 2022 Share #2645 Posted April 16, 2022 You probably need to change your MAC in the user.config in RPTC to the exact MAC of your JUN's loader config. Did you have a static IP? Quote Link to comment Share on other sites More sharing options...
dolbycat Posted April 16, 2022 Share #2646 Posted April 16, 2022 I succeeded in DS920+ DSM7.1 using TC. Thank you pocopico ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DS920+ now ./rploader.sh satamap now ./rploader.sh identifyusb now ./rploader.sh build geminilake-7.0.1-42218 sudo rm -r /home/tc/redpill-load/custom/extensions/redpill-dtb (Modify the "home/tc/redpill-load/ds920.dts" file for your own system) ./rploader.sh build geminilake-7.1.0-42661 sudo reboot 2 Quote Link to comment Share on other sites More sharing options...
IG-88 Posted April 16, 2022 Share #2647 Posted April 16, 2022 22 hours ago, cferra said: 3622xs+ image also supports high core/thread count - I’m not 100 percent of the amount but I believe it’s 24. @pocopicoor @IG-88 can confirm. yes its the same old for 3615 and 918+ but 3617 got to the same as 3622 as it was raised in kernel version to 4.4 and its 24 threads Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2648 Posted April 16, 2022 (edited) 4 hours ago, Peter Suh said: Oh, I need to rewrite the new guide for 7.1. ㅜㅜ And, there is an error in the dtc patch function. I tried making test.sh as below. The fifth usbvid is taking the pid #!/bin/sh loaderdisk=$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3) localdisks=$(lsblk | grep -i disk | grep -i sd | awk '{print $1}' | grep -v $loaderdisk) localnvme=$(lsblk | grep -i nvme | awk '{print $1}') usbpid=$(cat user_config.json | jq '.extra_cmdline .pid' | sed -e 's/"//g' | sed -e 's/0x//g') usbvid=$(cat user_config.json | jq '.extra_cmdline .pid' | sed -e 's/"//g' | sed -e 's/0x//g') loaderusb=$(lsusb | grep "${usbvid}:${usbpid}" | awk '{print $2 "-" $4 }' | sed -e 's/://g' | sed -s 's/00//g') echo loaderdisk: $loaderdisk echo localdisks: $localdisks echo localnvme: $localnvme echo usbpid: $usbpid echo usbvid: $usbvid echo loaderusb: $loaderusb result : tc@box:~$ ./test.sh Protocol spec without prior Class and Subclass spec at line 23281 loaderdisk: sdb localdisks: sda localnvme: usbpid: 5567 usbvid: 5567 loaderusb: yeah, i thought i've pushed that but evidently i didnt. So now i did. it should be fixed Edited April 16, 2022 by pocopico Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2649 Posted April 16, 2022 1 hour ago, Enigel said: I would like to update a baremetal DS918+ from 6.2.3-25426 Update 3 to 7.0.1 but i can't find when to swap the old USB (with Jun's loader) with the new one (RedPill Tinycore). The new USB stick is working, it tested on a PC with same hardware configuration but I don't know the exact steps for migrating to 7.0.1. - DSM version : DSM 6.2.3-25426 Update 3 - Loader version and model: JUN'S LOADER v1.03b - DS918+ - Using custom extra.lzma - Hardware: CPU: Intel Core i5-4460 CPU @ 3.20GHz MB: ASUS H97M Plus RAM: 16 GB DISKS: 3X 3TB (Raid 5) Onboard LAN : Intel I218-V Keep a backup of this usb stick and note your serial, mac address, sataportmap and diskidxmap. Also make sure you have a system configuration backup. Quote Link to comment Share on other sites More sharing options...
IG-88 Posted April 16, 2022 Share #2650 Posted April 16, 2022 21 hours ago, blackmix said: I see only 8/16 on 3622xs+ might depend on you definition of "see", the display in the dsm gui is static and only shows what the original synology unit would have the 24 is based on the kernel config that synology published for 3622 you net to look into the log (type "dmesg" in the console) or maybe try "cat /proc/cpuinfo" 1 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.