Search the Community

Generally you should add a sataportmap entry for each controller. The current TCRP code will recommend this. The only case not to do so is the >9 port card as you have described. This is dependent on a lot of factors, whether you are trying to use SATABOOT etc. Script enhancement should help folks move their configurations to a more predictable space. Testing across the various hypervisors is inconsistent, so there may be some work to do there.

So do not add any sataportmap for the last listed pci sata controller and it should use all available ports. Good to have that confirmed. I did exactly that in a vm build using a HBA (8 port) adapter in proxmox. However the disk ordering started at 2, I could never get the disk ordering to start at 1, even though the hba card is the only available sata controller which is being pci pass thru. It listed all the hdd but starting at 2 (not at 1)

The "16" in 616 is invalid. SataPortMap is only one digit with a maximum of "9" This is not good for LSI9201-16i obviously. However, SataPortMap = "1" should probably work for you to use 17 HDD. Specifically, if the last PCI controller (must be actually the highest PCI slot) has >9 ports, you can leave that entry on SataPortMap blank and it should use all the ports. I would advise maxdisks of 24 instead of 36 (internalportcfg must be modified accordingly).

1.This is a shell script that executes several commands at once as described in the "Redpill Tinycore Loader DSM 7.1 Build" guide. To use, you can download and untar it as follows and use it in the /home/tc directory. Helps build DSM 7.1 by managing the PAT file directory required for decryption. ( It currently supports the latest version of the DSM, 7.1.0-42661 update 1 nanopack version. ) Automatically add mac2 to user_config.json file for dual NIC, a feature that TC doesn't have. ( Manual Response Version ) wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/m.sh.gz; tar -zxvf m.sh.gz; ( Auto Answer Version with y ) wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz; tar -zxvf my.sh.gz; Where y is unnecessarily asked, it automatically responds. Usage: ./my.sh <Synology Model Name> <Option> <Option> <Option> Options: noconfig, noclean, manual - noconfig: SKIP automatic detection change processing such as SN/Mac/Vid/Pid/SataPortMap of user_config.json file. - noclean: SKIP the 💊 RedPill LKM/LOAD directory without clearing it with the Clean now command. However, delete the Cache directory and loader.img. - manual: Options for manual extension processing and manual dtc processing in build action (skipping extension auto detection) Please type Synology Model Name after ./my.sh ./my.sh DS918+ ./my.sh DS3617xs ./my.sh DS3615xs ./my.sh DS3622xs+ ./my.sh DVA3221 ./my.sh DS920+ ./my.sh DS1621+ # Update : add noconfig, noclean, manual combination options # 2022.05.06 You can use it like this. ./my.sh DS918+ noconfig noclean manual ----------------------------------------------------------------------------------------------------- 2. Deploy scripts that you can leverage if you need to add a separate ext manually for VM users. It includes the fuction to add exts created by @FOXBI with multiple selections like capture. For the instructions on how to use, you can download and decompress as below and use it in /home/tc directory. ( Auto Answer Version with y ) wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/myv.sh.gz; tar -zxvf myv.sh.gz; The way to use it is existing same as my.sh. Where y is unnecessarily asked, it automatically responds. ---------------------------------------------------------------------------------------- Usage: ./myv.sh <Synology Model Name> <Options> Options: noconfig, noclean, manual - noconfig: SKIP automatic detection change processing such as SN/Mac/Vid/Pid/SataPortMap of user_config.json file. - noclean: SKIP the 💊 RedPill LKM/LOAD directory without clearing it with the Clean now command. However, delete the Cache directory and loader.img. - manual: Options for manual extension processing and manual dtc processing in build action (skipping extension auto detection) Please type Synology Model Name after ./myv.sh ./myv.sh DS918+ ./myv.sh DS3617xs ./myv.sh DS3615xs ./myv.sh DS3622xs+ ./myv.sh DVA3221 ./myv.sh DS920+ ./myv.sh DS1621+ CAUTION) Not all exts correspond to 7.1.0-42661. Please check @pocopico's ext GITHUB in advance and use it. We do not respond to errors caused by unsupported revisions.

Thank you!! I succeeded! Everything works, all disks are recognized. I need to set sataportmap to 6 because this motherboard defines disks 0,1,4,5 so in DSM it shows me Disk 1, DIsk 2, Disk 5, Disk 6 But it doesn't matter to me because I still know who is what.

Exactly. If you manage to install it with one drive, when you build loader again again with sataportmap 4 it will still boot from 1st drive into DSM, but you will see other drives. Make sure the other data in user_config.json stay the same. That's how I got it to work, hope you will to

Ok, I'll try but just to be sure what to do: I do the build loader with SataPortMap 1 if it works then continue installing DSM with only one drive then after installation and everything works with one drive then to try to build again with SataPortMap 4? And if I build again then it will not ask me to install DSM again?

Try This. Build a loader with SataPortMap 1, install with only one hdd on port0, When you install build loader again with sataportmap 4 and connect other drives.

