Madasafish Posted September 27, 2022 #1 Posted September 27, 2022 Any ideas? [!] One of the patches - /home/tc/redpill-load/config/_common/v7.1.1/ramdisk-003-post-init-script.patch - failed to apply Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- /usr/sbin/init.post |+++ /usr/sbin/init.post -------------------------- patching file usr/sbin/init.post Using Plan A... Hunk #1 FAILED at 31. 1 out of 1 hunk FAILED -- saving rejects to file usr/sbin/init.post.rej done *** Process will exit *** FAILED : Loader creation failed check the output for any errors Quote
pocopico Posted September 27, 2022 #2 Posted September 27, 2022 12 minutes ago, Madasafish said: Any ideas? [!] One of the patches - /home/tc/redpill-load/config/_common/v7.1.1/ramdisk-003-post-init-script.patch - failed to apply Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- /usr/sbin/init.post |+++ /usr/sbin/init.post -------------------------- patching file usr/sbin/init.post Using Plan A... Hunk #1 FAILED at 31. 1 out of 1 hunk FAILED -- saving rejects to file usr/sbin/init.post.rej done *** Process will exit *** FAILED : Loader creation failed check the output for any errors which platform ? Quote
Madasafish Posted September 27, 2022 Author #3 Posted September 27, 2022 The platform is shown in my signature. It's a new install and the command line used was... ./rploader.sh build bromolow-7.1.1-42962 Quote
pocopico Posted September 27, 2022 #4 Posted September 27, 2022 8 hours ago, Madasafish said: The platform is shown in my signature. It's a new install and the command line used was... ./rploader.sh build bromolow-7.1.1-42962 While at TCRP can you verify that the following edit works ? vi /home/tc//redpill-load/config/DS3615xs/7.1.1-42962/config.json find line : "@@@COMMON@@@/v7.1.1/ramdisk-003-post-init-script.patch", and replace with line : "@@@COMMON@@@/v7.1.1/ramdisk-003-post-init-script-noatime.patch", and run again the ./rploader.sh build bromolow-7.1.1-42962 Quote
Madasafish Posted September 28, 2022 Author #5 Posted September 28, 2022 I should not have attempted to load "bromolow-7.1.1-42962" build according to "7.x Loaders and Platforms as of 06-June-2022". So following that chart and using "bromolow-7.1.0-42661" as per the chart recommendation. Synology assistant see's the server and requests a "pat" file. The best progress I can get to is 57% using "DSM_DS3615xs_42661.pat"(link is in the chart). I have tried other 7.1 bromolow "pat" files but they fail earlier. Using the serial console provided by TinyCore on http://<yourip>:7681 (user/pass root/<blank>). cat/vi the log file linuxrescue.... cat /var/log/*rc* DiskStation> cat /var/log/*rc* START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module uhci-hcd ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "libphy.ko" for pocopico.tg3 (args: ) Loading kmod #1 "tg3.ko" for pocopico.tg3 (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-tg3.sh" for pocopico.tg3->on_boot Loading module tg3 -> Module tg3 loaded succesfully Ran "check-tg3.sh" for pocopico.tg3->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) The /dev/synoboot device exists but it does not contain expected partitions (>=3 partitions) ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== /dev/sda1 2048 4982527 4980480 fd /dev/sda2 4982528 9176831 4194304 fd /dev/sda3 9437184 1953320351 1943883168 fd /dev/sdb1 2048 4982527 4980480 fd /dev/sdb2 4982528 9176831 4194304 fd /dev/sdb3 9437184 1953320351 1943883168 fd /dev/sdc1 2048 4982527 4980480 fd /dev/sdc2 4982528 9176831 4194304 fd /dev/sdc3 9437184 1953320351 1943883168 fd /dev/sdd1 2048 4982527 4980480 fd /dev/sdd2 4982528 9176831 4194304 fd /dev/sdd3 9437184 1953320351 1943883168 fd /dev/sde1 2048 4982527 4980480 fd /dev/sde2 4982528 9176831 4194304 fd /dev/synoboot1 2048 100351 98304 83 /dev/synoboot2 100352 253951 153600 83 /dev/synoboot3 253952 2097151 1843200 83 ========== 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-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->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... Wed Sep 28 06:50:42 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 ============================================ Is this easily fixed? Quote
pocopico Posted September 28, 2022 #6 Posted September 28, 2022 (edited) 9 hours ago, Madasafish said: I should not have attempted to load "bromolow-7.1.1-42962" build according to "7.x Loaders and Platforms as of 06-June-2022". So following that chart and using "bromolow-7.1.0-42661" as per the chart recommendation. Synology assistant see's the server and requests a "pat" file. The best progress I can get to is 57% using "DSM_DS3615xs_42661.pat"(link is in the chart). I have tried other 7.1 bromolow "pat" files but they fail earlier. Using the serial console provided by TinyCore on http://<yourip>:7681 (user/pass root/<blank>). cat/vi the log file linuxrescue.... cat /var/log/*rc* DiskStation> cat /var/log/*rc* START /linuxrc.syno.impl Insert basic USB modules... :: Loading module usb-common ... [ OK ] :: Loading module usbcore ... [ OK ] :: Loading module ehci-hcd ... [ OK ] :: Loading module ehci-pci ... [ OK ] :: Loading module uhci-hcd ... [ OK ] :: Loading module xhci-hcd ... [ OK ] :: Loading module usb-storage ... [ OK ] :: Loading kernel modules from extensions ... Loading kmod #0 "libphy.ko" for pocopico.tg3 (args: ) Loading kmod #1 "tg3.ko" for pocopico.tg3 (args: ) :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-tg3.sh" for pocopico.tg3->on_boot Loading module tg3 -> Module tg3 loaded succesfully Ran "check-tg3.sh" for pocopico.tg3->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) The /dev/synoboot device exists but it does not contain expected partitions (>=3 partitions) ========== BEGIN DUMP OF ALL PARTITIONS DETECTED =========== /dev/sda1 2048 4982527 4980480 fd /dev/sda2 4982528 9176831 4194304 fd /dev/sda3 9437184 1953320351 1943883168 fd /dev/sdb1 2048 4982527 4980480 fd /dev/sdb2 4982528 9176831 4194304 fd /dev/sdb3 9437184 1953320351 1943883168 fd /dev/sdc1 2048 4982527 4980480 fd /dev/sdc2 4982528 9176831 4194304 fd /dev/sdc3 9437184 1953320351 1943883168 fd /dev/sdd1 2048 4982527 4980480 fd /dev/sdd2 4982528 9176831 4194304 fd /dev/sdd3 9437184 1953320351 1943883168 fd /dev/sde1 2048 4982527 4980480 fd /dev/sde2 4982528 9176831 4194304 fd /dev/synoboot1 2048 100351 98304 83 /dev/synoboot2 100352 253951 153600 83 /dev/synoboot3 253952 2097151 1843200 83 ========== 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-misc->on_boot Starting ttyd, listening on port: 7681 Ran "install_rd.sh" for redpill-misc->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... Wed Sep 28 06:50:42 UTC 2022 none /sys/kernel/debug debugfs rw,relatime 0 0 ============================================ Is this easily fixed? Yes, you need to specify on the linux line the size of loader disk. The variable is dom_szmax=XXX the total size in MB of your loader disk. If its 2GB the 2048, if 4 then 4096 and so on. EDIT : You can also set it on your user_config.json in the extra_cmdline section : "dom_szmax": "2048" Edited September 28, 2022 by pocopico Quote
Madasafish Posted September 30, 2022 Author #7 Posted September 30, 2022 All working now with TCRP v0.9.2.5 Thank-you 1 Quote
yorkman Posted November 18, 2022 #8 Posted November 18, 2022 I'm getting a similar error after running the command: ./rploader.sh build ds918p-7.0.1-42218 [!] One of the patches - /home/tc/redpill-load/config/_common/ramdisk-005-disable-disabled-ports.patch - failed to apply Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |--- a/usr/syno/web/webman/get_state.cgi |+++ b/usr/syno/web/webman/get_state.cgi -------------------------- patching file usr/syno/web/webman/get_state.cgi Using Plan A... Hunk #1 FAILED at 1. 1 out of 1 hunk FAILED... FAILED : Loader creation failed check the output for any errors any ideas on how to resolve? Running it from VMware Workstation v16.x. using tinycore-redpill.v0.9.3.0.vmdk Quote
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.