Search the Community

Have a read of my thread on getting this config working from this post onwards: Even though I'm running DSM in ESXi, I'm passing the controller through to the VM, so as far as DSM is concerned it's the same hardware configuration. From what you've shown me (not posted here in the forum), you're loading the correct driver for the P222, and can see connected HDDs in dmesg I'm pretty sure this is a sataportmap problem

This is the method proposed by "TheSTREET," which is not active in the forum here but is active in NAS-related forums in Korea. I've had a lot of trouble.Before the introduction...I have shortened the following words... Please don't get confused.... It's a word that I made to make it easier for you to understand.It's not a jargon, so please don't use it.LOL BSx = Bios SATA (number) - Sata number recognized by biosimilar sata controller chipsets DSx = DSM SATA (number) - Sata number recognized by DSM VSC = Virtual SATA Controller CSC = Chipset SATA Controller - INDEX - 1. Why do BIOS and Chipset talk? 2. Does Sataportmap and diskidxmap disable or disable Sataport? 3. VSC and Conclusion 1. About BIOS and chipset. I understand that you all know the BIOS...Let's move on. I know you're wondering, why the chipset? This is very closely related to SATA errors. In general, we take the C610 series (X99) chipsets as an example. This one basically has two CSCs.In fact, Windows and Linux also recognize two CSCs. SATA (Basic) and SSATA (Secondary SATA). In terms of specifications, SATA has six 6Gbps sataports...SSATA has four.Logically, I have 10. But when I work on DS3622xs+, if you set the option to 64..DS5 and DS6 are listed as inactive or unrecognized. So, after checking Intel's official data chart... Yes... As you can see, the CSC 0-3 Burnport is a fixed port with a sata-only signal, and the 4-5 channels have a different Muxed signal that shares lines 1 and 2 of PCIE and also shares with USB 3.0 ports. So I'm sure your chipsets are fixed, but there's also a port with mops that change their roles. I'm expecting it. It's literally a hard drive, and with that lane of USB or PCIE, the operating system is supposed to switch signals. For your information, BS4 and BS5 are using the DS5 and DS6 ports in Henology.Butroder doesn't handle it properly because it's shared. Let's stop talking about BIOS and chipset and move on to number two. 2. Does Sataportmap and diskidxmap disable or disable Sataport? This is important.We always keep our hard drives fixed while using Henology. So I thought about it and tested it...It's very simple.I've decided to think... In the case of NARS, if the hard drive fails, we replace it with a hot swap and rebuild the data, right? NARS has a hot-swappable option in each bay by default.The signal from each sataport is fixed... Yes, I am. After all the tests I've done so far...It doesn't work where you have the Muxed signal.In a CSC BS with a fixed signal... I left the hot swap option on...Sataport deactivation and unrecognized error has disappeared. Also, in the case of Muxed signals, Synalys NARS...It's a signal that's not working.I think it's more like that. In other words, the substrates of Synthetic are specially manufactured.Similar to a PC, but different...I have a lane. This is my own test, so...We need your experimental information. I'll wrap it up in the next chapter. 3. VSC and Conclusion After installing DSM during the test...I found something strange. Checking out lspci...I found the bus below. 0001:09:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11) 0001:0c:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11) It's strange. I'm sure it's Intel's main board.Even though we don't use a sata controller in addition...The Marvel sata controller was recognized... That's also four ports at 1:09:00... ...and four ports at 1:0c:00. So I thought... Redfill bootloader creates VSC and portmaps it so that it responds 1:1 with CSC. I'm crazy about the idea. As you all know, the Marvel sata controller...With a fixed signal for sata, not for mopsd... Satan Controller...Well? Yeah. . . . . . . . . . . . . . . . . . . .Of course you can't handle it.So if you use sataportmap to put in the Mukseed port... Then, it is highly likely that it can display messages such as hard recognition and errors... Let me summarize the important points now. ! IMPORTANT ! 1. Find the fixed sataport using the datasheet of each chipset. 2. Avoid using Muxed signals as much as possible. 3. Enable the HotPlug (or HotSWAP) feature on each SATA port in the BIOS. If you leave any information about chipsets you need in the comments...After work, I will find it and upload it to you'll find it. Thank you. P.S : After Use SataPortMap = 44 plugging in the hard drive, it was recognized and used immediately.(laughs)

