Leaderboard

[NOTICE] Now, when using DS918+ and HBA in REDPILL, the hard drive serial number is displayed. I've been hanging here all day today, and for the first time in a while, I'm bringing you some good news. It seems that DS918+ (apollolake) will now rise again to the level of the most perfect model. Transcoding, HBA everything is perfect. This makes it the only model that supports these two conditions. Until now, there has been a problem with not being able to distribute the serial number, which is the S.M.A.R.T information of the hard disk, when using it with HBA. There was a fatal problem that made it difficult to replace the hard drive when using it in raid mode. Today, the source of lkm5 for Kernel 5 developed for SA6400 was developed targeting Kernel 5, but various improvements were seen. https://github.com/XPEnology-Community/redpill-lkm5 I imported only the improved parts of the existing lkm source for Kernel 4 and compiled it. A new source that stands out is scsi_disk_serial.c / scsi_disk_serial.h. I could smell it just by looking at the name, so I brought it right away. lol scsi corresponds to the hba device and means the serial source of the disk. https://github.com/PeterSuh-Q3/redpill-lkm/blob/master/shim/storage/scsi_disk_serial.c Many experts came together to solve this problem in order to improve this source. Development was completed 3 months ago, but it seems no one has thought to apply it to Kernel 4.^^ Currently only applied to M-SHELL. I will spread this information separately to ARPL developers. As always, you will need to rebuild your loader. The lkm version that must be updated to the new version during the build process is 23.5.8. https://github.com/PeterSuh-Q3/redpill-lkm/releases/tag/23.5.8 @wjz304 Please see my lkm linked. I think you can consider the sources modified today as the target for syncing. Please try it and contact us if you have any problems. https://github.com/PeterSuh-Q3/redpill-lkm

Hello everyone, my name is pdbear. Recently, I've been exploring the setup of media servers like Emby, Plex, Jellyfin, etc., within Synology NAS. I noticed that the lack of GPU transcoding functionality was something missing. As a vGPU user, I took some time to adapt it accordingly. Currently, the driver is based on 510.108.03, and it supports almost all x86 Synology NAS with kernel 4.4.302+. Feel free to give it a try. github link: https://github.com/pdbear/syno_nvidia_gpu_driver

[NOTICE] M SHELL for TCRP v0.9.5.0 is released. https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.5.0 Added storage panel size selection menu and applied processing Addon (StoragePanel). Thanks to @wjz304 If you enter the loader build menu, you will see the new menu below activated by automatic update. The bay size of the storage panel is basically selected as the size of the genuine model. You can choose the size you would like to change. After that, just build the loader as usual. If you want to change the bay panel type again after using it, Even if DSM is already installed, you can run the Change Storage Panel registered in the manual scheduler. The size selected at the time of the loader build is the last one recorded. After editing, you can record one of the examples written after the # in the option at the back of storagepanel.sh in the task settings without typos. The size of the M.2 bay is arbitrarily set to 1X4. If you write only the desired number in ?/# in the form of ?X#, the size of the M.2 bay changes accordingly. The ? number in front is the singular number, and the # number after it is the quantity for each stage. Modify the option after .sh, check it, execute it, and reboot once to reflect it.

Internalportcfg，esataportcfg，usbportcfg计算.xlsx

SA6400 is an amd model and does not include an intel core graphics card. Jim developed 10-13 generation intel core graphics cards for sa6400. And it is still being optimized, arpl-i18n will not integrate them without the author's permission. You can ask jim for details.

[NOTICE] Now, when using DS918+ and HBA in REDPILL, the hard drive serial number is displayed. I've been hanging here all day today, and for the first time in a while, I'm bringing you some good news. It seems that DS918+ will now rise again to the level of the most perfect model. Transcoding, HBA everything is perfect. This makes it the only model that supports these two conditions. Until now, there has been a problem with not being able to distribute the serial number, which is the S.M.A.R.T information of the hard disk, when using it with HBA. There was a fatal problem that made it difficult to replace the hard drive when using it in raid mode. Today, the source of lkm5 for Kernel 5 developed for SA6400 was developed targeting Kernel 5, but various improvements were seen. https://github.com/XPEnology-Community/redpill-lkm5 I imported only the improved parts of the existing lkm source for Kernel 4 and compiled it. A new source that stands out is scsi_disk_serial.c / scsi_disk_serial.h. I could smell it just by looking at the name, so I brought it right away. lol scsi corresponds to the hba device and means the serial source of the disk. https://github.com/PeterSuh-Q3/redpill-lkm/blob/master/shim/storage/scsi_disk_serial.c Many experts came together to solve this problem in order to improve this source. Development was completed 3 months ago, but it seems no one has thought to apply it to Kernel 4.^^ Currently only applied to M-SHELL. I will spread this information separately to ARPL developers. As always, you will need to rebuild your loader. The lkm version that must be updated to the new version during the build process is 23.5.8. https://github.com/PeterSuh-Q3/redpill-lkm/releases/tag/23.5.8

I will build the same system after work today and test whether it works with igb without having to remove x540-T2. If the problem is recurring, I will improve it and distribute it.

This behavior seems to be a bit regular with the: x540-T2 (I have one), to avoid this I carry out the process without the 10G NIC installed, after the whole process, I turn off the PC, install the x540-T2 and it works without problems. There is a similar behavior on the original boxes with a DS1821+ and E10G18-T1 the first boot for the first time does not give ping. but if I first configure DSM and then put the NIC, everything works without problems.

