blackmix Posted April 15, 2022 Share #2576 Posted April 15, 2022 Will we have support for SA3600? I have a xeon e5 2690v3 and SA3600 supports 12 cores and 24 threads. Quote Link to comment Share on other sites More sharing options...
znation Posted April 15, 2022 Share #2577 Posted April 15, 2022 (edited) Il y a 2 heures, RedCat a dit : Not working, I tired and wrote here some days ago... That's the only thing which make me wait to upgrade my dsm to 7.1 Wait and see ... Hope somebody could help for this Edited April 15, 2022 by znation Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 15, 2022 Share #2578 Posted April 15, 2022 I can't do TC because it doesn't have a function yet I tried 7.1-42661 with DS920+ built with TOOL-CHAIN It doesn't seem like all Haswell CPUs don't work. The same Haswell, G3420, failed I only replaced the CPU with the E3-1220 V3, but it was successful a while ago. What is the difference between the two CPUs? Is it the difference between having and not having an iGPU? Quote Link to comment Share on other sites More sharing options...
AlexFullmoon Posted April 15, 2022 Share #2579 Posted April 15, 2022 Hello. I.ve got a problem after upgrading RAM — half or it is shown as "reserved" in GUI and nonexistent in report by free (i.e. 2×4 Gb, free shows only 4 total). Searching got me this older advice to set "disable_mtrr_trim" in grub.cfg, but it's unclear how this applies to redpill, and in any case, where I can add it in Tinycore config. What should I do? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 15, 2022 Share #2580 Posted April 15, 2022 (edited) 41 minutes ago, Peter Suh said: I can't do TC because it doesn't have a function yet I tried 7.1-42661 with DS920+ built with TOOL-CHAIN It doesn't seem like all Haswell CPUs don't work. The same Haswell, G3420, failed I only replaced the CPU with the E3-1220 V3, but it was successful a while ago. What is the difference between the two CPUs? Is it the difference between having and not having an iGPU? The i3-4160T also fails. Edited April 15, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
RedCat Posted April 15, 2022 Share #2581 Posted April 15, 2022 1 hour ago, Peter Suh said: I can't do TC because it doesn't have a function yet I tried 7.1-42661 with DS920+ built with TOOL-CHAIN It doesn't seem like all Haswell CPUs don't work. The same Haswell, G3420, failed I only replaced the CPU with the E3-1220 V3, but it was successful a while ago. What is the difference between the two CPUs? Is it the difference between having and not having an iGPU? It found hdd too? I can boot 920+ with 7.1, but dont find hdd Quote Link to comment Share on other sites More sharing options...
Badger Posted April 15, 2022 Share #2582 Posted April 15, 2022 10 hours ago, Peter Suh said: P@ssw0rd I'm trying Peter Suh's guide from page 102 of this thread... which specifies SSH into TC at the start to facilitate modifying some files before boot. The above password is not working for me. Is there a new one? I've tried both zero 0... and O, but both say access denied. I'm using login id "tc". Please advise. Quote Link to comment Share on other sites More sharing options...
AlexFullmoon Posted April 15, 2022 Share #2583 Posted April 15, 2022 2 hours ago, AlexFullmoon said: Hello. I.ve got a problem after upgrading RAM — half or it is shown as "reserved" in GUI and nonexistent in report by free (i.e. 2×4 Gb, free shows only 4 total). Searching got me this older advice to set "disable_mtrr_trim" in grub.cfg, but it's unclear how this applies to redpill, and in any case, where I can add it in Tinycore config. What should I do? Answering my own question TWIMC, yes, "disable_mtrr_trim" works in 7.0.1, and you just have to mount first partition on usb and manually add it to kernel options. Quote Link to comment Share on other sites More sharing options...
billat29 Posted April 15, 2022 Share #2584 Posted April 15, 2022 (edited) 3 hours ago, AlexFullmoon said: Hello. I.ve got a problem after upgrading RAM — half or it is shown as "reserved" in GUI and nonexistent in report by free (i.e. 2×4 Gb, free shows only 4 total). Searching got me this older advice to set "disable_mtrr_trim" in grub.cfg, but it's unclear how this applies to redpill, and in any case, where I can add it in Tinycore config. What should I do? You can add this to user_config.json: { "extra_cmdline": { "pid": "0x4200", "vid": "0x13fe", "sn": "xxxxxxxxx", "mac1": "xxxxxxxx", "SataPortMap": "42", "DiskIdxMap": "0002", "disable_mtrr_trim": null } This worked on my N54L Edited April 15, 2022 by billat29 2 Quote Link to comment Share on other sites More sharing options...
Badger Posted April 15, 2022 Share #2585 Posted April 15, 2022 Well I finally got there..... 3622xs+ w/7.1-42661 on MSI (MS-7641) mobo (AMD). I was unsuccessful migrating from 7.0.1 to 7.1.0 (although migration from 6.2.3 to 7.0 worked fine). I used Sue's guide from page 102 of this thread (fresh install) and it went smoothly. For the life of me, I couldn't figure out how to SSH or telnet into the DSM as advised... but luckily it just came right up after boot and then installing 42661 from Synology download center. I'm doing a file sync from my genuine DS216J (which is running 7.0.1) and then I'll install some apps and do some testing on the new Xpenology box. Thanks to all developers and testers! Quote Link to comment Share on other sites More sharing options...
cferra Posted April 15, 2022 Share #2586 Posted April 15, 2022 5 hours ago, blackmix said: Will we have support for SA3600? I have a xeon e5 2690v3 and SA3600 supports 12 cores and 24 threads. 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. Quote Link to comment Share on other sites More sharing options...
phone guy Posted April 15, 2022 Share #2587 Posted April 15, 2022 7 hours ago, RedCat said: Not working, I tired and wrote here some days ago... What is not working about it? the build command or adding the ext? they both work and the apollolake is 918 and its clearly listed in that ext url "ds918p_42661": "https://github.com/jumkey/redpill-load/raw/develop/redpill-acpid/recipes/universal.json" ./rploader.sh build apollolake-7.1.0-42661 will build a 918 v7.1 loader. Quote Link to comment Share on other sites More sharing options...
blackmix Posted April 15, 2022 Share #2588 Posted April 15, 2022 1 hour 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. I see only 8/16 on 3622xs+ Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2589 Posted April 16, 2022 7 hours ago, RedCat said: It found hdd too? I can boot 920+ with 7.1, but dont find hdd There is a detailed guide to dtc adjustment of ds920+ in @dolbycat's post. Probably not this topic, but it was shared in the Redfil 6.2.4 topic. Without the correct adjustment of this dtc, the hard drive cannot be found properly. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2590 Posted April 16, 2022 6 hours ago, Badger said: I'm trying Peter Suh's guide from page 102 of this thread... which specifies SSH into TC at the start to facilitate modifying some files before boot. The above password is not working for me. Is there a new one? I've tried both zero 0... and O, but both say access denied. I'm using login id "tc". Please advise. There is no problem with the password. The TC grants a new authentication key again when SSH is accessed after a new boot. So either you use an SSH client that can automatically update this authentication key again, or you have to erase the known_hosts file of ./ssh every time inside the macos terminal. Because of this hassle, I use a utility called PortX. Quote Link to comment Share on other sites More sharing options...
cferra Posted April 16, 2022 Share #2591 Posted April 16, 2022 (edited) 2 hours ago, blackmix said: I see only 8/16 on 3622xs+ Even though the cpu that comes with the unit is 8/16 - the max cores coded in kernel is 24. Linked is a breakdown done by @IG-88 Edited April 16, 2022 by cferra 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2592 Posted April 16, 2022 The 7.1 Dedicated Full Version Installation Guide topic is now approved. I think it would have been better to leave out the number 6 item about using ext. Users who use TC for the first time tend to follow it unconditionally. It's an option only, so please be careful. 1 1 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2593 Posted April 16, 2022 @pocopico Here is the TCRP loader boot log for ds920p-42218. As mentioned above, ds920p-42218 is missing from all ext, so I temporarily modified my repo and used it. There is a problem with the install_rd.sh file script handling the dtb file. It seems that the disc cannot be found because of this. SynologyNAS> cat /var/log/junior_reason Exit on error [99] rp ext init exec failure... 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 kmod #0 "raid_class.ko" for PeterSuh-Q3.mpt3sas (args: ) Loading kmod #1 "scsi_transport_sas.ko" for PeterSuh-Q3.mpt3sas (args: ) Loading kmod #2 "mpt3sas.ko" for PeterSuh-Q3.mpt3sas (args: ) Loading kmod #0 "mii.ko" for PeterSuh-Q3.r8169 (args: ) Loading kmod #1 "r8169.ko" for PeterSuh-Q3.r8169 (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 "check-mpt3sas.sh" for PeterSuh-Q3.mpt3sas->on_boot Loading module mpt3sas -> Module mpt3sas loaded succesfully Ran "check-mpt3sas.sh" for PeterSuh-Q3.mpt3sas->on_boot - exit=0 Running "check-r8169.sh" for PeterSuh-Q3.r8169->on_boot Loading module r8169 -> Module r8169 loaded succesfully Ran "check-r8169.sh" for PeterSuh-Q3.r8169->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) Still waiting for boot device (waited 6 of 30 seconds) Still waiting for boot device (waited 7 of 30 seconds) Still waiting for boot device (waited 8 of 30 seconds) Still waiting for boot device (waited 9 of 30 seconds) Still waiting for boot device (waited 10 of 30 seconds) Still waiting for boot device (waited 11 of 30 seconds) Still waiting for boot device (waited 12 of 30 seconds) Still waiting for boot device (waited 13 of 30 seconds) Still waiting for boot device (waited 14 of 30 seconds) Still waiting for boot device (waited 15 of 30 seconds) Still waiting for boot device (waited 16 of 30 seconds) Still waiting for boot device (waited 17 of 30 seconds) Still waiting for boot device (waited 18 of 30 seconds) Still waiting for boot device (waited 19 of 30 seconds) Still waiting for boot device (waited 20 of 30 seconds) Still waiting for boot device (waited 21 of 30 seconds) Still waiting for boot device (waited 22 of 30 seconds) Still waiting for boot device (waited 23 of 30 seconds) Still waiting for boot device (waited 24 of 30 seconds) Still waiting for boot device (waited 25 of 30 seconds) Still waiting for boot device (waited 26 of 30 seconds) Still waiting for boot device (waited 27 of 30 seconds) Still waiting for boot device (waited 28 of 30 seconds) Still waiting for boot device (waited 29 of 30 seconds) Still waiting for boot device (waited 30 of 30 seconds) ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=1 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 ERROR: Some of the scripts failed! See above for any with exit != 0 :: Executing "on_boot" custom scripts ... [ OK ] Exit on error [99] rp ext init exec failure... Sat Apr 16 04:14:41 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2594 Posted April 16, 2022 7 minutes ago, Peter Suh said: @pocopico Here is the TCRP loader boot log for ds920p-42218. As mentioned above, ds920p-42218 is missing from all ext, so I temporarily modified my repo and used it. There is a problem with the install_rd.sh file script handling the dtb file. It seems that the disc cannot be found because of this. SynologyNAS> cat /var/log/junior_reason Exit on error [99] rp ext init exec failure... 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 kmod #0 "raid_class.ko" for PeterSuh-Q3.mpt3sas (args: ) Loading kmod #1 "scsi_transport_sas.ko" for PeterSuh-Q3.mpt3sas (args: ) Loading kmod #2 "mpt3sas.ko" for PeterSuh-Q3.mpt3sas (args: ) Loading kmod #0 "mii.ko" for PeterSuh-Q3.r8169 (args: ) Loading kmod #1 "r8169.ko" for PeterSuh-Q3.r8169 (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 "check-mpt3sas.sh" for PeterSuh-Q3.mpt3sas->on_boot Loading module mpt3sas -> Module mpt3sas loaded succesfully Ran "check-mpt3sas.sh" for PeterSuh-Q3.mpt3sas->on_boot - exit=0 Running "check-r8169.sh" for PeterSuh-Q3.r8169->on_boot Loading module r8169 -> Module r8169 loaded succesfully Ran "check-r8169.sh" for PeterSuh-Q3.r8169->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) Still waiting for boot device (waited 6 of 30 seconds) Still waiting for boot device (waited 7 of 30 seconds) Still waiting for boot device (waited 8 of 30 seconds) Still waiting for boot device (waited 9 of 30 seconds) Still waiting for boot device (waited 10 of 30 seconds) Still waiting for boot device (waited 11 of 30 seconds) Still waiting for boot device (waited 12 of 30 seconds) Still waiting for boot device (waited 13 of 30 seconds) Still waiting for boot device (waited 14 of 30 seconds) Still waiting for boot device (waited 15 of 30 seconds) Still waiting for boot device (waited 16 of 30 seconds) Still waiting for boot device (waited 17 of 30 seconds) Still waiting for boot device (waited 18 of 30 seconds) Still waiting for boot device (waited 19 of 30 seconds) Still waiting for boot device (waited 20 of 30 seconds) Still waiting for boot device (waited 21 of 30 seconds) Still waiting for boot device (waited 22 of 30 seconds) Still waiting for boot device (waited 23 of 30 seconds) Still waiting for boot device (waited 24 of 30 seconds) Still waiting for boot device (waited 25 of 30 seconds) Still waiting for boot device (waited 26 of 30 seconds) Still waiting for boot device (waited 27 of 30 seconds) Still waiting for boot device (waited 28 of 30 seconds) Still waiting for boot device (waited 29 of 30 seconds) Still waiting for boot device (waited 30 of 30 seconds) ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=1 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 ERROR: Some of the scripts failed! See above for any with exit != 0 :: Executing "on_boot" custom scripts ... [ OK ] Exit on error [99] rp ext init exec failure... Sat Apr 16 04:14:41 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=1 On second thought, the boot-wait seems strange. Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2595 Posted April 16, 2022 47 minutes ago, Peter Suh said: ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=1 On second thought, the boot-wait seems strange. Is it because there is no redfill-misc? First, I will make it into my repo and look at the log again with the build including this. Quote Link to comment Share on other sites More sharing options...
RedCat Posted April 16, 2022 Share #2596 Posted April 16, 2022 (edited) 8 hours ago, phone guy said: What is not working about it? the build command or adding the ext? they both work and the apollolake is 918 and its clearly listed in that ext url "ds918p_42661": "https://github.com/jumkey/redpill-load/raw/develop/redpill-acpid/recipes/universal.json" ./rploader.sh build apollolake-7.1.0-42661 will build a 918 v7.1 loader. I used this link: https://github.com/jumkey/redpill-load/raw/develop/redpill-acpid/rpext-index.json I can add the ext, and I can build the image. The function not working. If I press the power button, nothing happend. Under 7.0.1 it is work, I press button DSM shut down, but unter 7.1 nothing happend. I tired your link also: Edited April 16, 2022 by RedCat Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2597 Posted April 16, 2022 (edited) I don't know if it was shared somewhere, but I'm sharing it for people who don't know. This function is called ttyd. If redpill-misc ext is installed correctly, No separate telnet management is required. The port 7681 enables you to take advantage of existing Telnet access capabilities. (without separate Telnet clients) From your browser, go to http://<yourip>:7681 user root / no password. Edited April 16, 2022 by Peter Suh Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2598 Posted April 16, 2022 45 minutes ago, Peter Suh said: Is it because there is no redfill-misc? First, I will make it into my repo and look at the log again with the build including this. Or, I think it would be right to find sata by loading dtb first and then loading boot-wait, right? Quote Link to comment Share on other sites More sharing options...
Peter Suh Posted April 16, 2022 Share #2599 Posted April 16, 2022 @pocopico I have a question. I am curious about the loading order of ext captured below captured. Alphabetical order of directories visible in the list Does it load as it is? 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) Still waiting for boot device (waited 6 of 30 seconds) Still waiting for boot device (waited 7 of 30 seconds) Still waiting for boot device (waited 8 of 30 seconds) Still waiting for boot device (waited 9 of 30 seconds) Still waiting for boot device (waited 10 of 30 seconds) Still waiting for boot device (waited 11 of 30 seconds) Still waiting for boot device (waited 12 of 30 seconds) Still waiting for boot device (waited 13 of 30 seconds) Still waiting for boot device (waited 14 of 30 seconds) Still waiting for boot device (waited 15 of 30 seconds) Still waiting for boot device (waited 16 of 30 seconds) Still waiting for boot device (waited 17 of 30 seconds) Still waiting for boot device (waited 18 of 30 seconds) Still waiting for boot device (waited 19 of 30 seconds) Still waiting for boot device (waited 20 of 30 seconds) Still waiting for boot device (waited 21 of 30 seconds) Still waiting for boot device (waited 22 of 30 seconds) Still waiting for boot device (waited 23 of 30 seconds) Still waiting for boot device (waited 24 of 30 seconds) Still waiting for boot device (waited 25 of 30 seconds) Still waiting for boot device (waited 26 of 30 seconds) Still waiting for boot device (waited 27 of 30 seconds) Still waiting for boot device (waited 28 of 30 seconds) Still waiting for boot device (waited 29 of 30 seconds) Still waiting for boot device (waited 30 of 30 seconds) ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=1 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 ERROR: Some of the scripts failed! See above for any with exit != 0 :: Executing "on_boot" custom scripts ... [ OK ] Exit on error [99] rp ext init exec failure... Sat Apr 16 05:47:21 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 SynologyNAS> Connection closed by foreign host. Quote Link to comment Share on other sites More sharing options...
pocopico Posted April 16, 2022 Author Share #2600 Posted April 16, 2022 31 minutes ago, Peter Suh said: @pocopico I have a question. I am curious about the loading order of ext captured below captured. Alphabetical order of directories visible in the list Does it load as it is? 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) Still waiting for boot device (waited 6 of 30 seconds) Still waiting for boot device (waited 7 of 30 seconds) Still waiting for boot device (waited 8 of 30 seconds) Still waiting for boot device (waited 9 of 30 seconds) Still waiting for boot device (waited 10 of 30 seconds) Still waiting for boot device (waited 11 of 30 seconds) Still waiting for boot device (waited 12 of 30 seconds) Still waiting for boot device (waited 13 of 30 seconds) Still waiting for boot device (waited 14 of 30 seconds) Still waiting for boot device (waited 15 of 30 seconds) Still waiting for boot device (waited 16 of 30 seconds) Still waiting for boot device (waited 17 of 30 seconds) Still waiting for boot device (waited 18 of 30 seconds) Still waiting for boot device (waited 19 of 30 seconds) Still waiting for boot device (waited 20 of 30 seconds) Still waiting for boot device (waited 21 of 30 seconds) Still waiting for boot device (waited 22 of 30 seconds) Still waiting for boot device (waited 23 of 30 seconds) Still waiting for boot device (waited 24 of 30 seconds) Still waiting for boot device (waited 25 of 30 seconds) Still waiting for boot device (waited 26 of 30 seconds) Still waiting for boot device (waited 27 of 30 seconds) Still waiting for boot device (waited 28 of 30 seconds) Still waiting for boot device (waited 29 of 30 seconds) Still waiting for boot device (waited 30 of 30 seconds) ERROR: Timeout waiting for /dev/synoboot device to appear. Most likely your vid/pid configuration is not correct, or you don't have drivers needed for your USB/SATA controller ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== ========== END OF DUMP OF ALL PARTITIONS DETECTED ========== Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=1 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 ERROR: Some of the scripts failed! See above for any with exit != 0 :: Executing "on_boot" custom scripts ... [ OK ] Exit on error [99] rp ext init exec failure... Sat Apr 16 05:47:21 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 SynologyNAS> Connection closed by foreign host. The only way to know for sure is to extract custom.sh and read the exec file. 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.