@The Chief может знаете в чем может быть дело: ставлю dsm 7.2 от 918+ с плагинами hdddb, nvmecache, nvmevolume, в материнке 2 носителя nvme и после установки они появляются в диспетчере, но просто после нескольких перезагрузок один или оба пропадают. При этом остаются видны в "nvme list". пробовал ставить dsm без выбора плагинов в лоадере, пробовал разные лоадеры, потом вручную ставил hdddb, nvmechache а вместо enable_m2_volume пробовал m2_volume (который в терминале форматирует и появляет диски в менеджере для онлайн сборки) - и вот первый из двух он вытаскивает а второй уже нет (после перезагрузки он в менеджере не появляется а скрипт по прежнему его видит, можно отформатировать, запрашивает перезагрузку и так по кругу). Такое ощущение что не хочет больше одного носителя добавлять. Может я что-то неправильно делаю? Опишите может какой-то прядок действий, который по вашему мнению должен 100% приводить к успеху в моей ситуации. А с дисками все нормально и при выборе DSM на основе модели с device tree (например, SA6400) таких проблем нет - оба диска сразу видны в диспетчере и после установки hdddb их сразу можно делать томами и они не отваливаются оба. Но мне нужно заставить их работать в ds918+ или ds1019+ - они на sataportmap и там я нормально вижу соответствие номеров дисков портам на матплате.

Hi guys, i'm trying to install tcrp on TrueNas Core 13.0-U5.3 (bhyve). I'm able to get the installation through with this configuration : TCRP Image (RAW) (sda) Storage #1 (DISK) (sdb) Storage #2 (DISK) (sdc) However, this is how it's presented when trying to set up the satamap : tc@box: $ ./rploader.sh satamap now Machine is VIRTUAL Hypervisor= Found "00:02.0 Intel Corporation 82801HR/HO/HH (ICH8R/DO/DH) 6 port SATA Controller [AHCI mode]" Detected 6 ports/0 drives. Bad ports: -5 -4 -3 -2 -1 0. Override # of ports or ENTER to accept <6> ◊ Found "00:03.0 Intel Corporation 82801HR/HO/HH (ICHBR/DO/DH) 6 port SATA Controller [AHCI mode]" Detected 32 ports/3 drives. Bad ports: 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32. Mapping SATABOOT drive after maxdisks WARNING: Other drives are connected that will not be accessible! Computed settings: SataPortMap=11 DiskIdxMap=0010 WARNING: Bad ports are mapped. The DSM installation will fail! Should i update the user_config.json with these values ? [Yy/Nn] So it appears that two SATA Controllers are detected, with the first not holding any drives, and second holding the three drives (TCRP, Storage #1, Storage #2). The "SATABOOT drive after maxdisks" issue seems to be the pain point, and the other drives indeed are unaccessible (synology loader indicates no drives are found). What should I change with the setup or how should I configure the SataPortMap/DiskIdxMap in this configuration? Do I need to find a way to blacklist/unload the SATA Controller at 00:02.0? Any pointers would be much appreciated!

Hello friends, I am running DSM 7.0.1 of 918+ on ESXi 7.0 with tinycore bootloader. I have a virtual sata controller to boot up DSM and had to pass-throughed onboard SATA (ACHI) controller because two HDDs attached to were extracted from the old Synology machine and bind together as SHR. Anyway, I have successfully made all the way through Synology installation page. but it keep saying there are failures with the HDDs on SATA Port (12,13) and that the SATA Ports has been disabled. DiskIdxMap=94 SataPortMap=00 is my current configuration of user_config.json and I just don't know what number shall I be assigning to make this work. Please help.