And if you simply need a 5-bay storage panel instead of 4, you may want to use the panel size change function that has been supported since version 23.8.8 below. Install DS923+ and change panel size from 4 to 5. https://github.com/wjz304/arpl-i18n/releases/tag/23.8.8

Before installing XPEnology using DSM 7.x, you must select a DSM platform and loader. XPEnology supports a variety of platforms that enable specific hardware and software features. All platforms support a minimum of 4 CPU cores, 64GB of RAM, 10Gbe network cards and 16 drives. Each can run "baremetal" as a stand-alone operating system OR as a virtual machine within a hypervisor. A few specific platforms are preferred for typical installs. Review the table and decision tree below to help you navigate the options. NOTE: DSM 6.x is still a viable system and is the best option for certain types of hardware. See this link for more information. DSM 7.x LOADERS ARE DIFFERENT: A loader allows DSM to install and run on non-Synology hardware. The loaders for DSM 5.x/6.x were monolithic; i.e. a single loader image was applicable to all installs. With DSM 7.x, a custom loader must be created for each DSM install. TinyCore RedPill (TCRP) is currently the most developed tool for building 7.x loaders. TCRP installs with two step-process. First, a Linux OS (TinyCore) boots and evaluates your hardware configuration. Then, an individualized loader (RedPill) is built and written to the loader device. After that, you can switch between starting DSM with RedPill, and booting back into TinyCore to adjust and rebuild as needed. TCRP's Linux boot image (indicated by the version; i.e. 0.8) changes only when a new DSM platform or version is introduced. However, you can and should update TCRP itself prior to each loader build, adding fixes, driver updates and new features contributed by many different developers. Because of this ongoing community development, TCRP capabilities change rapidly. Please post new or divergent results when encountered, so that this table may be updated. 7.x Loaders and Platforms as of 06-June-2022 Options Ranked 1a 1b 2a 2b 2c 3a 3b DSM Platform DS918+ DS3622xs+ DS920+ DS1621+ DS3617xs DVA3221 DS3615xs Architecture apollolake broadwellnk geminilake v1000 broadwell denverton bromolow DSM Versions 7.0.1-7.1.0-42661 7.0.1-7.1.0-42661 7.0.1-7.1.0-42661 7.0.1-7.1.0-42661 7.0.1-7.1.0-42661 7.0.1-7.1.0-42661 7.0.1-7.1.0-42661 Loader TCRP 0.8 TCRP 0.8 TCRP 0.8 TCRP 0.8 TCRP 0.8 TCRP 0.8 TCRP 0.8 Drive Slot Mapping sataportmap/ diskidxmap sataportmap/ diskidxmap device tree device tree sataportmap/ diskidxmap sataportmap/ diskidxmap sataportmap/ diskidxmap QuickSync Transcoding Yes No Yes No No No No NVMe Cache Support Yes Yes Yes Yes Yes (as of 7.0) Yes No RAIDF1 Support No Yes No No Yes No Yes Oldest CPU Supported Haswell * any x86-64 Haswell ** any x86-64 any x86-64 Haswell * any x86-64 Max CPU Threads 8 24 8 16 24 (as of 7.0) 16 16 Key Note currently best for most users best for very large installs see slot mapping topic below AMD Ryzen, see slot mapping topic obsolete use DS3622xs+ AI/Deep Learning nVIDIA GPU obsolete use DS3622xs+ * FMA3 instruction support required. All Haswell Core processors or later support it. Very few Pentiums/Celerons do (J-series CPUs are a notable exception). Piledriver is believed to be the minimum AMD CPU architecture equivalent to Intel Haswell. ** Based on history, DS920+ should require Haswell. There is anecdotal evidence gradually emerging that DS920+ will run on x86-64 hardware. NOT ALL HARDWARE IS SUITABLE: DSM 7 has a new requirement for the initial installation. If drive hotplug is supported by the motherboard or controller, all AHCI SATA ports visible to DSM must either be configured for hotplug or have an attached drive during initial install. Additionally, if the motherboard or controller chipset supports more ports than are physically implemented, DSM installation will fail unless they are mapped out of visibility. On some hardware, it may be impossible to install (particularly on baremetal) while retaining access to the physical ports. The installation tutorial has more detail on the causes of this problem, and possible workarounds. DRIVE SLOT MAPPING CONSIDERATIONS: On most platforms, DSM evaluates the boot-time Linux parameters SataPortMap and DiskIdxMap to map drive slots from disk controllers to a usable range for DSM. Much has been written about how to set up these parameters. TCRP's satamap command determines appropriate values based on the system state during the loader build. It is also simple to manually edit the configuration file if your hardware is unique or misidentified by the tool. On the DS920+ and DS1621+ platforms, DSM uses a Device Tree to identify the hardware and ignores SataPortMap and DiskIdxMap. The device tree hardcodes the SATA controller PCI devices and drive slots (and also NVMe slots and USB ports) prior to DSM installation. Therefore, an explicit device tree that matches your hardware must be configured and stored within the loader image. TCRP automatic device tree configuration is limited. For example, any disk ports left unpopulated at loader build time will not be accessible later. VMware ESXi is not currently supported. Host bus adapters (SCSI, SAS, or SATA RAID in IT mode) are not currently supported. Manually determining correct values and updating the device tree is complex. Device Tree support is being worked on and will improve, but presently you will generally be better served by choosing platforms that support SataPortMap and DiskIdxMap (see Tier 1 below). CURRENT PLATFORM RECOMMENDATIONS AND DECISION TREE: VIRTUALIZATION: All the supported platforms can be run as a virtual machine within a hypervisor. Some use case examples: virtualize unsupported network card virtualize SAS/NVMe storage and present to DSM as SATA run other VMs in parallel on the same hardware (as an alternative to Synology VMM) share 10GBe network card with other non-XPEnology VMs testing and rollback of updates Prerequisites: ESXi (requires a paid or free license) or open-source hypervisor (QEMU, Proxmox, XenServer). Hyper-V is NOT supported. Preferred Configurations: passthrough SATA controller and disks, and/or configure RDM/RAW disks This post will be updated as more documentation is available for the various TCRP implementations.

