Forums

I found solution. 🙂 set static boot on user_config.json to true and boot at least once by selecting TCRP FRIEND

Bonjour Nicoueron, Déjà merci pour ton petit tuto très clair. Cela m'a donné envie de créer un domaine sous OVH, mais maintenant je ne sais pas lier mon domaine à ma Freebox, je dois avouer que je suis complètement perdu avec les paramètre OVH lol. Je n'ai pas vraiment trouvé de tuto pour m'aider dans cette configuration, connaitrais tu un tuto pour m'aider s'il te plais ? Mais je continus à chercher. Merci par avance et bon dimanche,   Gastonzz

[notification] mshell-TCRP remote Xpenology bootloader update function distribution complete and how to use it.   This is how to use the update function of the mshell-TCRP remote Xpe bootloader. This is a method of injecting a loader that was built separately without entering the loader build menu not only remotely but also using mshell that you are already using and building it. This feature also allows migration between models after building with another model.   Please note that when building a loader in native or virtual state, You must set the same MAC address as the remote XPE. Otherwise, upon reboot, the IP address may change to a different IP address than the one you know.   0. Enter the model / version / SN / MAC address suitable for the remote Henology mshell and build the loader pre-build.   1. Create remote.*.tgz file for remote loader upload Use the new "Packing loader file for remote update" as a submenu of the "Addtional Functions" menu. Remote.*.tgz files are created through the process of copying and compressing files as above.   2. Transfer the file to the local PC using scp in the MS Windows command window or MacOS terminal window (requires ' before and after the address path). Just answer yes to the first fingerprint question. You must enter your login password as shown below. In w0rd 0 is a number. In the scp command below. You must not leave out a single thing. scp tc@192.168.35.62:/home/tc/remote.*.tgz . yes P@ssw0rd     3. Check the downloaded file through Explorer and prepare to upload the file to the remote Synology. Control Panel->Users & Groups->Advanced Tab->Enable User Home Service.  (The user home does not necessarily have to be volume 1.)     4. Upload remote.*.tgz files to /homes/admin with File Station. Be sure to upload only one file. If there is an existing remote.*.tgz file, be sure to delete it in advance and upload only the one you want to use.   5. Execute the upgrade processing shell command with root privileges. sudo -i bash -c "$(curl https://raw.githubusercontent.com/PeterSuh-Q3/tinycore-redpill/main/remote-upgrade.sh)"   6. Reboot Synology to apply the upgrade.  If you are using a version other than DSM Update 0, you can perform one-time recovery.  This recovery is a normal process, so please proceed as is.      Review: I wanted to be able to upload files and handle upgrades through a GUI like rr manager.  I couldn't implement it because I don't know how to code in PHP, Python, and web UI.  Also, grub.cfg was not copied to the P1 partition on purpose.  Only the Synology model name changes, and if touched incorrectly, the VID/PID of the USB may be recorded incorrectly, resulting in a fatal kernel panic.  This part was excluded because it could be problematic.    

First, if you consider your remote N54L, it may not be suitable for using the remote upgrade function I developed this time. The remote loader may be using DSM 5 and has a different structure from redpill. This upgrade pack is available assuming you are already using the mshell bootloader. This time, please visit your parents' house and replace the loader manually like we did this time.   1x Baremetal N54L install of DSM 7.2.1-69057 Update 5 using TCRP-mshell loader as DS3622xs+ 2x Baremetal N54L install of DSM 5.2-5967 Update 3 using XPEnoboot_DS3615xs_5.2-5644.5 using Jun Loader as DS3615xs     And honestly, it is difficult to pinpoint why the acpid addon does not work. Since the addon used by the rr loader is simply borrowed, there is no in-depth analysis. As a result of testing on my DS1520+ (Gemini Lake like DS920+), button.ko exists and operates as a modprobe.     However, when checking whether the service is operating well using the command below, it shows that acpid is operating well.   systemctl status acpid.service  

You must use the top command on Synology or use the resource manager to find programs causing overload.   /usr/sbin/scaler.sh Are you overloading top?   Can you capture and show me the evidence?