Приветствую! У меня на матплате есть 2 родных nvme слота, но один из них на обратной стороне платы и там быстро становится очень жарко. Получил такой удлинитель (называется R44SF for M.2 NVMe SSD Riser Card Extension Cable) чтобы вытащить диск поближе к вентиляторам. В биос и загрузчике подключенный через удлинитель ssd виден, в liveusb тоже норм все работает, но как только пробую после сборки запустить установку DSM оно дальше надписи "больше сообщений здесь не будет" не идет. Выключаю, достаю диск и тогда загрузится нормально. Вставляю напрямую без удлинителя и тоже нормально. Можно ли как-то подружить удлинитель? Даже и не думал, что эта штука может так влиять. Второй момент это для сборок 918+ и 1019+ попробовал еще использовать простенький pci-e to m.2 nvme adapter Akasa - и вот в M.2 слоте материнки накопитель получается заставить появляться в диспетчере хранения DSM, а через адаптер pci-e не появляется никак. При этом если выбирать модель на device tree, то там pci-e адаптер работает и появляется сразу. Может какие-то параметры sataportmap нужно вручную прописать ? Пробовал разобраться с определением значений для SataPortMap и DiskIdxMap и там все непросто совсем. Может кто-то может объяснить на этом примере?

thank you. trying to switch to 918+... Could you help me with the correct values for SataPortMap and DiskIdxMap?

How to make the discs in dsm go as they connected to motherboard? please help tried to add cmd lines: SataPortMap 6 DiskIdxMap 00 sata_remap 0>1:1>2:2>3:3>4:4>5:5>6 but no changes.

Hey there, it might be a silly question with a simple answer but it was years ago I lastly dealt with My 6.2 Xpenology. So any help is highly appreciated! Due to a new NAS Case (Jonsbo N2) I changed my HBA 4xSata (all 4 SATA ports recognized in DSM) to a HBA 6xSata (not all SATA ports recognized in DSM). Because of the connector orientation and additional ports, I had to change the HBA. I also upgraded to DSM 7.1.1 but already tried 6.2 and multiple different versions and reinstalls with no difference. Current Board: J5040-ITX Old HBA: Syba SI-PEX40064 4 Port SATA III New HBA: IOCREST PCIe gen3 x1 zu 6 Ports 6G SATA III Im running Xpenology in Proxmox and can verify that before the PCI passthrough, all attached drives are recognized under Proxmox even with the new HBA. PCI passthrough is properly configured and was/is still working with the old HBA. 3x WDC_WD30EFxxxx In DSM only one disk is recognized. I read, that SataPortMap and DiskIdxMap is a thing, but can't really understand how that could be something in my particular problem. Any Luck with getting the new SATA HBA with 6 properly working ports in DSM configured? Or do I need just to get another one instead, or stick to the old one? But then I would've just had 2 ports due to the new case. Thanks in advance!

Hello community, I'm in a bit of a panic at the moment. I had the latest DSM 7.1.1 installed and running in an ESXi 6.5 VM. It has: - Tiny pill vmdk on SATA 0:0 - 100GB vmdk on SATA1:0 - 100GB vmdk on SATA1:1 - 1TB vmdk on SATA1:2 - LSI 2308 using mpt2sas in passthrough, which has 7 x 6TB SATA disks For some reason there was a gap between the virtual disks and HBA disks, the DS3622+ shows 12 bays, but my disks went to 16 (probably because it had reserved 8 for the SATA controller). This caused some sort of corruption of the DSM RAID0 (the one installed on all disks) on disks 13-16 every time the server had an issue and needed to recover, appearently DSM didn't like more than 12 disks. So I decided in all my wisdom to deal with that. by changing the satamap. Stupid idea, it turned out to be. I changed maxdisks from 16 to 12, and generated a satamap. It saw all controllers and all disks, and generated SataPortMap=14 DiskIdxMap=0C00 After building and booting the image, it is found, and says I've moved disks to a new DS (other serial?). I recover, wait 10 minutes, and get "something went wrong". I tried changing the maps to SataPortMap=148 DiskIdxMap=0C0000 as I found it weird my HBA wasn't in there. I explicitly added the mpt2sas extension again for good measure. This map I believe is the correct one, has the 3 vmdk's + a spare slot, 7 HBA disks + a spare slot, and the SATABOOT as disk 13, past maxdisks, the way it should be. But again, to no avail. I also tried SataPortMap=188 DiskIdxMap=000000 which I think was the original disk order, but that doesn't work too. To add to my stupidity, I didn't make a backup of the original boot disk, and I also have no idea what the original config was, in the "old" directory I only find json's with config that don't make sense to me. From what I can see, all disks and all disk partitions are still what they should be and not damaged, so why can't I get DSM configured and booting again?