hi, any try to add more than 16HDD? i successful install 3615 and add 17HDD - 1 on MB sata and 16 on LSI9201-16i edit user_config.json "SataPortMap": "616", "DiskIdxMap": "0001" "internalportcfg" : "0x3FFFFFFFF", "maxdisks" : "36", but USB HDDs connecting as internal

- Outcome of the update: SUCCESSFUL - DSM version prior update: new install - Loader version and model: Redpill Tinycore V0.4.6 DSM 7.1-42661 Update 1 (DS918+) - Using custom extra.lzma: NO - Installation type: HP ProDesk 600 G1 SFF - Additional comments: Only one HDD must be connected for install and use "SataPortMap": "1", after install you can connect other drives and change to "SataPortMap": "4"

Thanks you guys. You are great. I have decided to give DS918+ another try, or more like 10 tries to be correct. I finally manged to install DS918 with "SataPortMap": "1" and only one disk inside. I made a fresh install on a cleaned drive and will move my data around and configure stuff later on. Later I build a loader again with "SataPortMap": "4" and it boots now and detects other drives. I moved back the drive from DS920+ install with data on and it recovered the pool with no problems. Still one drive to move from DS3615xs later but I belive it will go without problems.

My favorite setup so far is to physically install only one disk in sata port 1 and set sataportmap=1 to succeed from dsm installation. After success, increase the disk and sataportmap. Have you tried this method?

https://dlcdnets.asus.com/pub/ASUS/mb/LGA1155/P8H61-I_LX_R2.0/E7989_P8H61-I_LX_R2.pdf If you look at page 31 of this manual, it says that hot plug and ahci are possible. Be sure to enable both options. This will help with disk not being found related to sataportmap.

First, make sure your SATA disks are set to AHCI in bios. While at GRUB select your boot option and press "e" then edit the sataportmap and diskidxmap to : sataportmap=888 and diskidxmap=00080F and press F10. Then login and execute fdisk -l again

Hello all, Hope someone can help me with the right DiskIdxMap and SataPortMap. I made a loader for a 3615xs and 3622xs+ and both show that no disks are found. TC suggests DiskIdxMap = 2 and SataPortMap = 22. The motherboard is an Asus P8H61-I-LX-R2 with an i5-2500. The codes for the drive controllers are 00:1f.2 (8086:1c00) and 00:1f.5 (8086:1c08). Tried a lot of combinations for the mapping, changed BIOS settings for sata like AHCI and IDE, but no luck. What can I do, any ideas ? Regards, Paul

Its my impression that, on older platforms (DS3615/918/3617/32622/DVA3221), there is no way to configure the slot#. The disks are represented to the GUI by their device name. eg. sda will always be 1st drive. sde the fifth and so on. So the disks are getting their slot on a sequencial way. Here the SataPortMap, DiskidxMap and sata_remap comes to assist. So on my system with mptsas (LSI 3Gb/sas HBA) ls -l /sys/block/sd[a-z]/device lrwxrwxrwx 1 root root 0 May 12 03:13 /sys/block/sdc/device -> ../../../2:0:0:0 lrwxrwxrwx 1 root root 0 May 12 03:13 /sys/block/sdd/device -> ../../../2:0:1:0 lrwxrwxrwx 1 root root 0 May 12 03:13 /sys/block/sde/device -> ../../../2:0:2:0 lrwxrwxrwx 1 root root 0 May 12 03:13 /sys/block/sdf/device -> ../../../2:0:3:0 lrwxrwxrwx 1 root root 0 May 12 03:13 /sys/block/sdg/device -> ../../../2:0:4:0 lrwxrwxrwx 1 root root 0 May 12 03:13 /sys/block/sdh/device -> ../../../2:0:5:0 lrwxrwxrwx 1 root root 0 May 12 03:13 /sys/block/sdi/device -> ../../../2:0:6:0 lrwxrwxrwx 1 root root 0 May 12 03:13 /sys/block/sdj/device -> ../../../2:0:7:0 I need to test on my test VM to see if there is a way to fix that. On newer platforms with Device tree files the slot number is hardcoded into the model.dtb file and enforced into a specific place on the system. So every HBA port number will be represented on a specific port.

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.

The loader is running now and i'm able to start the installation. But now i get the Error Message "Failed to install the file. The file is probably corrupted" I used the following Settings: VM Configuration: CPU Mode: 4 CPUs (Host Passthrough) Memory: 4096 MB Machine: Q35-5.1 Bios: OVMF USB Controller 3.0 (qemu XHCI) 1st Disk: USB with tinycoe-redpill-uefo.v0.4.6.img 2nd Disk: SATA 1 TB Network: e1000 Commands: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DVA3221 ./rploader.sh satamap now ./rploader.sh identifyusb now ./rploader.sh ext denverton-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/e1000/rpext-index.json ./rploader.sh build denverton-7.1.0-42661 manual user_config.json: { "extra_cmdline": { "pid": "0x0001", "vid": "0x46f4", "sn": "20C0SJRMZENMW", "mac1": "0011327C18F4", "SataPortMap": "66", "DiskIdxMap": "0006" }, "synoinfo": { "internalportcfg" : "0xffff", "maxdisks" : "16", "support_bde_internal_10g" : "no", "support_disk_compatibility" : "no", "support_memory_compatibility" : "no" }, "ramdisk_copy": { } }

