-iliya- Posted May 17, 2022 Share #3426 Posted May 17, 2022 5 минут назад, pocopico сказал: @flyride , i'm testing my theory with internal / usb and maxdisks so when i set 32 for internalportcfg and 8 had the default for usbportcfg the USB was identified as internal disk. No i'm changing to what i think would be ok. internalportcfg 24 + usbportcfg 8 = 32 and see. i'm try this about 5-10minutes and post result Quote Link to comment Share on other sites More sharing options...
-iliya- Posted May 17, 2022 Share #3427 Posted May 17, 2022 3 минуты назад, flyride сказал: Just curious though, in the above example of reboot problem, what happens if you eject the USB's using the DSM UI? I can check it later Quote Link to comment Share on other sites More sharing options...
techfriend63 Posted May 17, 2022 Share #3428 Posted May 17, 2022 1 minute ago, pocopico said: Hi can you follow my instructions again ? I think you've got something wrong. hello this is what I am using for VM: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh satamap now ./rploader.sh serialgen DS3622xs+ ./rploader.sh clean now ./rploader.sh build broadwellnk-7.0.1-42218 When I check "/home/tc/redpill-load/config/DS3622xs+/7.0.1-42218/", "config.json" is not present. This is the same for DS3617xs. Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 17, 2022 Author Share #3429 Posted May 17, 2022 (edited) 14 minutes ago, techfriend63 said: hello this is what I am using for VM: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh satamap now ./rploader.sh serialgen DS3622xs+ ./rploader.sh clean now ./rploader.sh build broadwellnk-7.0.1-42218 When I check "/home/tc/redpill-load/config/DS3622xs+/7.0.1-42218/", "config.json" is not present. This is the same for DS3617xs. Yes, i just saw that, i'm fixing now. Edit @techfriend63 please try again Edited May 17, 2022 by pocopico 1 Quote Link to comment Share on other sites More sharing options...
flyride Posted May 17, 2022 Share #3430 Posted May 17, 2022 45 minutes ago, -iliya- said: I can check it later If this doesn't make the SATA drives accessible, there is command line sequence that will hotplug out an inaccessible disk device and rescan it to get the correct sd mapping. Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 17, 2022 Author Share #3431 Posted May 17, 2022 55 minutes ago, pocopico said: @flyride , i'm testing my theory with internal / usb and maxdisks so when i set 32 for internalportcfg and 8 had the default for usbportcfg the USB was identified as internal disk. No i'm changing to what i think would be ok. internalportcfg 24 + usbportcfg 8 = 32 and see. @flyride i think my theory was right and only happens when i limited the sataportmap to match the total of maxdisks. Then internalportcfg could usbportcfg are working as expected. I have SataPortMap=22 and DiskIdxMap=000204 for 4 Sata disks and 24 SCSI disks. Then USB gets the sdac which is 26+3-28=1. So i guess its a combination of all parameters. 1 Quote Link to comment Share on other sites More sharing options...
-iliya- Posted May 17, 2022 Share #3432 Posted May 17, 2022 6 минут назад, pocopico сказал: @flyride i think my theory was right and only happens when i limited the sataportmap to match the total of maxdisks. Then internalportcfg could usbportcfg are working as expected. I have SataPortMap=22 and DiskIdxMap=000204 for 4 Sata disks and 24 SCSI disks. Then USB gets the sdac which is 26+3-28=1. So i guess its a combination of all parameters. I understand this is in a virtual machine? But can you check if some of the disks are turned off so that the slots are freed, USB will also be connected as USB or as an internal one? I'm a little confused - what parameters do I need to specify in the bootloader SataPortMap=68 and DiskIdxMap=00 maxdisk 32 and respectively for 24 internal and 8 usbport? Quote Link to comment Share on other sites More sharing options...
-iliya- Posted May 17, 2022 Share #3433 Posted May 17, 2022 1 час назад, pocopico сказал: @flyride , i'm testing my theory with internal / usb and maxdisks so when i set 32 for internalportcfg and 8 had the default for usbportcfg the USB was identified as internal disk. No i'm changing to what i think would be ok. internalportcfg 24 + usbportcfg 8 = 32 and see. now i rebuild new loader 3622 with "SataPortMap": "68", "DiskIdxMap": "00" }, "synoinfo": { "internalportcfg": "0x0ffffff", "usbportcfg": "0x0f00000000", "maxdisks": "32", 6 sata on MB enable and only 9201-16i installed on 1 PCI - no HDD connected to LSI USB connected as internal 21 port Quote Link to comment Share on other sites More sharing options...
-iliya- Posted May 17, 2022 Share #3434 Posted May 17, 2022 1 час назад, flyride сказал: Just curious though, in the above example of reboot problem, what happens if you eject the USB's using the DSM UI? I can't test this, because when USB is connected as an internal drive, there is no USB safe eject button. If you just remove USB, then sata does not take its place. Quote Link to comment Share on other sites More sharing options...
flyride Posted May 17, 2022 Share #3435 Posted May 17, 2022 (edited) 21 hours ago, -iliya- said: after remove 3 sata HDD and connect 3 USB looks like this Can you please do a test to repeat this scenario Then ls /sys/block so we can see how the 3 SATA HDD drives are being mapped. And ls -la /sys/class/scsi_host Edited May 17, 2022 by flyride Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 17, 2022 Author Share #3436 Posted May 17, 2022 43 minutes ago, flyride said: Can you please do a test to repeat this scenario Then ls /sys/block so we can see how the 3 SATA HDD drives are being mapped. And ls -la /sys/class/scsi_host @-iliya- @flyride I think that, since no external module loading is required, SATA/AHCI are the first drives that will be identified. All other drives besides SATA/AHCI will be identified later in the boot process. So the disk enumeration will always start from SATA and then SCSI/SAS. Only be checking DSM GUI you are not 100% sure for how are the disks identified. Drive numbers will be sda-z (for the first 26) and then sdaa-z (for the next 26) and so goes on. The disks will be listed with fdisk -l |grep Disk |grep sd even if they are not present in the Storage Manager GUI. The only way to troubleshoot is to check also via ssh. Quote Link to comment Share on other sites More sharing options...
flyride Posted May 17, 2022 Share #3437 Posted May 17, 2022 (edited) 2 hours ago, -iliya- said: I can't test this, because when USB is connected as an internal drive, there is no USB safe eject button. If you just remove USB, then sata does not take its place. Ok, well here is how you can fix it then. First, you need to know a USB with an improper assignment. You can see this in Storage Manager. Let's assume for example it's sdu This command will logically remove it from the system and free up the slot: sudo echo 1 > /sys/block/sdu/device/delete Repeat for all USB's that are misassigned like this. Avoid accidentally removing the loader USB. Now you need to determine the mismapped HDDs: ls /dev/sd* | grep [a-z]$ This will return a list of disk devices. Any device larger than the maxdisks value (i.e. 16 maxdisks = /dev/sdq..z, /dev/sdaa..az) is mismapped. Then you need to identify the SCSI host number of each of the mismapped HDDs (sub for "X"): ls -la /sys/block/sdX A long string will be returned, and embedded will be a host number (i.e. host10). Record this and repeat through the list. Then you need to hotplug out each of the mismapped HDD's (sub for "X"): sudo echo 1 > /sys/block/sdX/device/delete Finally hotplug back in and assign new namespace slots for the mismapped drives (sub for "X" with all host numbers recorded from previous step): sudo echo "- - -" > /sys/class/scsi_host/hostX/scan You might need to manually start the array at that point. sudo mdadm --assemble --scan Edited May 17, 2022 by flyride 1 Quote Link to comment Share on other sites More sharing options...
-iliya- Posted May 17, 2022 Share #3438 Posted May 17, 2022 (edited) 2 часа назад, flyride сказал: Can you please do a test to repeat this scenario Then ls /sys/block so we can see how the 3 SATA HDD drives are being mapped. And ls -la /sys/class/scsi_host and so I try to replicate the scenario. I had to create a bootloader with these parameters "SataPortMap": "688", "DiskIdxMap": "00060e" }, synoinfo: { "internalportcfg": "0x3fffff", "usbportcfg": "0xffc0000", "esataportcfg": "0x0", "maxdisk": "22", i connected all 16 disks in LSI, in DSM i see 22 disks as internal USB HDD link as external Скрытый текст sda sdb sdc sdd sde sdg sdh sdi sdj sdk sdl sdm sdn sdo sdp sdq sdr sds sdt sdu sdv Скрытый текст sda sdb sdc sdd sde sdg sdh sdi sdj sdk sdl sdm sdn sdo sdp sdq sdr sds sdt sdu sdv sdw - USB HDD seen as external next i disconnect 4 sata HDD 19-20-21-22 and connect USB - seen as internal Скрытый текст sda sdb sdc sdd sde sdg sdh sdi sdj sdk sdl sdm sdn sdo sdp sdq sdr sdu - USB HDD Скрытый текст sda sdb sdc sdd sde sdg sdh sdi sdj sdk sdl sdm sdn sdo sdp sdq sdr sds sdt sdu USB sdv sdw now i connect 2 USB and ls /sys/block added 2 device: sdy sdz connect one more 2 USB flash ls /sys/block added 2 device: sdaa sdab in DSM i see 4 USB Скрытый текст GPT PMBR size mismatch (4294967294 != 7814037166) will be corrected by write. Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdd: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sde: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdk: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdl: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdm: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdo: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdq: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdp: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdr: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdn: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdg: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdj: 465.8 GiB, 500106780160 bytes, 976771055 sectors Disk /dev/sdi: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdh: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdu: 111.8 GiB, 120034123776 bytes, 234441648 sectors Disk /dev/sds: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdt: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdv: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdw: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk /dev/sdy: 298.1 GiB, 320072933376 bytes, 625142448 sectors Disk /dev/sdx: 3.7 TiB, 4000787029504 bytes, 7814037167 sectors Disk /dev/sdz: 14.4 GiB, 15495856128 bytes, 30265344 sectors Disk /dev/sdaa: 24.7 GiB, 26536837120 bytes, 51829760 sectors Скрытый текст total 0 drwxr-xr-x 2 root root 0 May 17 21:44 . drwxr-xr-x 61 root root 0 May 17 21:44 .. lrwxrwxrwx 1 root root 0 May 17 21:44 host0 -> ../../devices/pci0000:00/0000:00:1f.2/ata1/host0/scsi_host/host0 lrwxrwxrwx 1 root root 0 May 17 21:44 host1 -> ../../devices/pci0000:00/0000:00:1f.2/ata2/host1/scsi_host/host1 lrwxrwxrwx 1 root root 0 May 17 22:08 host12 -> ../../devices/pci0000:00/0000:00:14.0/usb2/2-6/2-6.4/2-6.4:1.0/host12/scsi_host/host12 lrwxrwxrwx 1 root root 0 May 17 22:28 host19 -> ../../devices/pci0000:00/0000:00:14.0/usb2/2-6/2-6.3/2-6.3:1.0/host19/scsi_host/host19 lrwxrwxrwx 1 root root 0 May 17 21:44 host2 -> ../../devices/pci0000:00/0000:00:1f.2/ata3/host2/scsi_host/host2 lrwxrwxrwx 1 root root 0 May 17 22:28 host20 -> ../../devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5.3/2-5.3:1.0/host20/scsi_host/host20 lrwxrwxrwx 1 root root 0 May 17 22:28 host21 -> ../../devices/pci0000:00/0000:00:14.0/usb2/2-6/2-6.1/2-6.1:1.0/host21/scsi_host/host21 lrwxrwxrwx 1 root root 0 May 17 22:28 host22 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/host22/scsi_host/host22 lrwxrwxrwx 1 root root 0 May 17 21:44 host3 -> ../../devices/pci0000:00/0000:00:1f.2/ata4/host3/scsi_host/host3 lrwxrwxrwx 1 root root 0 May 17 21:44 host4 -> ../../devices/pci0000:00/0000:00:1f.2/ata5/host4/scsi_host/host4 lrwxrwxrwx 1 root root 0 May 17 21:44 host5 -> ../../devices/pci0000:00/0000:00:1f.2/ata6/host5/scsi_host/host5 lrwxrwxrwx 1 root root 0 May 17 21:44 host6 -> ../../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host6/scsi_host/host6 lrwxrwxrwx 1 root root 0 May 17 21:44 host7 -> ../../devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9.2/1-9.2:1.0/host7/scsi_host/host7 1 MPT Port found Port Name Chip Vendor/Type/Rev MPT Rev Firmware Rev IOC 1. ioc0 LSI Logic SAS2116 B1 200 11000100 0 B___T___L Type Operating System Device Name 0 4 0 Disk /dev/sdk [6:0:4:0] 0 5 0 Disk /dev/sdl [6:0:5:0] 0 6 0 Disk /dev/sdm [6:0:6:0] 0 7 0 Disk /dev/sdn [6:0:7:0] 0 8 0 Disk /dev/sdo [6:0:8:0] 0 9 0 Disk /dev/sdp [6:0:9:0] 0 10 0 Disk /dev/sdq [6:0:10:0] 0 11 0 Disk /dev/sdr [6:0:11:0] 0 18 0 Disk /dev/sdg [6:0:18:0] 0 19 0 Disk /dev/sdh [6:0:19:0] 0 20 0 Disk /dev/sdi [6:0:20:0] 0 21 0 Disk /dev/sdj [6:0:21:0] 0 22 0 Disk /dev/sds [6:0:22:0] 0 23 0 Disk /dev/sdt [6:0:23:0] 0 24 0 Disk /dev/sdv [6:0:24:0] 0 25 0 Disk /dev/sdw [6:0:25:0] Edited May 17, 2022 by -iliya- 1 Quote Link to comment Share on other sites More sharing options...
-iliya- Posted May 17, 2022 Share #3439 Posted May 17, 2022 i have original Syno 1813+ and dx517 DSM7 and /etc/synoinfo.conf hase a 0011 1111 0000 0000 0000 0000 usbportcfg="0x3f0000" 0011 0000 0000 esataportcfg="0x300" 1111 1111 internalportcfg="0xff" USB ports after esata and skip 0000 before 1111 maxdisks="8" supportESATA="yes" eunitseq="sdi,sdj" ls /sys/block sda sdb sdc sdd sde sdf sdg sdh sdia sdib sdic sdid sdie /etc$ ls -la /sys/class/scsi_host total 0 drwxr-xr-x 2 root root 0 May 8 13:43 . drwxr-xr-x 39 root root 0 May 8 13:43 .. lrwxrwxrwx 1 root root 0 May 8 13:43 host0 -> ../../devices/pci0000:00/0000:00:1f.2/ata1/host0/scsi_host/host0 lrwxrwxrwx 1 root root 0 May 8 13:43 host1 -> ../../devices/pci0000:00/0000:00:1f.2/ata2/host1/scsi_host/host1 lrwxrwxrwx 1 root root 0 May 8 13:43 host10 -> ../../devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.0/host10/scsi_host/host10 lrwxrwxrwx 1 root root 0 May 8 13:43 host2 -> ../../devices/pci0000:00/0000:00:1f.2/ata3/host2/scsi_host/host2 lrwxrwxrwx 1 root root 0 May 8 13:43 host3 -> ../../devices/pci0000:00/0000:00:1f.2/ata4/host3/scsi_host/host3 lrwxrwxrwx 1 root root 0 May 8 13:43 host4 -> ../../devices/pci0000:00/0000:00:1f.2/ata5/host4/scsi_host/host4 lrwxrwxrwx 1 root root 0 May 8 13:43 host5 -> ../../devices/pci0000:00/0000:00:1f.2/ata6/host5/scsi_host/host5 lrwxrwxrwx 1 root root 0 May 8 13:43 host6 -> ../../devices/pci0000:00/0000:00:1c.2/0000:03:00.0/ata7/host6/scsi_host/host6 lrwxrwxrwx 1 root root 0 May 8 13:43 host7 -> ../../devices/pci0000:00/0000:00:1c.2/0000:03:00.0/ata8/host7/scsi_host/host7 lrwxrwxrwx 1 root root 0 May 8 13:43 host8 -> ../../devices/pci0000:00/0000:00:1c.3/0000:04:00.0/ata9/host8/scsi_host/host8 lrwxrwxrwx 1 root root 0 May 8 13:43 host9 -> ../../devices/pci0000:00/0000:00:1c.3/0000:04:00.0/ata10/host9/scsi_host/host9 fdisk -l |grep Disk |grep sd GPT PMBR size mismatch (225279 != 250879) will be corrected by write. The backup GPT table is not on the end of the device. This problem will be corrected by write. Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sdd: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sde: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sdf: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sdg: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sdh: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sdia: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sdic: 2.7 TiB, 3000591900160 bytes, 5860531055 sectors Disk /dev/sdib: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sdie: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sdid: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors 1 Quote Link to comment Share on other sites More sharing options...
techfriend63 Posted May 18, 2022 Share #3440 Posted May 18, 2022 13 hours ago, pocopico said: Yes, i just saw that, i'm fixing now. Edit @techfriend63 please try again Tested and it is Working!👌 Thanks for the update. Quote Link to comment Share on other sites More sharing options...
Bullseye Posted May 18, 2022 Share #3441 Posted May 18, 2022 Ok i have last question, i have my old J3455 NAS with 6.2.3 Update3 Juns Loader 918+ (CPU is apollo lake), if i want update that system to 7.1 what i should do to not lost all of my data and config (anyway i make full backup on external disk) ? First update system to latest version from DSM and restart, then take off my USB and burn tinycore-redpill and build for latest 7.1 918+ wih my old SN that i have on 6.2.3 JUNs ? Quote Link to comment Share on other sites More sharing options...
wimsan Posted May 18, 2022 Share #3442 Posted May 18, 2022 I have created two identical DS1621+ in Proxmox to "play" with Synology HA. I have tried several ways to build the HA pair but it always ends up with "volume1 on passive server crashed" i.e. not created. Building a pool/volume works fine standalone. Is there a way to build the HA pair from command line so that maybe I get more insight as to what is going wrong. Or does anyone have any other ideas to make this work? Quote Link to comment Share on other sites More sharing options...
gorski Posted May 18, 2022 Share #3443 Posted May 18, 2022 20 hours ago, pocopico said: Hi can you follow my instructions again ? I think you've got something wrong. this happened before day when you change repo links. there is no config.json file in redpill-load/config/DS3622xs+/7.0.1-42218/ Greets, Gorski Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 18, 2022 Author Share #3444 Posted May 18, 2022 47 minutes ago, gorski said: this happened before day when you change repo links. there is no config.json file in redpill-load/config/DS3622xs+/7.0.1-42218/ Greets, Gorski Its back again. 2 Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 18, 2022 Author Share #3445 Posted May 18, 2022 (edited) Hi @flyride @-iliya-, @IG-88, on a DS3622xs+ test VM that i have, i've contacted some tests and i've found that (A/B/C/D/E/F) in SataPortMap setting, are somehow acceptable values. I really dont know if that was always the case or if thats something new on these new systems. If i set SataPortMap=2F for instance, the system will scan 2 ports on the first HBA and then 22 on the second HBA. I guess someone might want to use this if he wants more than 9 ports on second HBA but only 2 on the third and more on the forth etc, so in that case, for SataPortMap, a value of SataPortMap=2A4F will scan : 1st HBA = 2 Ports 2nd HBA = 17 Ports 3rd HBA = 4 Ports 4th HBA = 22 Ports A SCANS=17 HBA Ports B SCANS=18 HBA Ports C SCANS=19 HBA Ports D SCANS=20 HBA Ports E SCANS=21 HBA Ports F SCANS=22 HBA Ports I've noticed that lower case letters in SataPortMap, are causing kernel panic. Tests : DiskIdxMap= SataPortMap=2A2 IRQ 72=2 , 73=17 , 74=2 -=> Total=21 DiskIdxMap= SataPortMap=2F2 IRQ 72=2 , 73=22 , 74=2 -=> Total=26 I've noticed also that the default boot value of HddHotPlug is 0 , (HddHotPlug=0) This probably affects the users that have empty/disconnected SATA ports. I unfortunatelly dont have any spare physical machine to test and validate fixing the "Wrong disk setting" DSM error Edited May 18, 2022 by pocopico 2 Quote Link to comment Share on other sites More sharing options...
flyride Posted May 18, 2022 Share #3446 Posted May 18, 2022 (edited) 1 hour ago, pocopico said: I've noticed that lower case letters in SataPortMap, are causing kernel panic. If it tests similarly on other platforms, we might as well code support into the script. For giggles, did you check: 30 0 31 1 32 2 33 3 34 4 35 5 36 6 37 7 38 8 39 9 3A : - 10? 3B ; - 11? 3C < - 12? 3D = - 13? 3E > - 14? 3F ? - 15? 40 @ - 16? 41 A - 17 42 B - 18 43 C - 19 44 D - 20 45 E - 21 46 F - 22 47 G - 23? ... Edited May 18, 2022 by flyride 2 Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 18, 2022 Author Share #3447 Posted May 18, 2022 (edited) 28 minutes ago, flyride said: If it tests similarly on other platforms, we might as well code support into the script. For giggles, did you check: 30 0 31 1 32 2 33 3 34 4 35 5 36 6 37 7 38 8 39 9 3A : - 10? 3B ; - 11? 3C < - 12? 3D = - 13? 3E > - 14? 3F ? - 15? 40 @ - 16? 41 A - 17 42 B - 18 43 C - 19 44 D - 20 45 E - 21 46 F - 22 47 G - 23? ... It took me couple of seconds to realize your idea EDIT : AND OMG !!! ITS EXACTLY LIKE THAT !!!! DiskIdxMap= SataPortMap=2:F IRQ 72=2 , 73=10 , 74=22 -=> Total=34 Edited May 18, 2022 by pocopico Quote Link to comment Share on other sites More sharing options...
flyride Posted May 18, 2022 Share #3448 Posted May 18, 2022 Does it crash with "O" - which would be 30 ports. That is the max number of ports on any controller I've ever seen (VMware paravirtual). The risk is that we are overrunning a fixed kernel memory structure with unknown consequences. I'll edit the satamap code to give the user the option and a warning. 1 Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 18, 2022 Author Share #3449 Posted May 18, 2022 (edited) and verified again with DiskIdxMap= SataPortMap=2=F IRQ 72=2 , 73=13 , 74=22 -=> Total=37 I've tested "a" which is 0x61 which would be port number 49 and the kernel panics. So there must be a limit. Now next goal is to find it DiskIdxMap= SataPortMap=2OF IRQ 72=2 , 73=30 , 74=22 -=> Total=54 Edited May 18, 2022 by pocopico 1 Quote Link to comment Share on other sites More sharing options...
flyride Posted May 18, 2022 Share #3450 Posted May 18, 2022 Again, just because it doesn't crash doesn't mean it isn't having a negative effect. It just means we didn't overrun into another critical structure that is obvious. PM'd updated satamap to you. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.