Thanks for the reply dj_nsk The ARC loader seems to be most advandced. But with the same result When the loader start i have one red line but perhaps it's normal ? "user requested editing..." What i try : I put a formated 6 Tb disk and the usb stick with fresh ARC loader I choose DS3622xs+ then 7.2 version ... And again when i put the pat file, with DSM link or with my pat file on computer same result, 55% then error said image is corrupted. i have an xpenology since 5.2 loader With 5.2 loader install was very simple after editing config file With 6.X loader, sataportmap parameters need to be edit all the time we add a new disk Example with 6.X loader, i started with 6 diks, my sataportmap was 42 then 43 with 7 disk then 44 with 8 disks On the motherboard their are 2 hosts : SATA/SAS Storage motherboard : PCH Built-in Storage- Intel® C224 : 4 x SATA3 6.0 Gb/s (from mini SAS connector), 2 x SATA2 3.0 Gb/s, Support RAID 0, 1, 5, 10 and Intel® Rapid Storage Additional SAS Controller- LSI 2308: 8 x SAS2 6Gbps ( from 2x mini SAS 8087 connector) I must said than LSI SAS controller was in IT mode (unraid )and not in IR mode As i use only 4 port on C224 (because last 2 was only 3 gb/s) then i want use 8 port on LSI 2308 So as i said before sataportmap work good with 6.x loader with 4x parameters I found this strange with 7.X loader (with only 1 blank disk for test) : With TCRP loader : I ve seen loader haved driver for intel c220 then it find 1 disk (test disk connected so normal) and 6 ports (Yes it's right but i don't want to use lhe last 2) And it find LSI SAS and it download SCSI driver for it, said nothing about port then it write sataportmap = 6 and DiskIdxMap=00 With ARPL loader it write sataportmap = 6 and DiskIdxMap=00ff and i read sataportmap infos in loader it said 6 green port for intel and 7 green port for LSI With ARC loader it write sataportmap = 1 and DiskIdxMap=00 So i have a different result with 3 different loader I don't know if this is the reason why i have the error with pat file corrupted at 55% ? I can't find a solution alone, i need help for a solution so thanks to all for help link to the motherboard : https://www.asrockrack.com/general/productdetail.asp?Model=E3C224D4I-14S#Specifications link to the motherboard manual : https://download.asrock.com/Manual/E3C224D4I-14S.pdf link to the LSI 2308 manual : https://www.supermicro.com/manuals/other/LSI_HostRAID_2308.pdf Thanks for the help

