Search the Community

I would advise you to try update to DSM 7.2.1 right away. Just before that, check if everything will work: do not connect your working disks yet, use some temporary SATA disk (you can try without it, but then you will not be able to fully launch the DSM) write one of the modern automated bootloaders (for example, Arc Loader) to a new USB flash drive start, configure the configuration, try to run the DSM if something doesn't work, try different settings, addons and modules, patches when everything works out, delete the temporary disk, connect the workers and run DCM with the same configuration. you will be asked to migrate - agree to save the settings. Some packages will be updated, and some (incompatible with DSM 7) will be deleted. But this is the lesser of evils. The data on the disks (files) must be saved. Notes: Hardware transcoding will not work on the 12th generation processor. Use the DS920+ - it is suitable for most household needs and allows you to forget about the SataPortMap.

Hello guys, I need your help. I was using a xpenology build since fall of 2018 and was working AMAZING!! The configuration was: - Asrock H370M-ITX/ac (6 SATA, 2 x NIC: i211V and i219V) - i3 8700 - 32Gb DDR4 RAM - SATA card SYBA SI-MPE40125 4 SATA ports -with Marvell 88SE9215 controller-, installed via M.2 e-key to mini pic-e adapter. So with the 6 ports of the motherboard have a total of 10 SATA ports. - 5x8Tb disks - Using Jun's loader 1.04b 918+ BAREMETAL (with extra.lzma for the second NIC) with DSM 6.2.3 I was completely in love with the build, I thought it was almost perfect for my needs (well, never had enough space ). I was always updating until I couldn't do it more in DSM 6.2.3. It was working so well, that even that I was tempted numerous of times to update to DSM 7 (but I was not confident enough), I kept locked to DSM 6.2.3 because I was not sure if there was anything I could do better with DSM 7, at least for my needs, and I wanted to wait until I buy new disks in summer, to do an update to DSM 7.2. It was working rock solid almost 24/7 for almost 5.5 years!! Sadly, a couple of weeks ago, the motherboard died (with no explanation), and there was no way to find a motherboard to replace it, at least in this form factor. So I had to find a replacement board (with obviously a new processor) to match the needs (and seriously there are really few possibilities, the world shortage is huge, at least in mini-ITX boards), thinking I would be able to make it work straight away with my build with few changes in the config, so I found the following: - Asrock H610M-ITX/AC (4 SATA, 1 x NIC: i219V) - i3 12100 - Same 32GB DDR4 RAM Using the mentioned SYBA card in the M.2 port, still have 8 SATA ports, and is fine for my needs even losing 2 ports, as have just 5 disks. I can see the disks in the EFI BIOS, so are being recognised, which is great as was one of my fears. So, I changed the grub.cfg of the USB with the Jun's loader of the previous configuration, and modified: - The mac address of my NIC, I got the mac address of the new board via USB with Ubuntu LTS (NOTE ABOUT MAC ADDRESSES IN THE PREVIOUS BUILD: "strangely" I was using in the previous build a "well known" mac addresses with a serial number that you can find in the forum, and it was working beautifully even with transcoding, and I don't think I was using the real mac addresses of the board!! Don't remember seriously... unless I changed the NIC mac addresses permanently to these ones, which I am not sure if it is even possible). - The SataPortMap configuration to 44 (means first 4 ports of 1st controller and first 4 ports of 2nd controller), instead the previous 64 As the previous build was using the extra.lzma for the i219V, I chose this motherboard because it had the same NIC, and I thought it would work straight away. So I booted the computer with the USB, and I am not not able to run the previous DSM installation nor able to find any Synology device with the web or the Synology assistant. Not sure if I have to use the reinstall option of the Jun's loader because of the new configuration (or is just if you want to install again DSM), and just used it with the default option of the loader (the first BAREMETAL one). I have the feeling that maybe the NIC is not being recognised and I don't understand why. Being headless I don't see any message when connected to my monitor via DisplayPort about if the loader is having any problem. Not sure what to do nor debug. Don't remember if I changed any BIOS settings in the past that maybe could matter. Just changed the hot plug of the SATA and few things more... Obviously, as I want to recover all the disks and see that everything is correct, I would like to avoid installing the DSM 7 for now (as I don't want to risk the existent disks and I have no other backups), and would love to first having DSM 6.2.3 working, and not have any problem afterwards to updated. But now I just want to see everything is correct and the DSM 6.2.3. Can anyone help me with that? I am very desperate and I don't know what more to do. Find attached the grub.cfg just in case there is any error. Thank you very much. grub.cfg

