Search the Community

Hi! Since I could not find any actual (updated) post guiding on how to use the updated loaders for Xpenology, and since I am NOT using Proxmox (I rather not have the overhead and don't need the extra abilities for now), I would like to present to all noobs and Xpenology enthusiasts starting out on this really cool journey, my guide on How-to create a Synology-like NAS machine (First a short-hand version, and after, the full version): Get a Bare metal PC/NAS build. Download your desired Loader. RR/ARPL, and ARC are the common options. Burn the loader onto a fast USB flash drive. Setup your Bare metal PC Bios boot order to load your USB flash drive FIRST. Plug said flash drive into the PC, and boot Select model and version Select and add addons and configure them as necessary Build the loader Boot the loader Enter the DSM via the supplied web IP address And here is for the meat and potatoes of it: You'll need a bare metal setup. You've probably heard the term before, but basically it means a constructed PC, almost any PC, without an operating system installed (so a virgin , one HDD/M2 NVME/SATA NVME storage at the minimum, to install the DSM environment). As for recommendations for what to use? It depends on your requirements really. Synology/Xpenology Machines are quite versatile, especially when you build them on a (more) powerful basis. But the range is Huge. You can get away with an ancient platform such as i7-26xx based PC, or go all the way to 12th-13th-14th gen CPU (although it is less recommended due to compatibility issues and drivers support). The sweet spot, for me, is 7th-9th gen CPU platforms. If you wish to save power, go for a "T" CPU (desktop CPUs with T at the end of the model name, are using much less power. Usually around 35W vs 65W-140W of the more powerful Intel CPUs). Once you have an assembled PC, you can head over (on another PC unless you have a temporary windows installation on the bare metal machine) to download the Loader. The Loader is as it says - a way to load the DSM - which is the Synology Operating system. Nowadays, there are basically two automated loaders (automated as they save you from having to work harder on building your specific loader for your requirements): RR/ARPL, and ARC. Both work in a very similar way that will be explained soon. You go to the releases section on the right of the page, and download the latest version. For instance: arc-24.5.26.img.zip for ARC, or rr-24.5.5.img.zip for RR. Then you will unzip the image from the zip file. you'll get a file with the suffix img. Next, you will need to use a program such as Rufus, or Belena Etcher to "burn" the img file you got, into a USB flash drive. I find Belena Etcher is simpler for that, but Rufus would work just as well. The resulting flash drive will have 3 partitions that may not be read by your windows PC. That's totally normal and fine. It will still work and boot. Do make sure you have at least a 16GB/32GB fast flash drive, as I have heard of slower (USB 2.0) flash drives that will simply not boot properly. Also, remember that the loader runs directly from the flash drive. NOT from your PC hardware. There are some workarounds, but I see no issue in keeping it that way. I simply use a fast tiny drive such as Samsung fit. Turn on your new NAS PC and go into bios (usually it's Del or F1/F2/F12 to enter bios). Then go and find the Boot order and make sure that your USB flash drive is set to boot first. You can disable any other boot drive/network (You will boot from the flash drive in any case for an Xpenology machine). Save the changes in the bios, and shut down. Then, plug in your flash drive if you haven't already, and turn the PC on again. You should get this screen after it boots: If your PC does not have a video card (integrated or discreet), you can still access the output using your network. You will need to find out what IP the machine will use, so you still might need to have a video card just to find that first.. But there are network sniffers out there like wireshark that can also scan your local network and find what new IP connected to it. So, in this example, you can see on the top of the image, a line with some information. When you first boot, this line will be shorter, as no DSM model or version will be selected yet. But once you select a model and version, the information will reflect on that top line. The menu shows you many options. We start with "choose a model": This list is MASSIVE and daunting! So which model should you choose?? Well, that's the million dollar question. If you go to Synology's website you can see all the models and some information about each. They are to match a person's budget and requirements. Some are more for office use and some are even for (up-to) mid-sized companies. There are also NAS models that are meant for video surveillance. Those are usually with "SA" at the start of the model name. Whichever model you choose, you can see some extra text next to it. That indicates the original hardware base used in the actual Synology Device. So, "r1000" for instance indicates AMD based hardware. You can find out more information regarding that here. However, it doesn't really matter. Your hardware may differ A LOT from the original hardware in a Synology machine, but the Xpenology loader you use will bridge any (or at least most) such differences, and allow your machine to work. I did find that some models do work better with my hardware than others, but I can't give you specifics as your hardware may be quite different than mine. After you selected a machine model (move with keyboard arrows and then navigate with tab and click ok), we move to the version selection (on the first screen): Optimally, you will want to select the newest product version (naturally), but if you are using especially old hardware, you might want to opt for an older version. As you can see, with this newest loader version, there are only two options. If you want older ones, you might have to get a older loader to match. Once you select it and click ok, you'll get this screen: and click ok as well. Then you are back again to the main screen. Next go to addons: Here you can select some addons you may want to add before you build your very own loader image. You can see the list by choosing "show all addons" Interesting ones are: hdddb for better compatibility with non listed hard drives and other storage (no parameters needed), cpuinfo for correct showing of your hardware in the DSM control panel info screen (again, no parameters required unless your info is not found correctly or automatically, in which case you can enter it manually), i915le10th which is to allow support for intel integrated graphics solutions (up to and including 10th gen Intel CPUs) - but only on certain models, as not all Synology models support integrated CPUs (they are mostly used for video transcoding), nvmecache which is to allow usage of your M2 NVME to be used as a cache to accelerate read/write speeds (you will need to create a SSD Cache inside your machine for this to work and use SSD advisor), sensors which are to report temperatures of your pc parts (hard drives, CPU, case fan and so on) - from my experience it does work too well, but will give you necessary information regarding your storage temperatures which is VERY important), and last is storagepanel which allows you to change the visible model/size in your DSM. What do I mean? Say you picked a simple DS224+ model which is a modest 2-Bay synology machine, but you are actually running 5 hard drives and one M2 NVME. If you don't make changes under storagepanel, all you'll see is a two bay model in your DSM (you will still be able to use all 5 disks). In order for the DSM interface to reflect your hardware correctly, you will enter the proper choice in parameters (when it is asked when you add this addon). In this case you will put TOWER_5_Bay 1X1 which indicates a similar Synology model, but one with room for 5 disks. It will actually put a photo of such a device for you to see when you log into the DSM. So the first part (TOWER_5_Bay) is to indicate the type of the model (tower) and how many bays. The second part (1X1) indicates how many M2 NVME devices are there. So, if you have two M2 NVME devices, it would be 1X2 instead. However... be mindful that there is a list of possible items that you can put in (other than TOWER_5_Bay and so on), which is (as far as I know): TOWER_4_Bay 1X4 # RACK_0_Bay RACK_2_Bay RACK_4_Bay RACK_8_Bay RACK_10_Bay RACK_12_Bay RACK_10_Bay_2 RACK_16_Bay RACK_20_Bay RACK_24_Bay RACK_60_Bay TOWER_1_Bay TOWER_2_Bay TOWER_4_Bay TOWER_4_Bay_J TOWER_4_Bay_S TOWER_5_Bay TOWER_6_Bay TOWER_8_Bay TOWER_12_Bay This list is actually inside a storagepanel.sh file (a script file) from the loader installation itself. I don't recommend trying values that are not in this list as it may just cause issues. Another thing I noticed is, that if you select a RACK model (such as SA6400 for instance), you can only use a RACK value. It simply won't let you put in another (such as a TOWER value). At least it didn't let me. If you don't change the storagepanel value, you'll get a default picture. Which may be a 24 bay rack.. Okay. So once you have added each of the addons you want, you go back to the main menu, and click on "Build the loader". This will take a while (can be a few minutes at least), once it is done, it will again go back to the main menu, and you can click on "Boot the loader". That will give you a screen where the DSM is booted, and after a minute or two you'll get something like this: This is the Loader boot up screen. As it mentions in the yellow text that will appear after a bit, you will need to go into your DSM interface after a few more minutes via https://x.x.x.x:5000 (where x.x.x.x is your NAS IP address - same as the loader IP address, but on port 5000 rather than on port 7681 as the loader) I hope you find it useful and easier to install the new loaders with this guide. I wish I had one like this to avoid some of the pitfalls along the way. Cheers!