I as I can see try update from base tinycore-redpill.v0.8.0.x, error can ignore it if at first boot you can select with keyboard TCRP FRIEND entry to boot. rploader.sh is deprecated on tinycore v0.9.4.9c but can give try ./rploader.sh update ./rploader.sh fullupgrade ./rploader.sh clean now # edit/restore user_config.json to fit your environment #./rploader.sh identifyusb now #./rploader.sh satamap now # vi user_config.json # check the settings, pay attention to pid, vid, netif_num, SataPortMap, DiskIdxMap, maxlanport, netif_seq if need it # build ds918p-7.1.1-42962 or ds918p-7.2.0-64570 ./rploader.sh ext ds918p-7.1.1-42962 add https://github.com/pocopico/tcrp-addons/raw/main/acpid/rpext-index.json ./rploader.sh build ds918p-7.1.1-42962 manual sudo rm -rf /home/tc/oldpat.tar.gz ./rploader.sh clean now ./rploader.sh backup now sudo reboot Please noted "manual" option must be use if want to be available to update from 7.1.1-42962 to 7.2.0-64570 on the fly from DSM menu with help of TCRP FRIEND. LE: TCRP FRIEND build with Peter Suh scripts v0.9.4.3-2 not support update from 7.1.1-42962 to 7.2.0-64570 from DSM menu at this time. How do i disable "checking for latest friend" --> user_config.json --> "friendautoupd": "false" ETH0 is now ETH1 and vice versa --> user_config.json --> change "maxlanport":"8", "netif_seq": "0 1 2 3 4 5 6 7" --> to "maxlanport":"2", "netif_seq": "1 0" CTRL+C to stop TCRP FRIEND to boot DSM and edit /mnt/tcrp/user_config.json via shell or \\TCRPFRIEND\tcrpfriend\tcrp\user_config.json form a PC. Enjoy TCRP FRIEND.

All 3 images attached look broken. See settings below. [HBA - H200, H310 recommended setting] DDSML, DS3622xs+, not EUDEV "DiskIdxMap": "1000", "SataPortMap": "12", "SasIdxMap: "0", "MaxDisks: "24"

This setting also worked on esxi. However, you need to try changing SataportMap and DiskIdxMap as follows. https://xpenology.com/forum/topic/61839-tinycore-redpill-loader-build-support-tool-m-shell/?do=findComment&comment=446694

If you are using bare metal, try modifying the settings as below. If it is a VM, please let me know again. You must use another method. Don't try to edit grub.cfg directly. Make sure you can edit the "user_config.json" file in M SHELL's bootloader build screen. This is what should be written in it. "DiskIdxMap": "1000", "SataPortMap": "12", "SasIdxMap: "0", "MaxDisks: "24" USE DDSML, Not EUDEV The loader needs to be rebuilt. 7.1.1-42661 is not supported, Did you build 7.1.1-42218 ? And, from the post below, there are results from testing related content. I haven't had a case for the DVA3221 yet, but I think it's worth a try.