Before the DSM installation, my DSM (sataportmap=8) can't find HDD Disk because of SATAPORTMAP setting. So I want to know SATAPORTMAP values of below motherboard. * Motherboard : Intel S2600GZ (C602 Chipset), 8 HDD bays & 2 SATA 6G Ports * HDD : 2.5" SATA HDD 8ea

I try for about 3days to get a working install and finally get it done in manual with the post of today from poco, but while 3622 do work good, just not the 918. But on the sataMapping, i'm quite not sure how the previous vm was done 2 post above from Peter. I understand in proxmox if you boot via .img assign as usb boot, it will not show up in the listing.. while booting and <assigning> the bootloader to the vm it show up in the hdd position. But how to get a proper listing.. or is it; we don't care about the position of the drive ? i do have the LSA2008 not yet install, so need to confirm first the lineup of position as i will add like 2 virtual hdd. I got a readyload vm backup v7 42218 and there is no "SataPortMap" and neither "DiskIdxMap". Only the proper pid 0-vid 0x46f4 for proxmox, (written in one of the page in the redpill-loader github.) And this over a Proxmox having: sata0 as bootloader and sata1 as dsmlocalhdd. When i do a 3622xsp and set "SasIdxMap": "0", / "SataPortMap": "1", / "DiskIdxMap": "0" i can have half the hdd location for sata and scsi : if hdd add in mode Virtio hdd = not detected Scsi0 = show in position #8 Scsi1 = in posi #9 (with writeback-discard. option ssd not put) if scsi1 trsf in sata1 = show in posi #3 newhd in sata3 = show in posi#5 When set another (ds36)3622xsp vm with user_config set "SataPortMap=9", "DiskIdxMap=0" * vm: q35/seabios/virtioscsi ctrl/ sata0 = dsmlocal20g / sata1= redpillBootloader i got the sata0 in position #10. So i add another hdd as sata3 : it outside of the range as being as #13. Adding an hdd as Virtio block1 : it is not detected. Adding an hdd as Scsi1 = it show as posi #16 *also with option satamap at 9 i cannot install dsm, reboot with option -e , edit to put 1 instead; then dsm install is possible. On the build i did used EXT from pocopico: acpid and virtio, but acpid don't work to turn off the vm. when build it show as downloading from Jumkey github.. perhaps it's not updated or so. sudo ./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/redpill-load/develop/redpill-acpid/rpext-index.json sudo ./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/redpill-load/master/redpill-virtio/rpext-index.json i also read about v9s.. but never find out what is it.. is this a bundle of virtio and acpid especially for proxmox ? As mention briefly at page 124.. of the loader. Thanks in advance

I have tested on VMware Workstation, i expect that to work on ESXi as well. The process is more or less the same as physical 1. Download the TCRP vmdk from REPO. 2. Create a Virtual machine with at least 2GB RAM 3. Attach the VMDK to SATA0:0 4. Data Disks to SATA1:0….X 5. Boot to tinycore 6. Perform a rploader.sh upgrade : ./rploader.sh update now 7. Perform a full upgrade : ./rploader.sh fullupgrade now 8. Generate a serial : ./rploader.sh serialgen DS920+ 9. Edit user_config.json : make sure SataPortMap=1 or leave default "58" 10. Check contents of user_config.json : cat user_config.json 11. Identify required modules and add extensions : ./rploader.sh listmods geminilake-7.1.0-42661 12. Build loader : ./rploader.sh build geminilake-7.1.0-42661

Я просмотрел руководство по материнской плате на веб-сайте Asus, но, похоже, горячее подключение не поддерживается. Лучший способ найти диск — физически смонтировать диск только в порт Sata1, изменить SataportMap=1, DiskIdxMap=00 и попробовать установить DSM. После успешной установки DSM вы можете увеличить размер диска и изменить SataportMap=4.

hi, any try to add more than 16HDD? i successful install 3615 and add 17HDD - 1 on MD sata and 16 on LSI, edit user_config.json "SataPortMap": "616", "DiskIdxMap": "0001" "internalportcfg" : "0x3FFFFFFFF", "maxdisks" : "36", but USB HDDs connect as internal

I changed it to DS3622xs+ like you. Since the DTC is not used, the SataPortMap was used again. User_config.json is set as below. "SataPortMap": "9", "DiskIdxMap": "00" However, during the migration, there was an error that disk 7,8,9 could not be found Temporarily edit the SataPortMap from 9 to 3 and lower it DSM re-installation of DS3622 was successful. As a result, slot #1 is filled, but slot #2 is empty. I will try to solve this part by changing the settings little by little.

При переходе на 7.0.1 с помощью tinycore-redpill не обнаруживает диски. Материнка Asus P5G41T-M LX 4 sata (автоматом определяет "SataPortMap": "22", "DiskIdxMap": "0002"). Пробовал в разных комбинациях подключать диск, результат прежний. Что посоветуете?