Install DSM 7.2 on FreeBSD using vm-bhyve and TinyCoreRedPill This guide is for installing DSM 7.2 on a Virtual Machine with a Virtual Disk using bhyve with TCRP Friend kernel. To make this guide I used the main TCRP Guide, the ESXi Guide and I got most of my conf file from this Bhyve Guide. I didn't explain much, just some vm-bhyve relevant info, more in depth explanations can be found in those guides. I used DSM 7.2.0-64570 and DS3622xs+ My CPU is Xeon so I used DS3622xs+ Download site for DSM 7.2 for DS3622xs+. Direct link to download DSM_DS3622xs+_64570.pat Link to Tiny Core RedPill Releases. I used the uefi img tinycore-redpill-uefi.v0.9.4.9.img.gz Step 1 - (Config file) After bhyve is installed use this "synology.conf" config file below. It goes in with the rest of the vm-bhyve config files poossibly at "/pool/vm/.templates" directory. synology.conf loader="uefi" cpu=8 cpu_sockets=1 cpu_cores=4 cpu_threads=2 memory=16G ahci_device_limit="1" disk0_type="ahci-hd" disk0_name="tinycore-redpill-uefi.v0.9.4.9.img" disk1_type="ahci-hd" disk1_name="disk0.img" disk1_opts="sectorsize=4096/4096" disk1_size="10T" debug="yes" network0_type="e1000" network0_switch="public" graphics="yes" xhci_mouse="yes" graphics_res="1600x900" Notes: Network type "virtio-net" driver did not work for version 7.1.1-42962 and I did not try it yet with friend, so I still used the e1000 driver instead. I also have not tried "virtio-blk" and "sparse-zvol" recently. Step 2 - (Create VM) Create a VM named "synology" using the template synology.conf sudo vm create -t synology synology This creates two empty files, or two disks in the /pool/vm/synology/ directory. disk0 named "tinycore-redpill-uefi.v0.9.4.9.img" - the boot disk. disk1 named "disk0" - data disk. I named the disk0 "tinycore-redpill-uefi.v0.9.4.9.img" because now the actual TCRP disk file needs to be copied to the VM directory to overwrite the empty disk with the same name. Deflate the img.gz file using "gzip -d tinycore-redpill-uefi.v0.9.4.9.img.gz" Copy the downloaded disk img file to the VM directory sudo cp /pool/vm/.iso/tinycore-redpill-uefi.v0.9.4.9.img /pool/vm/synology The config file uses UEFI bootloader and graphics so the VM will run on a VNC port. Step 3 - (Start VM) Start the VM sudo vm start synology This will start the VM and boot the TCRP disk since TCRP is in the first place, the disk0 place. The disk1 is just named "disk0" but it still comes at second place after the TCRP disk. Step 4 - (Booting TCRP) Boot will have one option. When TCRP boots get the IP info by running "ifconfig" ssh into it with user "tc" and password "P@ssw0rd". Step 5 - (Install DSM) Below is the commands needed to install DMS from the TCRP Loader Guide. Type "y" and hit enter to update the json file. One important point is to use "realmac" when running DSM in a VM as explained in the ESXi Guide . On "satamap" command type number "1" and hit enter. You can also just hit enter but if you hit enter without typing 1 it will say DSM install will fail but it does not fail. Probably because it's a VM. ./rploader.sh update ./rploader.sh fullupgrade ./rploader.sh serialgen DS3622xs+ realmac ./rploader.sh satamap ./rploader.sh build ds3622xsp-7.2.0-64570 exitcheck.sh reboot After reboot: When TCRP boots choose "Tiny Core Friend" option, hit enter to boot. That option will be selected by default. Then go to https://finds.synology.com/ and hit connect, or you can see the IP from Friend and add port :5000 to the IP. Click install. Select to manually upload the DSM pat file you downloaded earlier (DSM_DS3622xs+_64570.pat). Wait up to 10 minutes. DSM will install packages. After you create an account select not to auto update DSM but to install them manually. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Notes and things I noticed: Without Friend using tcrp 0.9.4.2 I was able to install version 7.1.1-42962 by choosing the SATA option, but SATA option did not work for newer versions. I did actually install the latest version (7.2.0-64570) at first with SATA option but then after DSM is done it says "something went wrong" and it wants to rebuild, but then if I force shutdown the VM and start it again but with Friend option Synology continues to install the packages and installs. After DSM is installed SATA option also works as well as Friend option. While back I tried to manually update from version 42661 but it failed, but then I didn't have Friend. ----------- If someone has additional useful things regarding vm-bhyve let me know.