I've been successfully running a previous version 7.0.1 of DSM in my ESXi server and decided boldly to upgrade it to 7.2.0 with the appropriate .pat file through DSM itself. That never worked, DSM did boot up to the recovery phase and stated I have moved the data disks and DSM wanted to initiate the recovery process, but would not finish it successfully. I decided to do a fresh installation of TCRP 0.9.4.9 and removed the RDM data disks from the VM and removed as well the DSM data disk and recreated the boot volume with the TCRP VMDK gzip file and ran the appropriate tasks with the image builder to get DS918+ DSM-7.2.0-64570. Installation was exactly by the guid I was once able to get the DSM up to the point of selecting how to install DSM, at which I selected to use the .pat file I had (DSM_DS918+_64570.pat). After installation I am back in the recovery stage even I don't have any of the RDM data disks attached to the VM Serial console works and through that I can access the logfiles. There is no /var/log/junior-mode file but a junior_reason which states something I don't understand why the system has dropped to junior mode. DiskStation> cat /var/log/junior_reason Exit on error [7] root not matched with junior... /var/log/messages throws all kind of errors which I'm not sure are they ignorable, here's few; Jul 23 00:55:17 kernel: [ 25.913996] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jul 23 00:55:17 root: Failed to curl [https://dataupdate7.synology.com/juniorexpansionpack/v1/getUpdate?platform=apollolake&buildnumber=64570][7] Jul 23 00:55:17 kernel: [ 26.033756] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jul 23 00:55:17 kernel: [ 26.043179] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jul 23 00:55:17 findhostd: ninstaller.c:168 umount partition /tmpRoot insmod: can't insert '/lib/modules/syno_hddmon.ko': Operation not permitted /var/log/messages gets filled with this repeating error: Jul 23 01:16:26 getty[7810]: tcgetattr: Input/output error^M Here is the user_config.json file; Notable is that I had to manually correct the model and version information. Otherwise it always stayed as model DS3622xs and version 7.1.1-42962 { "general": { "model": "DS918+", "version": "7.2.0-64570", "smallfixnumber": "0", "zimghash": "00713e465ddf347e1683a41f7ffa75afd670945c568502d754d4a24c7cb9e4ab", "rdhash": "e6e1a1fd59ce864dd174b6fb733ceda511648a9e3727845b8c0c52995af91fa2", "usb_line": "withefi earlyprintk syno_hw_version=DS918+ console=ttyS0,115200n8 netif_num=1 pid=0xa4a5 earlycon=uart8250,io, 0x3f8,115200n8 syno_port_thaw=1 mac1=000C297BB4E3 sn=1860PDN019675 vid=0x0525 elevator=elevator loglevel=15 HddHotplug=0 DiskId xMap=1000 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=1 log_buf_len=32M root=/dev/md0 SataPortMap=18 ", "sata_line": "withefi earlyprintk syno_hw_version=DS918+ console=ttyS0,115200n8 netif_num=1 pid=0xa4a5 earlycon=uart8250,io ,0x3f8,115200n8 synoboot_satadom=2 syno_port_thaw=1 mac1=000C297BB4E3 sn=1860PDN019675 vid=0x0525 elevator=elevator loglevel=15 HddHotplug=0 DiskIdxMap=1000 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=1 log_buf_len=32M root=/dev/md0 Sa taPortMap=18 ", "redpillmake": "prod", "friendautoupd": "true", "staticboot": "false", "hidesensitive": "false" }, "ipsettings": { "ipset": "", "ipaddr": "", "ipgw": "", "ipdns": "", "ipproxy": "" }, "extra_cmdline": { "pid": "0xa4a5", "vid": "0x0525", "sn": "0000000000000", "mac1": "FFFFFFFFFFFF", "netif_num": "1", "SataPortMap": "18", "DiskIdxMap": "1000" }, "synoinfo": { "internalportcfg": "0xffff", "maxdisks": "16", "support_bde_internal_10g": "no", "support_disk_compatibility": "no", "support_memory_compatibility": "no", "maxlanport": "8", "netif_seq": "0 1 2 3 4 5 6 7" }, "ramdisk_copy": {} } I will try again with DSM 7.1.1 version to see is this something which fails specificly with 7.2.0 or is something else wrong. I appreciate all help and comments to get things back up .. Erik

Hello, I'm using an HP P420i controller, I installed DS3622xs+, DSM 7.1-42661 Update 1, collected it with the hpsa driver, everything was installed, I then had 1 array on the controller, he saw this array as 1 hard disk, it was time to need a second array to record the camera, faced a problem, he's the second array he doesn't see it, i am set sataportmap anyway, DiskIdxMap, the main thing is that I see it in the CLI as /dev/sdb and in the Storage Manager 1 disk. lspci -nnq 0000:02:00.0 RAID bus controller [0104]: Hewlett-Packard Company Smart Array Gen8 Controllers [103c:323b] (rev 01) lsscsi [0:1:0:0] disk HP LOGICAL VOLUME 8.00 /dev/sda [0:1:0:1] disk HP LOGICAL VOLUME 8.00 /dev/sdb [0:3:0:0] storage HP P420i 8.00 - lsscsi -Hv [0] hpsa dir: /sys/class/scsi_host//host0 device dir: /sys/devices/pci0000:00/0000:00:02.2/0000:02:00.0/host0 Now I left DiskIdxMap=00 SataPortMap=2 I also noticed something strange in /var/log/disk.log, for some reason he sees the second array as a usb flash drive