1.Select the menu to edit user config as shown below. 2.When you enter the menu, it changes to editing mode as shown below. Edit as shown below and move the focus to the OK button with the Tab key once. Save and exit with the Enter key. Be careful to avoid typos. 3.If it is changed normally, you will not be able to see the MaxDisks item. You can check in the window at the bottom right that the remaining three items have changed. 4. Now please rebuild the loader.

Опять как в прошлый раз, сам спросил - сам ответил)

Reporting is a little late. A few days ago, I purchased the product below and tried it out. https://www.ebay.co.uk/itm/385760379322 Tested on DT-based ds920+. esata does not separate it into a separate device tree. It is considered one of the sata ports. As a result as below, model.dts and model.dtb are converted via the dtbpatch add-on.. It has been confirmed that it is created automatically. No separate work is required on synoinfo.conf or model.dtb. The add-on maps the disk automatically. SynologyNAS> ll /sys/block | grep -e sata -e sd lrwxrwxrwx 1 root root 0 Sep 7 13:32 sata1 -> ../devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sata1 Running "install.sh" for dtbpatch->on_boot->modules dtbpatch - modules 'dtc' -> '/usr/sbin/dtc' 'readlink' -> '/usr/sbin/readlink' Patching /etc.defaults/ ls: /sys/bus/usb/devices/usb*: No such file or directory /dts-v1/; / { compatible = "Synology"; model = "synology_geminilake_920+"; version = <0x01>; internal_slot@1 { protocol_type = "sata"; ahci { pcie_root = "00:1f.2"; ata_port = <0x04>; }; }; }; backup /etc.defaults/model.dtb to model_bak.dtb '/etc.defaults/model.dtb' -> '/etc.defaults/model_bak.dtb' /var/run/model.dts:6.21-12.7: Warning (unit_address_vs_reg): /internal_slot@1: node has a unit name, but no reg or ranges property '/etc.defaults/model.dtb' -> '/run/model.dtb' System Disk: (not supported in junior mode) Internal Disk 01: /dev/sata1 02: 03: 04: 05: 06: 07: 08: 09: 10: 11: 12: 13: 14: 15: 16: Esata port count: 0 USB Device Ran "install.sh" for dtbpatch->on_boot->modules - exit=0

Yep. The random reboot was not the loader but my motherboard (hardware pb). Since I changed it, no problems at all...