What is this? tc@box:~$ ./rploader.sh satamap now usb Loader BUS: usb Found SCSI HBAs, We need to install the SCSI modules scsi-5.10.3-tinycore64 is already installed! Succesfully installed SCSI modules Found "00:1f.2 Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)" Detected 6 ports/5 drives. Override # of ports or ENTER to accept <6> Found SCSI/HBA "01:00.0 LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 02)" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid bus number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (84 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) lspci: -s: Invalid slot number Found SCSI/HBA "" (0 drives) Computed settings: SataPortMap=6 DiskIdxMap=00 Should i update the user_config.json with these values ? [Yy/Nn] n OK remember to update manually by editing user_config.json file tc@box:~$ exit In fact, the model is Controladora Fujitsu Lsi 9211-8i Model: D2607-a21. Is that error means that my HBA is not been recognised? 5 of 6 HDD on HBA is been shown on DSM.

Is there an in-depth tutorial on how DSM/Xpen responds to changes in SATA disks? (perhaps also covering USB). I ask because so far all I can find are forum responses "do this", "edit sataportmap/DiskIdxMap values", "I did this..." Do I have to reinstall/recover whenever I rearrange drives? I'm hoping for an in-depth planning guide that covers a lot of general info, AFTER INSTALL, on what happens / what-to-do when adding/rearranging SATA drives, controllers, swapping out drives (e.g. for single-disk volumes), covering all scenarios. And perhaps about attaching/removing USB dives too. Again, so all I've found are posts that address specific issues when somebody is migrating a drive, or adding a new drive... I'm hoping to find a broad tutorial that answers questions I don't have yet. More... Rather than one-time build a reasonably spec'd box, I'm using misc leftover hardware, so I expect to have a lot of sata drive changes over time (tho I expect that's not ideal, I'm just the type that will tweak-as-I-go.) My choice hardware is very limiting (Lenovo M900 tiny), and I know I should just use more suitable stuff, but... I'm still in discovery mode, and when I get far along then I'd like to avoid having to rebuild from scratch. So what's specifically eluding me is... Using ARC loader, I seem to need at least one Sata drive to install -- I can't install on NVMe? Even tho I thought I'm installing on the USB stick, is it really installing on a base sata drive? What happens if I wish to remove the 1st (only) sata drive at a later time to upgrade it? Does this 1st sata drive get used for core DSM apps, so it's required and can't be removed? Is rearranging SATA drives a matter of "edit config file and cross fingers"? No dynamic behavior by DSM? If I were to use a JBOD sata box (my sata port supports port-multiplier), and occasionally pop in a drive, or delete a volume and remove a drive, whether I'll have to edit the If I were to add an ASMedia or JMB585 secondary sata controller, then could I jockey sata drives on those? I've been monkeying with DS920+, which doesn't seem to have satamap command ... should I switch to DS3622xs+? So with this external sata JBOD 5-bay drive rack, if it's so much trouble to swap drives, I could instead connect it with a USB-SATA bridge (instead of attaching it to an add-on sata controller), and use via File Station(?) That would be quite limiting -- no software DSM-based RAID (I'm fine with that), but would I otherwise be able to share files via apps like Plex Server off of those USB-attached drives? Any links to tutorials that address these topics? Thanks!!!

I try to edit config.json, but SataPortMap and DiskIdxMap are blank: SataPortMap = " " DiskIdxMap ->nothing is written So, how can I set more disks to my box without mess things up?

It's a miracle. Today trying ARC-loader 24.3.21 I set again SataPortMap : "6666" and DiskIdxMap : "00060c12" and now it's work!!! (6xSATA on m/b + 2x6ports NVME ASM1166 + 1x6ports PCIe4x ASM1166 as 3622xs+)