I am trying to install DS3622xs+ 7.1.0 archictecture: broadwellnk DSM: 7.0.1-7.1.0-42661 drive slot mapping: sataportmap/diskidxmap) on a Dell PowerEdge T430 Intel Xeon e5-2623 v4 2.6Ghz, 4c/8t PERC H330 integrated RAID Controller Up to eight 3.5" Hot Plug drives four 1TB 7.2K RPM SATA 6 Gbps 3.5" HDDs, 13g but I am getting an error: /usr/local/bin/grub-editenv: error: cannot open `/home/tc/redpill-load/localdiskp1/boot/grub/grubenv': Read-only file system. After I continue with the commands and reboot the system, there are no Redpill entries in the GRUB menu. Any idea what is the cause and fix?

Flyride's instructions should work. All 8 disks of the pass-through HBA were recognized!! I got the result like below. and, DiskIdxMap=1000 SataPortMap=12 For setting, you need to use the following method. Editing user_config.json on the loader build is pointless. Initialize this value of M SHELL. How to fix sata cmdline.

I'm going to follow these instructions from flyride. SataPortMap=12 DiskIdxMap=1000 It is difficult to apply the above settings in a general way. I'll let you know if I'm successful after I finish the exam.

In HBA, SataPortmap and DiskIdxMap are not used. That's why I used blanks. SasIdxMap specifies that the HBA uses the disks from mapping number 1, but I don't know if Esxi doesn't affect it. I will test whether the AMD CPU is a variable or has other influences under the same conditions. In the past, there was a similar inquiry in Bare Metal, but there was an issue in which only 6 out of 8 disks were recognized. I'm also going to take an exam after work, so it will take time. After 12 hours?

Can someone please confirm that Surveillance Station licenses will not break if I update my DS920+ nas from DSM 7.1.1-42962 Update 2 to the currently latest ds920p-7.2.0-64570 Update 1, along with updating both SS packages to the latest 9.1.2-10854? I plan to just boot the DVA1622 redpill loader image and run the commands below the way I have before. Or maybe I need to reinstall redpill loader from scratch? Mind you that my DVA1622 DSM only shows me I can update to firmware ds920p-7.2.0-64570 (without Update 1), although I see I could manually download DSM_DVA1622_64570.pat with Update 1. I'm running dva1622 from VMWare Workstation 16.2. a. Perform rploader update by running ./rploader.sh update b. Perform a fullupdate to update all local files of your image by running ./rploader.sh fullupgrade c. Change your serial and mac address by running ./rploader.sh serialgen DVA1622 realmac d. Update user_config.json with your VID:PID of your usb stick by running ./rploader.sh identifyusb e. Update user_config.json with your SataPortMap and DiskIdxMap by running ./rploader.sh satamap Are these steps still correct? I haven't played with redpill for some time. I just don't want to have SS break licenses like it has for me in the past. Btw, I always forget this but I believe I'm supposed to manually download the SurveillanceStation-x86_64-9.1.2-10854_openvino.spk package from Synology for DVA1622 correct?

Burn a new USB with the image from this link. https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.4.3-2 If only HBA such as LSI 2008 is used, adjustment of SataPortMap is not required.

For beginners, and to configure the environment for the most common situations, M SHELL does not specify DiskIdxMap and SataPortMap as instructed by TTG. These settings will help with dynamic mapping as guided by the TTG. However, for experienced users, the setting of DiskIdxMap / SataPortMap may be required. In case of such a case, a function that can directly modify the cmdline is prepared as shown below. Press the e key within 7 seconds of booting the FRIEND kernel. By modifying "Edit SATA line", you can enter the window as shown below. Record the desired value directly. This cmdline is written permanently unless you rebuild the loader.

I'm trying to setup a DS918+ but my Gigabyte motherboard has 5 SATA instead of 6 as one is dedicated to an NVME. I'm getting this error message. I was able to install successfully but I'm concerned that in the future this port might cause an issue. Any idea on how to resolve this? tc@box:~$ ./rploader.sh satamap Found "00:17.0 Intel Corporation Device 43d2 (rev 11)" Detected 6 ports/1 drives. Bad ports: 1. Override # of ports or ENTER to accept <6> 6 Computed settings: SataPortMap=6 DiskIdxMap=00 WARNING: Bad ports are mapped. The DSM installation will fail!