Moi perso j'ai une carte mere ali express que tu as mise en lien sur ton post (N5105). 2 nvme non bridé en gen3, 6 ports SATA. Elle fonctionne parfaitement bien. Et concernant le iGPU, y'a un loader compatible avec les bons drivers, je peux te mettre en relation avec le dev pour qu'il te file l'img (base ARPL). Tous les drivers iGPU 11,12 et 13 sont ok. Elle fonctionne parfaitement bien (6 hw transco en // sans problèmes), 40-50w de conso avec 4 disques de 18To, 2 NVMe de 500Go. Sinon tu as le QNAP TS-364, tu le trouve aux alentours des 400e, il est compatible avec le loader en question (il tourne en ce moment même chez moi aussi lol, NAS d'un collègue) Sinon Si tu as un peu plus de budget, tu as des cartes Erying avec un CPU mobile 11500h ou 12500h, la carte coute entre 180 et 260e selon le modele. 60-65w de conso, mais une puissance qui n'a rien à voir... Par contre, en cas de charge, tu montes a 100-150w (transco CPU par ex sans HW transco) N5105 pour 140e : https://fr.aliexpress.com/item/1005005931159486.html?spm=a2g0o.productlist.main.1.6ada6a34DKs3ez&algo_pvid=14f5c485-f144-4e89-ac6c-bceb327f8ee7&algo_exp_id=14f5c485-f144-4e89-ac6c-bceb327f8ee7-0&pdp_npi=4%40dis!EUR!200.69!140.48!!!212.62!!%4021038eda16935712795733425e5bd2!12000034902017161!sea!FR!0!A&curPageLogUid=BeQaAz5ps8MO 11500h : https://fr.aliexpress.com/item/1005005881497180.html?spm=a2g0o.productlist.main.3.4ebd1e6cjVdPPk&algo_pvid=47bd563c-a8f6-4ac0-a698-86ab789c4674&algo_exp_id=47bd563c-a8f6-4ac0-a698-86ab789c4674-1&pdp_npi=4%40dis!EUR!495.00!198.0!!!495.00!!%4021038eda16935713115294787e5bd2!12000034686691773!sea!FR!0!A&curPageLogUid=M4BjrTpueIZP 12500h : https://fr.aliexpress.com/item/1005005881418539.html?spm=a2g0o.productlist.main.5.2e401e6c8rkGua&algo_pvid=5f130915-2d2d-4d28-b441-f707b207b469&algo_exp_id=5f130915-2d2d-4d28-b441-f707b207b469-2&pdp_npi=4%40dis!EUR!670.00!268.0!!!670.00!!%4021038eda16935713424435643e5bd2!12000034686441983!sea!FR!0!A&curPageLogUid=lsUjDMajDu3t

[notification] Introducing a new add-on "drivedatabase" for unrecognized firmware version issues. It is a shell called Synology_HDD_db created by @007revad, and with some modifications, it is installed automatically along with the M SHELL for TCRP loader as a service of DSM. https://github.com/PeterSuh-Q3/tcrp-addons/tree/main/drivedatabase To use this addon you will need to rebuild your loader. If you are prompted to update the drive database due to a storage manager error as shown below, you can rebuild the loader or run @007revad's Synology_HDD_db directly by connecting to ssh on DSM. Execute the command as below. sudo -i curl -kLO https://raw.githubusercontent.com/007revad/Synology_HDD_db/main/syno_hdd_db.sh chmod +x syno_hdd_db.sh ./syno_hdd_db.sh

Thank you for your feedback. However, DS920+ is a platform that cannot use HBA, so it seems to have nothing to do with mptsas and the recently improved redpill.ko (lkm). So, I think the cause of the unknown firmware coming out of DS920+ lies somewhere else. There is already a solution to solve the unknown firmware issue, but there was no notice. I will post a notice about this “drivedatabse” addon a little later.

Hello @Peter Suh THANK YOU VERY MUCH FOR YOUR ABOVE AND BEYOND ATTENTION and EFFORT in making all of this JUST WORK! I wanted to pass on to you as well, that my 920+ just using standard SATA controllers, now too is showing unknown firmware. I had previous used that script to have my HDD's recognized by DSM, and all had been just fine for a good while. The only thing I have done, is on 2 separate times, just to catch some updates you created/added, I rebuild the loader, nothing more. So whatever got changed/added/modified on the backend, that carried forward into the new builds, making no other modifications, that seems to have brought on this quirk. 😉 It doesn't appear to be detrimental in any way, but just wanted to give you some additional supportive feedback. Thank YOU for being the Master you are!

Естественно. И сконфигурировать ее. Если система работала, то на новой флешке можно найти и востановить существуюшую DSM из меню.

Hello ! I can tell that someone found the solution with loader SA6400 with kernel 5.10 Integrated gpu from 11th to 13gen is working fine, and CPU too^^. Backport and integration of i915 is working just fine actually My config based on Erying chineese motherboard, based on mobile CPU on an ITX motherboard :

[NOTICE] MSHELL for TCRP, NVMe volumeization function has been applied. NVMe Volumeization is a feature that enables the use of NVMe cache and additional NVMe volumes. As always, you need to rebuild the loader for the feature to work. If DSM is not activated immediately after installation, you must reboot once. If you want to check that the script is working normally, you can run the command below with sudo privileges. sudo -i for file in `ls /etc/systemd/system/*.service | awk -F / '{print $NF}'`; do systemctl status ${file}; done If the check result shows that the file has already been edited as shown below, it is normal. Because the service is running repeatedly Patches of the libhwcontrol.so.1 file are iterated over and over again. ( DS3622xs+ seems to be patched normally, but it doesn't actually work. ) As a result of testing with @007revad the currently operating platform is Apollo Lake, Gemini Lake, v1000, r1000 and DS1621xs+. Broadwell, Broadwellnk, Denverton will not work. https://github.com/007revad/Synology_enable_M2_volume Thanks 007revad

You can also forget HP Gen10 plus at least with ESXi/Proxmox, already tried no way to passtrough the iGPU. Maybe as baremetal, but did not try.

Nope, cpu generation is old as well as igpu, lowest igpu needed for AI/DVA is HD500 if not mistaken, some reported working on 4400 but I doubt that. P.S. in my personal experience HD530 worked with AI perfectly (its i3-6100T cpu) so lower than that probably won't work with AI. Your Xeon is like i7-3770 which 3 gens older than needed unfortunately

In fact, there were requests from users to create a new guide, There's nothing complicated enough to make it a guide. In this request, "I am a beginner, so I really need this guide!" The request is also a bit far-fetched. Proceed to build the TCRP loader again for 7.2 and you're done. There is absolutely nothing difficult.

Hello, If someone is interested, I built the WireGuard SPK for Epyc7002 DSM 7.2 Original souces and instructions here : https://www.blackvoid.club/wireguard-spk-for-your-synology-nas/ WireGuard-epyc7002-1.0.20220627.spk

Ok, I removed the NIC, booted without it, shut down, inserted it again, rebooted and the card works Don't know why, didn't change anything, but actually, I'm a happy camper. One annoying thing, upon every restart, one of my disks reports an partition error and I have to repair it... Thereafter everything is fine. SMART shows no errors.

Loader Information and Background RedPill is the core technology that enables DSM 7.x to run on non-Synology hardware. This post is intended to serve as a definitive tutorial/reference for configuring @pocopico's TinyCore RedPill (TCRP) loader. It explains how to install TCRP on baremetal, i.e. with DSM as the only operating system on your NAS hardware. A tutorial to install TCRP using the ESXi hypervisor is located here. There are other hypervisor tutorials in the Tutorials and Guides forum. TCRP uses a two step-process. First, a Linux OS (TinyCore) boots and evaluates the NAS hardware configuration. Therefore, it is best to have the hardware you plan to use (disk controllers and network cards in particular) installed prior to starting the TCRP setup. Then, an individualized loader (RedPill) is created. This loader is used to install and run DSM. After that, you can switch between starting DSM with RedPill, and booting back into TinyCore to adjust and rebuild the loader as needed. Basic Linux command line skills are needed to complete the installation. The tutorial provides examples of the commands that are needed, but exact syntax and capitalization are critical. If unfamiliar, research and review the following minimal list of commands: ls show the files in the current directory cat <file> show the contents of the specified file pwd show the current directory name cd <directory path> change to the specified directory (same rules as Windows, except with forward slashes instead of backslashes). With no argument, it returns to the “home” TCRP directory vi <file> a file editor, for manual editing of configuration files if required Ongoing Development This tutorial is maintained for consistency with the pocopico stable repository. Since TCRP is completely open-sourced, anyone can fork their own repo and contribute to development, and pocopico now maintains a separate development repo. As the best features and ideas are fully vetted and tested, they may be incorporated into the stable repo over time. If you use a repo, script or shell other than the pocopico stable repo, the loader may behave quite differently and the instructions and troubleshooting steps in this tutorial might no longer apply. In an open-source community, you can use any development resource you want, but you add the additional responsibility of understanding, vetting and testing that code on your system. Migration Step 1. Choose a DSM Platform/Architecture Evaluate your intended NAS hardware and your the intended use of DSM, and select a platform that best meets your needs. Reference information here: https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/ Write down the selected platform (e.g. DS918+), the corresponding architecture (e.g. apollolake) and whether the platform uses SataPortMap/DiskIdxMap or Device Tree for slot mapping. This information will be needed later. Now, make sure the NAS hardware is compatible, and prepare it correctly: x86-64-compatible CPU with two cores or more Each platform have maximum threads support! Any threads in excess will be ignored For certain platforms, Intel CPUs must be 4th generation “Haswell” or newer with FMA3 instruction set The corresponding AMD CPU architecture is “Piledriver” or newer AMD-based systems may require deactivation of the C1E option in the BIOS 2GB of RAM or more 2GB or larger USB flash drive Configure the BIOS to boot from the USB flash drive ONLY SATA disk controllers are preferred, but SCSI/SAS are compatible IMPORTANT: All SATA controllers must be configured to AHCI mode SATA controllers with port multipliers are not compatible ATA controllers are not compatible (disable embedded ATA in BIOS if possible) At least one SATA/SCSI/SAS drive (HDD or SSD), minimum size 21GB IMPORTANT: Enable SATA port hotplug on each disk port, if hotplug is supported by the BIOS/controller IMPORTANT: Disable M.2 SATA ports that are not in use, if supported by the BIOS/controller NVMe drives are not usable except as dedicated cache devices Host Bus Adapters are not currently compatible with Device Tree platforms Install any NVMe drives intended as cache devices On Device Tree platforms, NVMe drives must be installed prior to loader installation in order for them to be recognized Step 2. Download TCRP and Write Image to the USB Flash Drive The latest pocopico stable loader code is always linked here: https://xpenology.com/forum/topic/7848-links-to-loaders/ Download the tinycore-redpill 7.x loader and save it to your personal computer. Then, open it with a zip manager to show the boot images: tinycore-redpill.vX.X.X.img.gz (for BIOS/CSM/Legacy boot from USB flash drive) tinycore-redpill-uefi.vX.X.X.img.gz (for UEFI/EFI boot from USB flash drive) tinycore-redpill.vX.X.X.vmdk.gz (for virtual machine SATABOOT from disk image) Select the boot image that matches the boot capability of the NAS motherboard. If unsure, choose BIOS/CSM/Legacy boot. Save the gzip file to your personal computer, then open it with a zip archive manager and save the uncompressed version. Write the uncompressed image to the USB flash drive using Win32DiskImager or other appropriate tool. The USB flash drive is used to store TinyCore and the RedPill loader that it generates. It is a permanent component of an operational XPEnology system. Do not remove it, even after the DSM installation is complete and the NAS is fully up and running. Step 3. Boot into TinyCore and Complete Pre-Configuration Updates Start your NAS with the USB flash drive installed and TinyCore will boot. Then, launch a command-line session with either of these methods: Click the Terminal icon at the bottom right of the TinyCore desktop to launch a console window Use a ssh client (e.g. PuTTY) on your computer to connect a network-based console Consult your DHCP server/router for the IP address assignment (TinyCore's host name is "box") Login credentials: tc/P@ssw0rd When the Linux command line prompt ($) is displayed, update the TCRP script ./rploader.sh update Checking Internet Access -> OK Checking if a newer version exists -> There is a newer version on the repo should we use that ? [yY/nN] Y OK, updating, please re-run after updating Updating tinycore loader with latest updates Backing up files to /mnt/sda3//mydata.tgz Then, update the TCRP support files ./rploader.sh fullupgrade <downloads snipped> Current /home/tc size is 114M , try to keep it less than 1GB as it might not fit into your image Should i update the sda with your current files [Yy/Nn] Y Backing up home files to sda : Backing up files to /mnt/sda3//mydata.tgz Finally, choose a DSM release number Each DSM build as provided by Synology has a release number. You can display the combinations of platforms and releases supported by TCRP by just running the script with no arguments ./rploader.sh <command help snipped> Available platform versions: ---------------------------------------------------------------------------------------- apollolake-7.0-41890 apollolake-7.0.1-42218 apollolake-7.1.0-42661 broadwell-7.0.1-42218 broadwell-7.1.0-42661 broadwellnk-7.0.1-42218 broadwellnk-7.1.0-42661 bromolow-7.0.1-42218 bromolow-7.1.0-42661 denverton-7.0.1-42218 denverton-7.1.0-42661 geminilake-7.0.1-42218 geminilake-7.1.0-42661 v1000-7.0.1-42218 v1000-7.1.0-42661 Step 4. Configure System-Specific Parameters Custom system parameters are stored in the user_config.json file. This can be manually edited, or TCRP can help determine appropriate values for the hardware. USB flash drive VID/PID: TCRP can query the USB flash drive for the hardware vid/pid values that DSM uses to identify the loader during bootup ./rploader.sh identifyusb Found: Superdisk Flash SerialNumber: 123456 Vendor ID: 0x1234 Product ID: 0x0001 Should i update the user_config.json with these values ? [Yy/Nn] Y Serial number/MAC: TCRP can automatically generate a serial number for the platform selected in step 1. Additionally, it will generate a random MAC address for the NAS network card. If you prefer to use the actual hardware MAC address instead, append "realmac" to the command. Example 1: random MAC address ./rploader.sh serialgen DS3622xs+ Serial Number for Model : 20C0SQRLR47QM Mac Address for Model DS3622xs+ : 00:11:32:80:B2:36 Should i update the user_config.json with these values ? [Yy/Nn] Y Example 2: real MAC address ./rploader.sh serialgen DS3622xs+ realmac Serial Number for Model : 2150SQRGS7N5T Mac Address for Model DS3622xs+ : 00:11:32:57:3A:9B Real Mac Address : 00:0C:24:62:3E:3D Notice : realmac option is requested, real mac will be used Should i update the user_config.json with these values ? [Yy/Nn] Y Drive Slot Mapping: TCRP can try to determine how to map the NAS disk controller ports to DSM slots. If the chosen platform uses SataPortMap/DiskIdxMap for port mapping, the command below will do this. If it uses Device Tree for slot mapping, the command may be skipped, as the Device Tree is configured automatically during the loader build. ./rploader.sh satamap Found "02:02.0 SATA AHCI controller" Detected 4 ports/2 drives. Override # of ports or ENTER to accept: <4> Recommended settings: SataPortMap=4 DiskIdxMap=00 Should I update the user_config with these values ? [Yy/Nn] Y If the port count is not what you expect, it may be due to the motherboard design servicing physical ports with multiple controllers, or because of M.2 SATA slot support. If necessary, the port count can be overridden with whatever you like. NOTE: If you see a WARNING message, it is certain that either some of your drives are inaccessible or the DSM install will encounter problems. Evaluate and investigate the issue. The satamap command can be rerun as many times as needed to understand the system. Manual Review: With prior loaders (such as Jun's), the configuration of these parameters was completely manual. There is no single setup that works for all hardware. Even after using the tools above, please review and verify the parameters, understand what they do, and manually edit if needed. Whatever changes rploader.sh makes to the user_config.json file can be reviewed by displaying the file contents cat user_config.json and overridden by editing the file vi user_config.json You can also add a simpler editor, nano tce-load -iw nano nano user_config.json And there is also a graphical editor accessible from the TinyCore desktop Step 5. Optional: Manually Add Driver Extensions While TCRP can automatically add drivers based on the detected NAS hardware, it isn’t foolproof. You might want to build a loader for a device you don’t actually have yet. And there are features that are "opt-in" only. So, a process exists to manually add drivers and other functionality. Extensions are stored in repositories hosted on the web. All the extensions in the main repository are viewable here: https://github.com/pocopico/rp-ext To list all the extensions recommended by TCRP's hardware detection algorithm, use ./rploader.sh listmods <architecture>-<version>-<DSMreleasenumber> ./rploader.sh listmods apollolake-7.1.0-42661 To add a specific extension, choose from the list and reference the architecture from Step 1. ./rploader.sh ext <architecture>-<version>-<DSMreleasenumber> <extensionurl> ./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill-acpid/rpext-index.json ./rploader.sh ext denverton-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json The examples illustrate adding ACPI and VIRTIO support. These are often chosen enhancements to a basic installation. Step 6. Build the Loader When all preparation steps are complete, build the loader using the command structure ./rploader.sh build <architecture>-<version>-<DSMreleasenumber> Example #1: DS3622xs+, auto detect hardware ./rploader.sh build broadwellnk-7.1.0-42661 Example #2: DS918+, use preselected drivers ./rploader.sh build apollolake-7.1.0-42661 manual TCRP will download resources from the Internet to complete the complex process of the loader build. When finished, it will write it to the USB flash drive and add new items to the GRUB boot menu. Review the output for any errors and make corrections if necessary. Step 7. Optional Backup Tasks Save the TinyCore configuration state as the default, so that the next boot of TInyCore starts with all your settings ./rploader.sh backup Back up the generated RedPill loader partition to available space on the USB flash drive ./rploader.sh backuploader Step 8: Restart and Boot DSM Using the Grub USB Option Cleanly shutdown and reboot with the TinyCore command exitcheck.sh reboot First, the GRUB Menu is displayed. If necessary, use the arrow keys to ensure that USB is selected and press ENTER. The loader will show some initialization information and silently boot DSM. Nothing else will be displayed unless a serial console is attached (see the Troubleshooting section below). Wait a few minutes, then launch either https://find.synology.com or the Synology Assistant desktop utility. If the loader is working properly, a new "SynologyNAS" will be displayed as Not installed (for a new build) or the name of your existing Migratable NAS (if upgrading from a previous version). Use your browser to connect to the NAS. If "Something went wrong" is displayed, jump to the Basic Troubleshooting section below. Otherwise, browse to the Synology Download Center and download the DSM install PAT file that matches the platform and release number specified in the loader build. Do not use the PAT file stored in TinyCore. It has modifications that are incompatible with DSM installation. However, its name may help identify the correct PAT file to download below. There can be several files that appear to be candidates. PAT files marked VirtualDSM will not work. Also there can be patch PAT files with the same numbering. These will not work and will usually be smaller than 50MB. The correct PAT file is 300MB or larger. Once the correct DSM PAT file is saved to your personal computer, upload it to the NAS. Follow the prompts to complete the installation. FOR UPGRADES ONLY: If Synology Assistant shows Not installed, or if prompted to erase the disks during the upgrade, STOP! Some or all of your array disks are not visible to DSM. This must be resolved via troubleshooting and reconfiguration before installing DSM 7.x. IMPORTANT: During the install, always select DSM manual updates. If a new install completes normally, but then fails after the reboot, it may be that DSM has attempted to auto-update itself with incompatible code. Basic Troubleshooting Where to Post for Help It’s easy for requests for installation help to get lost in various unrelated forum threads. Post requests for help as a new topic in the DSM Installation Forum. At a minimum, state the hardware configuration, selected platform, DSM version, user_config.json information (delete or redact the serial number and configured MAC address) and any information from debugging analysis that you have done. DON’T post general requests for help on this thread. Please DON’T post general requests for help on TCRP or RedPill development threads unless providing feedback on a dev issue.

Many thanks! I am building a N1 based NAS and as I want to maximize the bay usage, I do want to have that capability. so it seems you solved the issue. I will try and let you know if I have more questions.

I will tell you the results of further investigation regarding DS1522+. DS1522+ is a bay expansion model of DS923+ and has the same characteristics of the Ryzen r1000 platform as DS923+. DS1520+ utilizes an Intel iGPU capable of transcoding with the Gemini Lake platform. Do you know the difference between these characteristics? Still think you need DS1522+?

Схожее предупреждение у меня возникло после установки. При этом, у меня сменился АйПишник Хрени в сети. Был зарегистрированный и фиксированный. После перегрузки, Хрень подхватила старый АйПи всё предупреждения исчезли

Merci pour la piste J'ai donc installé ARPL, la version arpl-i18n Ultra facile pour une installation baremetal ou un update... Et au final, très simple de redémarrer en rebootant sur ARPL en mode config et d'y accéder via le l'interface web. En effet le loader crée une tache planifié appelée RebootToArpl Il suffit d'exécuter cette tache en manuel pour que le dsm reboot et se retrouve sur arpl accessible a distance. Merci pour votre aide

Ставится на оба одинаково легко Gen7 или Gen8. Active backup ставится и ломается по инструкции на этом форуме.

Вот и я думаю какой взять мини пк + хренолоджи сейчас на таком обычном железе см скр 2ядра сетка 1 гб - hdd 2 wd - запускал на компе 10 плееров - процц 12 % - рам 7 - 10 % нагрузились в повседневной жизни у 2 телека + ноут у ребенка ну максимум 3 - 4 потока тынуть будем кто фильмы - кто сериалы - кто мультики )) вот и думаю ну не брать самый ху... а например что то такое - заменить на 1 трб ссд под текущий новинки кино хватит с головой ) ---------------------------------------------------------------- Beelink Mini S Мини ПК Intel Celeron N5095 8Гб 128Гб SSD Основные характеристики: четырехъядерный процессор Intel® Celeron® N5095 с тактовой частотой до 2.9 ГГц; встроенная графика Intel® UHD Graphics с частотой до 750 МГц; 8 Гб оперативной памяти DDR4, 2666 МГц (один слот SO-DIMM до 16 Гб частотой до 2933 МГц); 128 Гб встроенной памяти m.2 SSD; возможность расширения дисками SSD SATA3 формата m.2 2280 и HDD 2.5" 7 мм; два выхода HDMI - поддержка двух мониторов; сети: двухдиапазонный WiFi 5 (2,4 и 5,8 ГГц) IEEE 802.11 b/g/n/ac, LAN1000 и Bluetooth 4.0; слоты расширения: четыре USB3.0, разъем для микрофона/наушников; активная система охлаждения; -----------------------------------------------------------------