Hello, After several attempts to get all my satas ports to work properly and to preserve my usb ports as an external drive, I decided to write here hoping to find some help ! I have a Xpenology 7.2 DS918+ running a SuperMicro X11SCL-IF motherboard with 4 physical sata ports and a total of 8 USB ports. I recently updated it to version 7.2 (Model DS918+) by following the tutorial => I then added a PCI-e 16x expansion card with 24 sata ports : TISHRIC TSR818 – ASM1812+1064 chip I also added an NVME M2 card with 6 sata ports : Riser - M.2 to SATA 3.0 This gives me a total of 34 satas ports (yes, I know it's a lot, but I wanted to be able to use all my old disks and not be limited in the future). As the DS918+ is limited to 16 disks by default, I made the modifications to support my 34 satas ports by rebooting on tinycore build. To do this, I modified the user_config.json to obtain the following properties: "synoinfo": { "internalportcfg": "0x3FFFFFFFF”, "maxdisks": "34", … "esataportcfg": "0x0", "usbportcfg": "0x3FC00000000" }, I then ran the command ./rploader.sh satamap I was surpised by what it displayed because it wasn't very consistent: For my motherboard with 4 physical ports Found "00:17.0 Intel Corporation Device a352 (rev 10)" Detected 6 ports/0 drives. Override # of ports or ENTER to accept <6> 6 ports found instead of 4 physical ports. No bad ports. So I declared 4 instead of 6. For my PCI-e x16 card with 24 physical ports Found "03:00.0 ASMedia Technology Inc. Device 1064 (rev 02)" Detected 24 ports/0 drives. Bad ports: -139 -138 -137 -136 -133 -132 -131 -130 -129 -128 -127 -126 -125 -124 -123 -122 -121 -120. Override # of ports or ENTER to accept <24> Found "04:00.0 ASMedia Technology Inc. Device 1064 (rev 02)" Detected 24 ports/1 drives. Bad ports: -115 -114 -113 -112 -109 -108 -107 -106 -105 -104 -103 -102 -101 -100 -99 -98 -97 -96. Override # of ports or ENTER to accept <24> Found "05:00.0 ASMedia Technology Inc. Device 1064 (rev 02)" Detected 24 ports/0 drives. Bad ports: -91 -90 -89 -88 -85 -84 -83 -82 -81 -80 -79 -78 -77 -76 -75 -74 -73 -72. Override # of ports or ENTER to accept <24> Found "06:00.0 ASMedia Technology Inc. Device 1064 (rev 02)" Detected 24 ports/0 drives. Bad ports: -67 -66 -65 -64 -61 -60 -59 -58 -57 -56 -55 -54 -53 -52 -51 -50 -49 -48. Override # of ports or ENTER to accept <24> Found "07:00.0 ASMedia Technology Inc. Device 1064 (rev 02)" Detected 24 ports/0 drives. Bad ports: -43 -42 -41 -40 -37 -36 -35 -34 -33 -32 -31 -30 -29 -28 -27 -26 -25 -24. Override # of ports or ENTER to accept <24> Found "08:00.0 ASMedia Technology Inc. Device 1064 (rev 02)" Detected 24 ports/0 drives. Bad ports: -19 -18 -17 -16 -13 -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 0. Override # of ports or ENTER to accept <24> 6 times detected with 24 ports on each with 18 bad ports each time. Knowing that I only have one card with 24 physical ports. I divided 24 by 6 and declared 4 for each. For my M2 NVME board with 6 physical ports Found "0e:00.0 ASMedia Technology Inc. Device 1166 (rev 02)" Detected 32 ports/0 drives. Bad ports: 7 8. Override # of ports or ENTER to accept <32> 32 ports detected with 2 bad ports. Knowing that I only have 6 physical ports. I declared 6 instead of 32. At the end, I get a warning telling me that there are bad ports, but I apply my config anyway and I get this in my user_config.json. "extra_cmdline": { … "SataPortMap": "44444446", "DiskIdxMap": "0004080c1014181c" }, I boot my system and all my sata slots seem to work (modulo the order of the disk numbers which are not consistent). I've read that I can redefine the order with sata_remap in extra_cmdline, is this true? On the other hand, when I plug in an external usb disk, it's detected as an internal device with disk number 17 (whatever USB port I use, I have 8 in total). And that's the subject of my message. How can I preserve my usb ports so that it's considered an external and not an internal disk? It must surely be linked to the wrong ports, but how do I manage them correctly ? If anyone has the right procedure I'm a taker 🙂 Here's the output of my dmesg command dmesg.txt Thank you in advance for your contribution

ARC Wiki tell: "SataPortMap & SataRemap only necessary for nonDT Models". Linux documents tell, that DT is a part of Linux kernel (compiled text file) As I understand, for changing device tree I need kernel recompiling (loader's kernel or DSM's kernel? ) at least it's unavaliable for me yet. OK, let it be 1-12, 39-44, 71-76 drives numbers in DT-mode, generally they work well.

arc loaders wiki can also be a good source of information https://github.com/AuxXxilium/AuxXxilium/wiki (the important and limitations part from the start page) https://github.com/AuxXxilium/AuxXxilium/wiki/Arc:-Notice-&-Workarounds https://github.com/AuxXxilium/AuxXxilium/wiki/Arc:-SataPortMap-&-SataRemap

Yes, I try it on one controller only (the last 6 ports), because don't understand yet how to backup stock firmwares. Yes, I use all of this in my "main" NAS. But with my 1166 it doesn't work... I has 10 HDDs for tests. 4 connected to m/b sata ports, 6 to "last" 1166 (Disks 71-76 in DeviceTree mode) and create SHR2 on this 6. (user config edited for 24 ports) I try reconnection this RAID to another two 1166 controllers without any problems. Then insert in user_config SataPortMap=6666 and DiskIdxMap=00060c12 and after DSM recovering lost first 2 hdds from 6. But RAID is not degrade!!! Then try autoconfigure (./rploader.sh satamap) 1. 6 ports/4drives connected 2. 32 ports/0 drive connected (-57 -56 is a bad ports) 3. 32 ports/0 drive connected (-25 -24 is a bad ports) 4. 32 ports/6 drive connected (7 8 is a bad ports)... Set SataPortMap=6888 and DiskIdxMap=00060e16, append "ff" for 32 port mode. After DSM recovering again (when it find, "that I insert discs from another Syno") I find in DSM only 2 from 1166 connected discs with "System Partition Damage". PS. sata_remap no work in any variants. Loader with sata_remap has first two boot menu items only Editing grub (pressing "e" in boot menu) unswer, that grub has no sata_remap command.

sata_remap=9>0:0>9 https://xpenology.com/forum/topic/32867-sata-and-sas-config-commands-in-grubcfg-and-what-they-do/ https://gugucomputing.wordpress.com/2018/11/11/experiment-on-sata_args-in-grub-cfg/ did you see this`? https://xpenology.com/forum/topic/52094-how-to-config-sataportmap-sata_remap-and-diskidxmap/ also a possible solution might be to just use one asm1166 and place it as last card, that way the 32 ports are no problem like 6 x sata onbard, 5 x sata with jmb585, 6 x sata with asm1166 if needed another jmb585 or jmb582 card can be placed in the middle to keep asm1166 last, jmb582 will be a pcie1x card but sometime all the good slots are all used but even a 1x slot can be useful (afair there a re even jmb585 with pcie 1x but using to many of the ports might result in some performance degradation) there is also a newer firmware from 11/2022 for asm1166 (at least newer the the one from silverstone) but it does not fix the 32 port problem https://winraid.level1techs.com/t/latest-firmware-for-asm1064-1166-sata-controllers/98543/18

Hi all, I know this is a well-worn topic, but I have not been able to find a specific answer on my situation. I understand how and why the SataPortMap & DiskIdxMap fields are used, (well, I think I understand it enough...) But my questions is: How does one go about determining what these values should be? I am currently running a: · TinyCore RedPill Loader with M-Shell (Latest as of 20240305) · Asus P11C-M4L with all SATA controllers turned off in the BIOS · ASUS PIKE II 3008 8-port SAS HBA card · 12GB/s SGPIO Expander hot-swap backplane that the connects back to the PIKE II card via 2 MiniHD Cables · 12 SAS disks attached to the this backplane · All 12 disks are being presented to Xpenology as individual disk. With: SataPortMap: 1 DiskIdxMap: 00 I end with DSM detecting all 12 disks, but the disk count starts at 02 and goes through to 13. Like other users I am trying to configure my system to use ports 01-12 I have read some comments suggesting that SAS configurations do not utilise the SataPort Map setting, however I find if I manipulate these settings, does affect the disk layout in DSM. As I have disabled my onboard SATA controllers I believe the PIKE Card is the first control which holds 8 ports, evern though via the SAS backplane it has 12 disks attached. As SataPortMap only uses 1 digit to configure the ports, I assume I need to use: SataPortMap: 8 SataPortMap: 1 DiskIdxMap: 00 Assigns my 12 disks from: sdb through to sdm and SataPortMap: 8 DiskIdxMap: 00 Assigns my 12 disks from: sdd through to sdo So these values are affecting my DSM configuration, what I do not understand is how to calculate the HEX values for the DiskIdxMap. I believe setting DiskIdxMap: 00 means that the first disk detected should be assigned to sda. Ssh-ing into the DSM, there is no sda listed, so I don’t believe there are any other disk controllers at play here. Have I misunderstood a concept here? Is there any glaringly obvious I have missed or misunderstood? Cheers, Leon

I'm build a test device on 6xSATA m/b + 2x 6ports NVME 1166 3622xs+. It work. With blank ("SataPortMap" : "" and "DiskIdxMap" : "") DSM7.2.1 see drives 1-12 and 39-44. I tried sata_remap in user_config and sata comandline (39\\>13...44\\>18, 39\>13...44\>18, 39>13:13>39...), but in all this cases DSM can see only drive 39. What about a right sintacs? Or its useless in DSM7? How can I remap them and set other ports as dummy?

Hi all, I have been using a HP G7 N54L Microserver with the standard 4 drives (4x 2TB Seagate SATA NASware, ancient but still working) and embedded NIC, and a SanDisk 16GB USB3.0 flashdrive running DSM5.0 that was setup by a friend around 10 years ago and it has worked flawlessly but given the age of the software I figured it was time to upgrade to DSM7.1.1. I'm a noob to xpenology myself so please be gentle. I've read up a fair bit but I've still got a ways to go. I've been following the well written upgrade guide here https://tomvanveen.eu/installing-synology-dsm-7-x-on-a-hp-n54l-in-2022/ in combination with the excellent post by flyride here: Many people have had success with it but I've run into a problem during the build in TinyCore. First I flashed the BIOS successfully using Kamzata's ROM (https://www.bios-mods.com/forum/showthread.php?pid=75965#pid75965). I didn't realise this reset the BIOS clock which I thought might be the issue but I've since updated it and the issue persists. I've also disabled the C1E Support setting so it's not that. I'm using older TC v0.9.3.0 as recommended in the guide for N54Ls, with the BIOS/CSM/Legacy boot from USB flash drive image. I can run through all the commands successfully but when I boot into RedPill USB option in the GRUB menu I get this "error: file './custom.gz' not found" (pic attached) and my router is not assigning an IP address so I can't find Synology in Synology Assistant (checked the ports/cables so issue is not router related). I noticed these issues following the build command in the TinyCore terminal: menuentry 'RedPill DS3622xs v7.1.1-42962 Beta (USB, Verbose)' { menuentry 'RedPill DS3622xs v7.1.1-42962 Beta (SATA, Verbose)' { Updated user_config with USB Command Line : withefi earlyprintk syno_hw_version=DS3622xs+ console=ttyS0,115200n8 netif_num=1 pid=0x5580 earlycon=uart8250,io,0x3f8,115200n8 syno_port_thaw=1 mac1=9CB65407E0C3 sn=2030SQRH8LJAM vid=0x0781 elevator=elevator loglevel=15 HddHotplug=0 DiskIdxMap=00 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 log_buf_len=32M root=/dev/md0 SataPortMap=6 Updated user_config with SATA Command Line : withefi earlyprintk syno_hw_version=DS3622xs+ console=ttyS0,115200n8 netif_num=1 pid=0x5580 earlycon=uart8250,io,0x3f8,115200n8 synoboot_satadom=1 syno_port_thaw=1 mac1=9CB65407E0C3 sn=2030SQRH8LJAM vid=0x0781 elevator=elevator loglevel=15 HddHotplug=0 DiskIdxMap=00 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 log_buf_len=32M root=/dev/md0 SataPortMap=6 Generating GRUB entries for model :ds3622xsp_42962 in /home/tc ./rploader.sh: line 2260: /home/tc/include/grubmgr.sh: No such file or directory Failed to generate grub.cfg ./rploader.sh: line 2261: /home/tc/include/grubmgr.sh: No such file or directory Failed to add USB entry ./rploader.sh: line 2262: /home/tc/include/grubmgr.sh: No such file or directory Failed to add SATA entry ./rploader.sh: line 2263: /home/tc/include/grubmgr.sh: No such file or directory Failed to add SATA entry ./rploader.sh: line 2264: /home/tc/include/grubmgr.sh: No such file or directory Failed to add SATA entry cp: cannot create regular file '/home/tc/redpill-load/part1/boot/grub/grub.cfg': Permission denied grep: /home/tc/grub.cfg: No such file or directory Copying grub file /home/tc/grub.cfg to /home/tc/redpill-load/localdiskp1/boot/grub/grub.cfg cp: cannot stat '/home/tc/grub.cfg': No such file or directory menuentry 'RedPill DS3622xs v7.1.1-42962 Beta (USB, Verbose)' { menuentry 'RedPill DS3622xs v7.1.1-42962 Beta (SATA, Verbose)' { Setting next grub entry Setting next grub entry to Friend : sudo: /usr/local/bin/grub-editenv: command not found sudo: /usr/local/bin/grub-editenv: command not found Grub entry has been set to : Ramdisk in not compressed 48778 blocks 42649 blocks 91425 blocks Cleaning up files Caching files for future use No adequate space on TCRP loader partition /mnt/sde3 to cache pat file Found /mnt/sde3/auxfiles/ds3622xsp_42962.pat file Removing older cached pat files to cache current Found /home/tc/redpill-load/cache/ds3622xsp_42962.pat, copying to cache directory : /mnt/sde3/auxfiles Saving user session for future use. Saving current extensions -> OK ! Saving current user_config.json -> OK ! Also worth noting (I think) is that when I attempt to boot into RedPill in the GRUB menu, the TinyCore option is no longer present, which it seems to be on successful installs. Apologies for the long first post. In my rookie status I'm stumped so any advice on what I can look into in order to proceed will be greatly appreciated. If any additional info or part of the command logs will be useful I can include it.

Still, is it compatible? Before I used a q6600 in dsm 6.1.. I follow this tutorial: https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ When I put "./rploader.sh build broadwellnk-7.1.0-42661" I get this: (I'm trying to install Ds3622xs+) tc@box:~$ ./rploader.sh build broadwellnk-7.1.0-42661 Error: Platform not found: rploader.sh Version: 0.10.0.0 -------------------------------------------------- -------------------------------------- Usage: ./rploader.sh <action> <platform version> <static or compile module> [extension manager arguments] Actions: build, ext, download, clean, update, listmods, serialgen, identifyusb, patchdtc, satamap, backup, backuploader, restoreloader, restoresession, mountdsmroot, postupdate, mountshare, version, monitor, bringfriend, downloadupgradepat, help - build <platform> <option> : Build the 💊 RedPill LKM and update the loader image for the specified platform version and update currentloader. Valid Options: static/compile/manual/junmod/withfriend** (default: withfriend) ** withfriend add the TCRP friend and a boot option for auto patching - ext <platform> <option> <URL> Manage extensions using redpill extension manager. Valid Options: add/force_add/info/remove/update/cleanup/auto . Options after platform Example: rploader.sh ext apollolake-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/e1000/rpext-index.json or for auto detect use rploader.sh ext apollolake-7.0.1-42218 auto - download <platform> : Download redpill sources only -clean: Removes all cached and downloaded files and starts over clean -update: Checks github repo for latest version of rploader, and prompts you download and overwrite - fullupgrade: Performs a full upgrade of the local files to the latest available on the repo. It will backup the current filed under /home/tc/old - listmods <platform>: Tries to figure out any required extensions. This usually are device modules - serialgen <synomodel> <option> : Generates a serial number and mac address for the following platforms DS3615xs DS3617xs DS916+ DS918+ DS920+ DS3622xs+ FS6400 DVA3219 DVA3221 DS1621+ DVA1622 DS2422+ RS4021xs+ DS923+ DS1522+ SA6400 FS2500 RS3413xs+ DS1019+ DS1520+ DS 1621xs+ DS723+ Valid Options : realmac , keeps the real mac of interface eth0 - identifyusb : Tries to identify your loader usb stick VID:PID and updates the user_config.json file - patchdtc : Tries to identify and patch your dtc model for your disk and nvme devices. If you want to have your manually edited dts file used convert it to dtb and place it under /home/tc/custom-modules - satamap : Tries to identify your SataPortMap and DiskIdxMap values and updates the user_config.json file - backup: Backup and make changes /home/tc changed permanent to your loader disk. Next time you boot, your /home will be restored to the current state. -backuploader: Backup current loader partitions to your TCRP partition - restoreloader: Restore current loader partitions from your TCRP partition - restoresession : Restore last user session files. (extensions and user_config.json) - mountdsmroot : Mount DSM root for manual intervention on DSM root partition - postupdate: Runs a postupdate process to recreate your rd.gz, zImage and custom.gz for junior to match root - mountshare : Mounts a remote CIFS working directory - version <option>: Prints rploader version and if the history option is passed then the version history is listed. Valid Options: history, shows rploader release history. - monitor : Prints system statistics related to TCRP loader - getgrubconf : Checks your user_config.json file variables against current grub.cfg variables and updates your user_config.json accordingly - bring friend Downloads TCRP friend and makes it the default boot option. TCRP Friend is here to assist with automated patching after an upgrade. No postupgrade actions will be required anymore, if TCRP friend is left as the default boot option. - downloadupgradepat Downloads a specific upgrade pat that can be used for various troubleshooting purposes - removefriend Reverse bringfriend actions and remove TCRP from your loader - help: Show this page -------------------------------------------------- -------------------------------------- Version: 0.10.0.0 tc@box:~$ --------------- Then the sataport map also fails: tc@box:~$ ./rploader.sh satamap Found "00:1f.2 Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)" Detected 6 ports/1 drives. Bad ports: 2 3 4. Override # of ports or ENTER to accept <6> Computed settings: SataPortMap=6 DiskIdxMap=00 WARNING: Bad ports are mapped. The DSM installation will fail! Should I update the user_config.json with these values ? [Yy/Nn] and Donate. tc@box:~$

satacontroller: "1", хотя при сборке загрузчика было выбрано "SataPortMap: Active Ports *" Нужно исправить на 3? Или лучше перебрать загрузчик со значением "SataPortMap: Max Ports"?

I ran into the exact problem when upgrading from DSM 7.1.x to 7.2.y. I only found 1 thing talking about it. (See Link) https://hedichaibi.com/fix-xpenology-problems-viewing-internal-hard-drives-as-esata-hard-drives/ My /etc/synoinfo.conf and /etc.defaults/synoinfo.conf had a problem with the esataportcfg setting. Original: esataportcfg="0xff000" internalportcfg="0x3fff" usbportcfg="0x8700" Changed to: esataportcfg="0x00" internalportcfg="0xffff" usbportcfg="0x00" I think I had to make the changes in both conf files. The USB one maybe a problem later but that should be easier to fix now that I know the problem. Note: These can be 32 bit values (32 drives... or maybe even 64-bit and 64 drives... but definitely at least 32) so up to: "0xffffffff" I'm really glad I got this figured out. I hope this helps people. PREngineer on this link had some other interesting changes for configuring the drives. These would make my drive ordering look better. (But my system is working so maybe I won't mess with this.) https://xpenology.com/forum/topic/52094-how-to-config-sataportmap-sata_remap-and-diskidxmap/

Перетыкал пару раз,запускается проверка и всё. Банально перепутал местами. Потом стал наклеивать скотч с порядковыми номерами. Но это в рамках своего девайса, при одном контроллере и неизменном SataPortMap То есть Хрень не особо любит перемену мест хардов, но дозволяет )))