This tutorial is a supplement to the ESXi TCRP installation tutorial located here: https://xpenology.com/forum/topic/62547-tutorial-install-dsm-7x-with-tinycore-redpill-tcrp-loader-on-esxi/ Installing DSM 7.1.0.-42661 on UNRAID 6.10.3 I have been trying to install DSM 7.1 on my unraid server for the last night. After some problems and testing I have created this guide to install DSM 7.1 on UNRAID working perfectly. This is my vm config: STEP 1-Virtual machine creation: Download tiny core from https://github.com/pocopico/tinycore-redpill Select CentOS VM Template and apply correct options from the attached image. Select Q35-6.2 Select 3.0 (qemu XHCI) Load tiny red core as vdisk1 USB by selecting manually (you can create previously the name of the folder for the VM inside /domains and upload the tinycore img ) Create secondary disk 50G or whatever you want (this is your data storage for synology) as vdisk2 SATA Select Network model: e1000 Save. Uncheck "Start VM after creation" Edit again vdisk2 in the advanced xml template (top right corner) to controller='1' (if we don't do this tiny red core will not detect the disk properly when doing the satamap and will not install DSM correctly and will ask you to reinstall the *.pat infinitely) STEP 2-Start VM and connect via SSH Start VM and load tiny red core Once the OS is loaded, open the terminal and enter ifconfig to find out the ip of the machine Connect via ssh (with Putty) to the obtained IP address. user: tc password: P@ssw0rd STEP 3-Run the following commands: To update tiny red core with the latest data ./rploader.sh update now ./rploader.sh fullupgrade now To generate random mac and serial numbers (copy mac address generated to set on unraid vm template later) ./rploader.sh serialgen DS918+ (or whatever version you want, you can see all versions available with command info ./rploader.sh) To map the connected disks ./rploader.sh satamap now To record the vid/pid from usb ./rploader.sh identifyusb now To install NIC drivers (sometimes it loads the e1000e module instead of the e1000 and it doesn't work, adding this command will make sure that the e1000 module for the NIC is loaded correctly) For e1000 Network Card run: ./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/e1000/rpext-index.json NOTE: change version according your selection for CPU and DSM version For virtio-net Network Card run: ./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json NOTE: change version according your selection for CPU and DSM version To build the image ./rploader.sh build apollolake-7.1.0-42661 STEP 4-Download your .pat for your correct cpu architecture from official repo or mega download for this version apollolake , we will need it to install DSM later. https://global.download.synology.com/download/DSM/release/7.1/42661-1/DSM_DS918%2B_42661.pat - Offical repo STEP 5-Edit VM settings on advanced xml mode and install *.pat After doing all the above we shut down the machine. Edit the virtual machine on xml advanced mode (if we change mac address in normal editing mode you will lose controller="1" option set for vdisk2 we did previously so you will have to set it again everytime you change and/or save a setting from normal mode, try to edit always in xml advanced mode), look for MAC address and set the MAC generated by tiny red core. Save Start VM Select the first option USB and leave it a few minutes until we find it with synology assistant Open WebGui and install *.pat We now have DSM 7.1 working on unraid. There is other method with SATA boot but I have to test it better. Hope this guide help someone. Regards.