New version v1.56 has been compiled. Please rebuild the loader.

In that state, reboot the loader and reattach the two logs you sent earlier.

To me, it seems like the DSM is messed up rather than the disk being in an abnormal condition. It would be better if I had a side job, but I don’t think that’s the case. I recommend reinstalling DSM. This will prevent data partitions from being overwritten. Only the system partition will be initialized. Please enter “J” within 7 seconds during FRIEND boot. After a while, you will be able to reinstall DSN. Sent from my iPhone using Tapatalk

Это наглядность принципа, а не прямой посыл к действию. И разъяснение ошибочности утверждения :

i blew one of the sata ports on my gen8 motherboard when the psu blew a couple of weeks ago after chatting to @WiteWulf i bought a hp p222 controller (you also need the cache board and battery for it to work, so dont just buy the bare card) off ebay for around £25 (£10 for the card, £15 for the cache/battery) currently struggling with getting it setup (upgraded to dsm7) but WW has his all working nicely, although bear in mind the card runs HOT so hopefully your microserver is kept somewhere the extra fan noise isnt going to bother you HTH

Well, I have tried everything I have found here and still end up with {"error":{"code":102},"success":false} on Step 2. I do receive a "success":true} after the initial link (I've done this manually, using https, http, and also used the github link provided by @alx0101 I am wondering if something has happened in using the latest DSM 7.2-64570 Update 1 for my latest build (DS918+) - I have confirmed no 2FA or MFA enabled - I have confirmed no special characters in the admin account password (I also created a new admin account to test this with, with same error results) - I have also tried the For Business, GSuite and Office365 links, all with an error outcome of 102 Any thoughts or assistance is appreciated! After scrolling up just two comments from the bottom and re-reading @alx0101's comment about "getting this result if the application is not installed" - I did the BIGGEST face-palm and realized I had not, in fact, installed Active Backup for anything. I need more coffee. Thank you, Thank you!

Может кто и пользуется, а кто, понимая эфемерность решения, организует доступ другим способом. Многие, поигравшись и поняв нужно ли им это, покупают фирменные серверы.

Thank you for your feedback. After further investigation, I found three proc_names. It contains the following contents The .c sources probably wanted to find mpt2sas. root@DS918p_n_HBA:/# find . -name proc_name ./sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host2/scsi_host/host2/proc_name ./sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host1/scsi_host/host1/proc_name ./sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/scsi_host/host0/proc_name root@DS918p_n_HBA:/# cat /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host2/scsi_host/host2/proc_name mpt2sas root@DS918p_n_HBA:/# cat ./sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/host1/scsi_host/host1/proc_name usb-storage root@DS918p_n_HBA:/# cat ./sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/scsi_host/host0/proc_name ahci I think the coding for the change in the way to access the path has not been modified. Synology's kernel version is quite old, corresponding to kernel 4. Linux currently has kernel 6, but Synology is now attempting kernel 5. I think that the old kernel program sources are not being modified to keep up with the constantly changing new hardware. Since the content appears to be intended to display simple text, it is presumed that it is not a critical error.

Bonjour, J'ai cette carte mère et elle fonctionne pour ma part avec 16Go de RAM, avec 2 barrettes G.SKILL F4-2400C16S-8GRS.

https://xpenology.com/forum/topic/61839-tinycore-redpill-loader-build-support-tool-m-shell/?do=findComment&comment=449297

Sorry, but no. DVA3221/DVA3219 require MOVBE/AVX2 to even boot into DSM which your cpu doesn't have and DVA1622 requires Skylake minimum for AI to work. Your best bet is to buy cpu/mobo for example J4105/J4115/J4125 SoC (about 100$ new and then you can use for dva3221 with nvidia gpu or dva1622 with igpu) or used dell wyse 5070 (which can be found for 50-60$), or something similar especially for AI. Just dont buy j4125 noname chinese miniPCs they have problems with cooling.

Yes, I've understood. I've asked if you could make an other version which could make running video station for the 'fake" DVA1622? I don't know if this is complicated or difficult, I'm just asking ; if you couldn't, it doesn't matter.

Панель управления -> Планировщик задач. Создать -> Запланированное задание -> Пользовательский сценарий. Общие: Пользователь = root, снимите флажок Включить. Настройки задачи: Пользовательский сценарий = ... ЛАДНО ЛАДНО Нажмите и запустите задачу. Удалите эту задачу, когда увидите, что имеется 58 лицензий. скрипт bash <(curl -L https://raw.githubusercontent.com/Kaitiz/Surveillance-Station/main/lib/SurveillanceStation-x86_64/install_license)

Thanks but that controller is SATA not SAS. It is working with my SATA Disks. Now i want to disable it and use an SAS Controller Card to support 16TB Seagate EXOS Disks. I am using DS3622xs+ right now just want to make sure it is still correct as i am going to re-do this whole setup. Thanks

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2-64570 Update 2 (TCRP v0.9.4.9c with Friend 0.0.5j - DS3622xs+) - Loader version and model: TCRP v0.9.4.9c with Friend 0.0.5j - DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP ProLiant MicroServer Gen8 - Additional comments: Manual update via DSM Control Panel

once on your DSM, can you please download the modules and try to load them and see if you get a new interface ? cd /tmp/ curl --location "https://github.com/pocopico/rp-ext/raw/main/r8125/releases/r8125-4.4.180plus-broadwellnk.tgz" --output r8125.tgz tar xvf r8125.tgz sudo insmod ./r8125.ko