Hi, trying this method, however I run into an issue after this loads to install DSM all of a sudden the screen goes blank and ping connectivity is lost to the hardware. Could this be related to i915 driver? --------------------------------------={ TinyCore RedPill Friend }=-------------------------------------- TCRP Friend Version : 0.1.0k 0.1.0 friend kernel version up from 5.15.26 to 6.4.16 0.1.0d Fix Some H/W Display Info, Add skip_vender_mac_interfaces cmdline to enable DSM's dhcp to use the correct mac and ip 0.1.0h Add process to abort boot if corrupted user_config.json is used 0.1.0j Remove skip_vender_mac_interfaces and panic cmdline (SAN MANAGER Cause of damage) 0.1.0k Added timestamp recording function before line in /mnt/tcrp/friendlog.log file. Model : SA6400, Serial : 2270TQRHSMTMY, Mac : D843AE17BF5B, Build : 7.2.0-64570, Update : 0, LKM : prod Loader BUS: usb CPU,MEM: 12th Gen Intel(R) Core(TM) i5-12500 [12 Thread(s)], 31.2G Memory DMI: Micro-Star International Co., Ltd. MS-7D40/MPG B760I EDGE WIFI (MS-7D40), BIOS A.60 01/10/2024 SAS/RAID HBAs Count : 0 , NICs Count : 1 System is running in UEFI boot mode Setting MAC Address from D8:43:AE:17:BF:5B to D8:43:AE:17:BF:5B on eth0 (r8169) IP Address :192.168.1.83, Network Interface Card : eth0 [10ec:8125] (r8125) Detecting upgrade : Ramdisk OK ! zImage OK ! Detecting Internet -> OK! Checking for latest friend -> OK, latest zImage : /mnt/tcrp/zImage-dsm initrd : /mnt/tcrp/initrd-dsm, Module Processing Method : EUDEV cmdline : withefi earlyprintk syno_hw_version=SA6400 console=ttyS0,115200n8 netif_num=1 pid=0xa836 earlycon=uart8250,io,0x3f8,115200n8 syno_port_thaw=1 SasIdxMap=0 mac1=D843AE17BF5B sn=2270TQRHSMTMY SMBusHddDynamicPower=0 vid=0x05dc elevator=elevator loglevel=15 HddHotplug=0 DiskIdxMap syno_hdd_detect=0 vender_format_version=2 sataboot2 syno_hdd_powerup_seq=0 log_buf_len=32M root=/dev/md0 SataPortMap syno_ttyS1=serial,0x2f8 syno_ttyS0=serial,0x3f8 Access http:/192.168.1.83:7681 via the TTYD web terminal to check the problem. (If you have any problems with the DSM installation steps, check the /var/log/linuxrc.syno.log file in this access) Default TTYD root password is blank User config is on /mnt/tcrp/user_config.json Press <r> to enter a menu for Reset DSM Password Press <e> to enter a menu for Edit USB/SATA Command Line Press <j> to enter a Junior mode (to re-install DSM) Press <ctrl-c> to stop boot booting in : 6 Press <ctrl-c> to stop boot booting in : 5