This guide is dedicated to installing DSM 7.0.1 BareMetal. It is a translation from Korean to English using a translator. Please understand if there is a slight misunderstanding. Existing RedPill, which has been released since last year, can generate IMG files directly through the bootloader compilation process only if Linux is available separately. This tinyCore RedPill provides a USB boot image with tinyCore Linux. It's much easier to work without having to install Linux separately. As usual, you can add the desired driver directly from the selection header and build it. Tinycore supports the following platforms (DS918+/DS3615xs/DS3617xs/DS3622xs+/DS1621+/DV3221/DS920+). You can continuously change the bootloader without re-creating the image (model/sn/mac, etc.) Tinycore supports both legacy versions for baremetal and virtual environments. 1. Prepare bootloader IMG file With the Download button in the middle of the GITHUB link below.Download the gz file. In it, 0.4.6 version img.You can unzip the gz file again and use the img file. (All files) https://github.com/pocopico/tinycore-redpill (for LEGACY) https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.4.6.img.gz (for UEFI) https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill-uefi.v0.4.6.img.gz (for VMWARE) https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.4.6.vmdk.gz 2. Bootloader IMG file USB recording Use the above tinycore-redpill.v0.4.6.img file to burn to USB with convenient image tools such as WinImage and Rufus. There is no need to pre-adjust the configuration file to modify the VID/PID/Serial/MAC/SATAPortMap like JUN loader. If you want to create a USB image on Mac or Linux, you can use the following DD command at the terminal. (Suppose the USB DEVICE ID identified by diskutil is disk4) sudo diskutil unmountDisk /dev/disk4 sudo dd if=/Users/MyAccount/Downloads/tinycore-redpill.v0.4.6.img of=/dev/disk4 bs=4m agree eject. 3.tinyCore Linux Boot USB boot by plugging into the PC you want to use as XPENOLOGY (you can start using UEFI 1 partition or USB CSM) Only TinyCore Linux menu appears and runs automatically Start the terminal app on the far right icon. Use the ifconfig command to verify the ip address where the en0 LAN card is automatically allocated. 4. CONFIG adjustment after SSH connection Connect ssh from another PC, such as putty. ( id:tc / pass : P@ssw0rd ) After connecting, update to the latest version with the following command. tc@box:~$ ./rploader.sh update now Tinycore Redpill is still in a stable state of stabilization. PocoPico, the developer of this program, will frequently fix bugs and announce rebuilding. There's a possibility that this rebuild will happen from time to time. Even if you use the first IMG file version of 0.4.6, you can continue to receive real-time updates of changes through the Internet. Therefore, before using it for the first time, please make sure to download the final patch status with the update option. If you've continued to migrate from JUN's XPhenology, tc@box:~$vi user_config.json The user_config.json file's VID/PID/Sn/Mac/SataPortMap, etc. are existing grub.Please refer to the cfg and insert it as it is. For new installers, perform serial GEN/USB VID, PID auto detect, SataPortMap auto detect, etc. as follows. The next process is DS3622xs+, which is currently undergoing the most stable session first. I will focus on explaining. tc@box:~$ ./rploader.sh serialgen DS3622xs+ tc@box:~$ ./rploader.sh identifyusb now tc@box:~$./rploader.sh satamap now (HBA card users are not required) You can see that the contents of user_config.json are changed automatically. Finally, it is common for existing users and new installers. tc@box:~$catuser_config.json, assuming there are 4 built-in sata ports. SataPortMap = "4", DiskIdxMap = "00" Please check if it is changed to the back. After find.synology.com, you may not be able to find the SATA HDD during DSM installation. The following is an example when a 6-port SATA expansion card is installed. SataPortMap = "46", DiskIdxMap = "0000" (For those who use cards such as H200, H310, H710, etc., exceptional, you do not need to erase the option of this SataPortMap and DiskIdxMap itself. Please erase the lines of the above two options in the vi editor and organize them well so that they don't end with Syntex errors. Of course. ./rploader.sh satamap now command is not required.) 5.BIOS built-in SATA port Hot Plug disable -> enable (important) To avoid temporarily reducing the SataPortMap value set above by the number of HDD physically connected by Sata cable during DSM installation, Be sure to turn on the Hot Plug function. This reduces the probability of encountering an error message saying that the HDD cannot be found because the number of SataPortMap automatically above is recognized as normal recognized. However, if M.2 and Sata ports are Muxed Sata ports that share Lane, it should be considered unusable. 6. Build bootloader after SSH connection When you have finished adding the above extension driver, you will finally build the bootloader. tc@box:~$ ./rploader.sh build broadwellnk-7.0.1-42218 The list of supported platforms can only be found in Help with the following commands: tc@box:~$ ./rploader.sh 7. backup and reboot for bootloader use After successfully completing the build, back up the configuration with the following command and restart the genology with USB. tc@box:~$ filetool.sh -b &&/usr/bin/exitcheck.sh Or tc@box:~$ ./rploader.sh backup now tc@box:~$ sudo reboot It has the same effect. The backed up settings and ext drivers remain the same. The next time TinyCore Linux starts for correction, the setting value will be restored from the mydata.tgz file. 8. Launch the Grub Menu BareMetal must select the first USB boot menu. The first USB menu will be automatically selected. The last selected menu will be stored and used for the next boot. 9. Installing DSM with find.synology.com On an XPhenology PC, There is a delay of about 1 to 2 minutes for IP allocation, so please wait a little longer. There is nothing more to do on this XPhenology PC once you have checked the Kernel boot message. Now look for XPhenology on another PC at find.synology.com. If found successfully, proceed with the initial installation of DSM or the expected migration DSM installation process.

Hello I installed Contao CSM 4.9 in DMS 6.2.1-23824-6 (DS918+) successfully and I would like to share this guide How to install contao 4 in synology 6.pdf that describes all necessary steps with all of you are interested in it and you are willing to make this kind of advanced modifications of the DSM configuration by yourself and at your own risk. Best regards