I am trying install DSM 7.2 - DS3622xs+ on the following system: Ryzen 5 4650g Rog Strix b550i (4xsata, 2xNvme) 32gb ram On motherboard sata: 2xSSD for Proxmox boot, 2xSSD for Proxmox VMs, 2xNVME for Xpenology cache On LSI/Broadcom SAS3008 HBA Controller in IT Mode: 4x18tb HDD, 2x SSD for VMs, 2xSata empty for future expansion ARC Loader 21.4.24.img I followed some PCIE passthrough tutorials to install xpenology using the manual HDD pass-through method which worked fine but was limited to 6 sata ports only. Installed with ARC Loader 21.4.24, selected the first option for SataportMap: Active Ports*. When I got to the find.synology.com screen, it recognized I had drives 2 to 7 and installed DSM. However, I would like the option to have more drives in the future, so I scrapped the VM and try to install again by passing the whole HBA card to the VM itself. I added- Raw Device - select HBA Card - ROM-BAR and PCI-Express Checked. I have tried every option for the SataportMap, but each time I get 'No Drives Detected'. In the Arc Loader sysinfo, when you scroll down, it recognizes the HBA card and says it has 6 drives attached to it. This told me that the loader can see the drives, so I manually passed through one of my NVME drives using scsi. When you get to the find.synology.com screen, it recognized the 1 nvme drive and was able to install DSM. When it finally loads, my 4x18th and 2xSSDs attached to the HBA are visible and working fine in DSM. So what am I missing? Can I not boot into DSM without having at least one HDD or SSD manually passed through? My eyes are going cross trying to troubleshoot every possibility, I wanted to list here everything I have done to troubleshoot but that would be a huge post. Should I skip trying to pass through the whole HBA Card and just manually pass through the drives? How do I add more drives then? Any suggestions are welcome.

I figured out how SataPortMap / DiskIdxMap works, but when I change these parameters, there are no changes in the DSM interface. The first disk is always empty...( I set the values but no change...( "SataPortMap": "", "DiskIdxMap": "0С00", "SasIdxMap: "0xffffffff"

Lot of guys before you requested same thing with HBA cards. Using random values will not help. You have to understand how SataPortMap / DiskIdxMap works, and how it can match your particular setup. and even with this, there is a high chance you never "figure it out". If it works, just get over it. Otherwise, just use search function about "HBA" cards... have fun.

I would like to figure it out... It’s strange why the settings SataPortMap": "12", "DiskIdxMap": "1000", "SasIdxMap: "0" do not work?

Thanks. Reinstalled DSM completely with parameters set to SataPortMap": "12", "DiskIdxMap": "1000", "SasIdxMap: "0", "MaxDisks: "24", but the result is the same.(

[HBA Recommended settings from flyride] Not EUDEV , Use Only DDSML (If you use TCRP-mshell ) "SataPortMap": "12", "DiskIdxMap": "1000", "SasIdxMap: "0" "MaxDisks: "24"