shrabok Posted May 20, 2022 Share #3526 Posted May 20, 2022 2 hours ago, flyride said: Ivy Lake is "older" - it can run anything not marked Haswell Skylake is not. From an architecture perspective - it can run anything. You didn't mention what platform you are running now. But you may choose DS3617xs or DS3622xs+ interchangeably at this point. Regardless, you will be asked for a Migration Install and data and DSM configurations should be preserved. Always have a backup of your data. Any 6.x can upgrade directly to 7.0.1 or 7.1 with no issues. r8168 and e1000e are usually part of the core DSM support drivers. There is a library of drivers in TCRP; selections can be manually added or you can ask the build process to try and identify your hardware "./rploader.sh build <arch-version-release> auto" and add them as needed. Thanks @flyride really appreciate the clarification! I'm currently running on DS3617xs and was hoping to go to DS3622xs+ directly and avoid a second step (which seems to be the case). Hope this helps others as well. Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 20, 2022 Share #3527 Posted May 20, 2022 @pocopico there seems to be an issue with the v9fs drivers and ds918 (42218 and 42661). it gives a recipe error when adding that ext and building the loader. someone has that issue in the proxmox thread. just letting you know. 1 Quote Link to comment Share on other sites More sharing options...
pigr8 Posted May 21, 2022 Share #3528 Posted May 21, 2022 (edited) i tried to build the latest loader for 3622, having a 9211-8i in passthrough is esxi having disks bigger than 2tb is still a problem, right? telnetted in: SynologyNAS> fdisk -l |grep Disk |grep sd fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sdb: 2048 GB, 2199023255040 bytes, 4294967295 sectors Disk /dev/sdc: 2048 GB, 2199023255040 bytes, 4294967295 sectors Disk /dev/sde: 2048 GB, 2199023255040 bytes, 4294967295 sectors Disk /dev/sdf: 2048 GB, 2199023255040 bytes, 4294967295 sectors Disk /dev/sdg: 233 GB, 250059350016 bytes, 488397168 sectors Disk /dev/sdd: 2048 GB, 2199023255040 bytes, 4294967295 sectors i have 5x 3tb disks so it seems still limited to 2tb, and /dev/sda is still missing it seems 😕 shouldn tc handle that? when i do satamap it sais that it fixes it. EDIT: same setup on 6.2.3 Jun's Loader user@DiskStation:~$ fdisk -l |grep Disk |grep sd Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sdb: 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: 232.9 GiB, 250059350016 bytes, 488397168 sectors Edited May 21, 2022 by pigr8 Quote Link to comment Share on other sites More sharing options...
Zac_Nas Posted May 21, 2022 Share #3529 Posted May 21, 2022 I am getting an error when building 920+, the dbt extension does not download, shows checksum error, anybody else getting this ? [#] Filling-in newly downloaded recipe for extension redpill-dtb platform ds920p_42661 [#] Downloading remote file https://github.com/jumkey/redpill-load/raw/develop/redpill-dtb/releases/install_rd.sh to /home/tc/redpill-load/custom/extensions/redpill-dtb/ds920p_42661/install_rd.sh ######################################################################## 100.0% [#] Verifying /home/tc/redpill-load/custom/extensions/redpill-dtb/ds920p_42661/install_rd.sh file... [ERR] [!] Checksum mismatch - expected 41a626b6af537240727e059da14a225fda7c78904fcbdc9b457a8cbf84d95a3a but computed 8de2386d48befda1c1301e7b2647ff6dae63cea9bcb28de3b6bd9a4185d5a734 *** Process will exit *** As a result my dtb file is not getting created and the disks are not recognised. Quote Link to comment Share on other sites More sharing options...
Unregistrado Posted May 21, 2022 Share #3530 Posted May 21, 2022 26 minutes ago, pigr8 said: i tried to build the latest loader for 3622, having a 9211-8i in passthrough is esxi having disks bigger than 2tb is still a problem, right? telnetted in: SynologyNAS> fdisk -l |grep Disk |grep sd fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sdb: 2048 GB, 2199023255040 bytes, 4294967295 sectors Disk /dev/sdc: 2048 GB, 2199023255040 bytes, 4294967295 sectors Disk /dev/sde: 2048 GB, 2199023255040 bytes, 4294967295 sectors Disk /dev/sdf: 2048 GB, 2199023255040 bytes, 4294967295 sectors Disk /dev/sdg: 233 GB, 250059350016 bytes, 488397168 sectors Disk /dev/sdd: 2048 GB, 2199023255040 bytes, 4294967295 sectors i have 5x 3tb disks so it seems still limited to 2tb, and /dev/sda is still missing it seems 😕 shouldn tc handle that? when i do satamap it sais that it fixes it. EDIT: same setup on 6.2.3 Jun's Loader user@DiskStation:~$ fdisk -l |grep Disk |grep sd Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sdb: 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: 232.9 GiB, 250059350016 bytes, 488397168 sectors I have a 3622 xpenology and it does work. i have 17 TB in SHR. Quote Link to comment Share on other sites More sharing options...
pigr8 Posted May 21, 2022 Share #3531 Posted May 21, 2022 1 minute ago, Unregistrado said: I have a 3622 xpenology and it does work. i have 17 TB in SHR. what HBA card do you have? If an LSI SAS2008, what firmware do you use? Quote Link to comment Share on other sites More sharing options...
Unregistrado Posted May 21, 2022 Share #3532 Posted May 21, 2022 12 minutes ago, pigr8 said: what HBA card do you have? If an LSI SAS2008, what firmware do you use? If i am not mistaken SAS2008 and flashed to IT mode latest software version. Quote Link to comment Share on other sites More sharing options...
pigr8 Posted May 21, 2022 Share #3533 Posted May 21, 2022 2 minutes ago, Unregistrado said: If i am not mistaken SAS2008 and flashed to IT mode latest software version. and what version of ESXi do you have? 7.0? Quote Link to comment Share on other sites More sharing options...
Unregistrado Posted May 21, 2022 Share #3534 Posted May 21, 2022 1 minute ago, pigr8 said: and what version of ESXi do you have? 7.0? esxi 7 U3 Quote Link to comment Share on other sites More sharing options...
naan Posted May 21, 2022 Share #3535 Posted May 21, 2022 Hi, I have an old MacMini with an i5-3210M Ivy Bridge CPU. which version should I use? I have installed bromolow DS3615xs successfully before. is there any other choice? Quote Link to comment Share on other sites More sharing options...
p3t3 Posted May 21, 2022 Share #3536 Posted May 21, 2022 @pocopico @jumkey Synology changed DS920+ 7.0.1-42218 pat recently, so need to update config 1 Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 21, 2022 Share #3537 Posted May 21, 2022 10 hours ago, pigr8 said: i tried to build the latest loader for 3622, having a 9211-8i in passthrough is esxi having disks bigger than 2tb is still a problem, right? telnetted in: SynologyNAS> fdisk -l |grep Disk |grep sd fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sdb: 2048 GB, 2199023255040 bytes, 4294967295 sectors Disk /dev/sdc: 2048 GB, 2199023255040 bytes, 4294967295 sectors Disk /dev/sde: 2048 GB, 2199023255040 bytes, 4294967295 sectors Disk /dev/sdf: 2048 GB, 2199023255040 bytes, 4294967295 sectors Disk /dev/sdg: 233 GB, 250059350016 bytes, 488397168 sectors Disk /dev/sdd: 2048 GB, 2199023255040 bytes, 4294967295 sectors i have 5x 3tb disks so it seems still limited to 2tb, and /dev/sda is still missing it seems 😕 shouldn tc handle that? when i do satamap it sais that it fixes it. EDIT: same setup on 6.2.3 Jun's Loader user@DiskStation:~$ fdisk -l |grep Disk |grep sd Disk /dev/sda: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors Disk /dev/sdb: 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: 232.9 GiB, 250059350016 bytes, 488397168 sectors No problem here. Running DS3622xs+ build DSM 7.1 42661 in VM with LSI 9211 8i pci pass thru with 5x 4tb ironwolf no issues here root@DS3622:~# fdisk -l |grep Disk |grep sd Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk /dev/sdd: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk /dev/sde: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors root@DS3622:~# Quote Link to comment Share on other sites More sharing options...
pigr8 Posted May 21, 2022 Share #3538 Posted May 21, 2022 1 hour ago, phone guy said: No problem here. Running DS3622xs+ build DSM 7.1 42661 in VM with LSI 9211 8i pci pass thru with 5x 4tb ironwolf no issues here root@DS3622:~# fdisk -l |grep Disk |grep sd Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk /dev/sdd: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors Disk /dev/sde: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors root@DS3622:~# so must be a firmware issue, do you know on what version you are? I'm on an old version because of trim support on ssd Quote Link to comment Share on other sites More sharing options...
phone guy Posted May 22, 2022 Share #3539 Posted May 22, 2022 5 hours ago, pigr8 said: so must be a firmware issue, do you know on what version you are? I'm on an old version because of trim support on ssd P20. google your hba and P20 IT MODE, there are literally hundreds of guides... many will have img/iso with all required files. I just went down that rabbit hole myself. Which card exactly do you have? Here is a starting point for you, but trust me google will have all the directions you'll need. Quote Link to comment Share on other sites More sharing options...
-iliya- Posted May 22, 2022 Share #3540 Posted May 22, 2022 (edited) В 18.05.2022 в 22:03, pocopico сказал: 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 I can run tests on real hardware, tell me what to write in user_conf for example: 1. test - 6 sata ports per MB + 16 ports per LSI1 2. test - 6 ports per MB + 16 ports per LSI1 + 8 ports per LSI2 3. test sata ports disabled in bios, only 16 ports on LSI1 + 8 ports on LSI2 I will try to find 30 real disks for tests Edited May 22, 2022 by -iliya- Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 22, 2022 Author Share #3541 Posted May 22, 2022 17 minutes ago, -iliya- said: I can run tests on real hardware, tell me what to write in user_conf for example: 1. test - 6 sata ports per MB + 16 ports per LSI1 2. test - 6 ports per MB + 16 ports per LSI1 + 8 ports per LSI2 3. test sata ports disabled in bios, only 16 ports on LSI1 + 8 ports on LSI2 I will try to find 30 real disks for tests You don’t have to find 30 disks. 30 HBA ports are OK also. Quote Link to comment Share on other sites More sharing options...
-iliya- Posted May 22, 2022 Share #3542 Posted May 22, 2022 3 минуты назад, pocopico сказал: You don’t have to find 30 disks. 30 HBA ports are OK also. real HBA i have only 24 port - 16+8 6 port on AHCI MB and what should be written to DiskIdxMap and SataPortMap as a result? Maxdisk and internalsataport? and etc Quote Link to comment Share on other sites More sharing options...
leang521 Posted May 23, 2022 Share #3543 Posted May 23, 2022 This is a Google translation tool, translated from Chinese to English. There may be grammatical errors, please forgive me I tried too much virtual machine configuration (KVM64/Host). Try to compile DS918, DVA3221, DS3622, etc. I also try to use SATA guidance and USB guidance. But every time it is guided, it leads to "Kernel Offset" error. [ 2.371160] [<ffffffff81446ea0>] ? ahci_pmp_retry_softreset+0xd0/0xd0 [ 2.371160] [<ffffffff814231cb>] ata_host_activate+0xbb/0x110 [ 2.371160] [<ffffffff81445f3b>] ahci_host_activate+0x4b/0x130 [ 2.371160] [<ffffffff813355e1>] ? pcibios_set_master+0x61/0x80 [ 2.371160] [<ffffffff814432be>] ahci_init_one+0x9ce/0xe20 [ 2.371160] [<ffffffff813379b6>] pci_device_probe+0x96/0x100 [ 2.371160] [<ffffffff813ce1c6>] driver_probe_device+0x1c6/0x280 [ 2.371160] [<ffffffff813ce2fc>] __driver_attach+0x7c/0x80 [ 2.371160] [<ffffffff813ce280>] ? driver_probe_device+0x280/0x280 [ 2.371160] [<ffffffff813cc2eb>] bus_for_each_dev+0x6b/0xa0 [ 2.371160] [<ffffffff813cdae9>] driver_attach+0x19/0x20 [ 2.371160] [<ffffffff813cd724>] bus_add_driver+0x1a4/0x1e0 [ 2.371160] [<ffffffff8192dc5b>] ? ata_sff_init+0x31/0x31 [ 2.371160] [<ffffffff813ceaeb>] driver_register+0x6b/0xc0 [ 2.371160] [<ffffffff813363a7>] __pci_register_driver+0x47/0x50 [ 2.371160] [<ffffffff8192dc74>] ahci_pci_driver_init+0x19/0x1b [ 2.371160] [<ffffffff81000341>] do_one_initcall+0x81/0x130 [ 2.371160] [<ffffffff818f26e7>] ? do_early_param+0x90/0x90 [ 2.371160] [<ffffffff818f2fb5>] kernel_init_freeable+0x14d/0x1de [ 2.371160] [<ffffffff8157601d>] ? rest_init+0x74/0x74 [ 2.371160] [<ffffffff81576026>] kernel_init+0x9/0xd3 [ 2.371160] [<ffffffff8157ba2f>] ret_from_fork+0x3f/0x80 [ 2.371160] [<ffffffff8157601d>] ? rest_init+0x74/0x74 [ 2.371160] Code: 35 16 00 48 8d 5b f8 45 8d 64 24 ff 45 85 e4 79 da 49 8d 3e e8 cb 53 fb ff 5b 41 5c 41 5d 41 5e 41 8d 07 41 5f 5d c3 48 8b 43 28 <48> 83 b8 20 01 00 00 00 0f 85 ec fe ff ff e9 62 ff ff ff 41 bf [ 2.371160] RIP [<ffffffff8141c8a7>] ata_host_start.part.38+0x197/0x1c0 [ 2.371160] RSP <ffff880179123be8> [ 2.371160] CR2: 0000000000000120 [ 2.371160] ---[ end trace ba65eee5942df4d0 ]--- [ 2.422739] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 [ 2.422739] [ 2.423716] Kernel Offset: disabled [ 2.423716] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 [ 2.423716] My virtual configuration file(.conf) is as follows. boot: order=sata1 cores: 4 cpu: host ide0: none,media=cdrom machine: q35 memory: 4096 meta: creation-qemu=6.1.0,ctime=1652514353 name: DVA3221 net0: virtio=00:11:32:DC:60:72,bridge=vmbr0,firewall=1 numa: 0 ostype: l26 sata0: data-zfs:vm-107-disk-0,size=1G sata1: data-zfs:vm-107-disk-2,size=160M sata2: data-zfs:vm-107-disk-1,backup=0,size=1000G serial0: socket smbios1: uuid=9ccd8891-7d4b-4b01-bdda-7485538927c3 sockets: 1 vmgenid: f2e20777-1bd3-40d7-be6b-2190cfc97203 My virtual machine hardware is: 32 X Intel (R) Xeon (R) CPU E5-2630 V3 @ 2.40GHz (2 slot). I saw the same problem with Ideasman69. But I asked him without any reply. saw your previous comments, but I didn't find useful information in @haydibeg Guide. Can you provide me with more help. Quote Link to comment Share on other sites More sharing options...
wimsan Posted May 23, 2022 Share #3544 Posted May 23, 2022 Hi, I have a TCRP DS1621+ running in Proxmox. If I select VirtIO for the network interface it works but Synology cannot/does not get a status from the interface. If I select RTL8139 it gets a status of 100 Mbps Full Duplex even though it runs on 1 Gbps. I built the bootloader as follows: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh ext v1000-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json ./rploader.sh ext v1000-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/r8101/rpext-index.json ./rploader.sh serialgen DS1621+ ./rploader.sh identifyusb now ./rploader.sh satamap now answer: 6 disks controller 1 answer: 6 disks controller 2 SataPortMap=66 DiskIdxMap=0006 ./rploader.sh build v1000-7.1.0-42661 Any ideas on how to get an interface status when using VirtIO? Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 23, 2022 Author Share #3545 Posted May 23, 2022 26 minutes ago, leang521 said: This is a Google translation tool, translated from Chinese to English. There may be grammatical errors, please forgive me I tried too much virtual machine configuration (KVM64/Host). Try to compile DS918, DVA3221, DS3622, etc. I also try to use SATA guidance and USB guidance. But every time it is guided, it leads to "Kernel Offset" error. [ 2.371160] [<ffffffff81446ea0>] ? ahci_pmp_retry_softreset+0xd0/0xd0 [ 2.371160] [<ffffffff814231cb>] ata_host_activate+0xbb/0x110 [ 2.371160] [<ffffffff81445f3b>] ahci_host_activate+0x4b/0x130 [ 2.371160] [<ffffffff813355e1>] ? pcibios_set_master+0x61/0x80 [ 2.371160] [<ffffffff814432be>] ahci_init_one+0x9ce/0xe20 [ 2.371160] [<ffffffff813379b6>] pci_device_probe+0x96/0x100 [ 2.371160] [<ffffffff813ce1c6>] driver_probe_device+0x1c6/0x280 [ 2.371160] [<ffffffff813ce2fc>] __driver_attach+0x7c/0x80 [ 2.371160] [<ffffffff813ce280>] ? driver_probe_device+0x280/0x280 [ 2.371160] [<ffffffff813cc2eb>] bus_for_each_dev+0x6b/0xa0 [ 2.371160] [<ffffffff813cdae9>] driver_attach+0x19/0x20 [ 2.371160] [<ffffffff813cd724>] bus_add_driver+0x1a4/0x1e0 [ 2.371160] [<ffffffff8192dc5b>] ? ata_sff_init+0x31/0x31 [ 2.371160] [<ffffffff813ceaeb>] driver_register+0x6b/0xc0 [ 2.371160] [<ffffffff813363a7>] __pci_register_driver+0x47/0x50 [ 2.371160] [<ffffffff8192dc74>] ahci_pci_driver_init+0x19/0x1b [ 2.371160] [<ffffffff81000341>] do_one_initcall+0x81/0x130 [ 2.371160] [<ffffffff818f26e7>] ? do_early_param+0x90/0x90 [ 2.371160] [<ffffffff818f2fb5>] kernel_init_freeable+0x14d/0x1de [ 2.371160] [<ffffffff8157601d>] ? rest_init+0x74/0x74 [ 2.371160] [<ffffffff81576026>] kernel_init+0x9/0xd3 [ 2.371160] [<ffffffff8157ba2f>] ret_from_fork+0x3f/0x80 [ 2.371160] [<ffffffff8157601d>] ? rest_init+0x74/0x74 [ 2.371160] Code: 35 16 00 48 8d 5b f8 45 8d 64 24 ff 45 85 e4 79 da 49 8d 3e e8 cb 53 fb ff 5b 41 5c 41 5d 41 5e 41 8d 07 41 5f 5d c3 48 8b 43 28 <48> 83 b8 20 01 00 00 00 0f 85 ec fe ff ff e9 62 ff ff ff 41 bf [ 2.371160] RIP [<ffffffff8141c8a7>] ata_host_start.part.38+0x197/0x1c0 [ 2.371160] RSP <ffff880179123be8> [ 2.371160] CR2: 0000000000000120 [ 2.371160] ---[ end trace ba65eee5942df4d0 ]--- [ 2.422739] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 [ 2.422739] [ 2.423716] Kernel Offset: disabled [ 2.423716] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 [ 2.423716] My virtual configuration file(.conf) is as follows. boot: order=sata1 cores: 4 cpu: host ide0: none,media=cdrom machine: q35 memory: 4096 meta: creation-qemu=6.1.0,ctime=1652514353 name: DVA3221 net0: virtio=00:11:32:DC:60:72,bridge=vmbr0,firewall=1 numa: 0 ostype: l26 sata0: data-zfs:vm-107-disk-0,size=1G sata1: data-zfs:vm-107-disk-2,size=160M sata2: data-zfs:vm-107-disk-1,backup=0,size=1000G serial0: socket smbios1: uuid=9ccd8891-7d4b-4b01-bdda-7485538927c3 sockets: 1 vmgenid: f2e20777-1bd3-40d7-be6b-2190cfc97203 My virtual machine hardware is: 32 X Intel (R) Xeon (R) CPU E5-2630 V3 @ 2.40GHz (2 slot). I saw the same problem with Ideasman69. But I asked him without any reply. saw your previous comments, but I didn't find useful information in @haydibeg Guide. Can you provide me with more help. can you please sent me the SataPortMap setting ? It should be in your user_config.json. Quote Link to comment Share on other sites More sharing options...
leang521 Posted May 23, 2022 Share #3546 Posted May 23, 2022 (edited) 1 hour ago, pocopico said: can you please sent me the SataPortMap setting ? It should be in your user_config.json. I have tested the following configurations respectively "SataPortMap": "02", "DiskIdxMap": "0000" "SataPortMap": "04", "DiskIdxMap": "0000" "SataPortMap": "24", "DiskIdxMap": "0000" Edited May 23, 2022 by leang521 Quote Link to comment Share on other sites More sharing options...
pocopico Posted May 23, 2022 Author Share #3547 Posted May 23, 2022 (edited) 4 minutes ago, leang521 said: I have tested the following configurations respectively "SataPortMap": "02", "DiskIdxMap": "0000" "SataPortMap": "04", "DiskIdxMap": "0000" "SataPortMap": "24", "DiskIdxMap": "0000" The 0 in first HBA is known to cause kernel panic. Try "SataPortMap": "1" and see how it goes Edited May 23, 2022 by pocopico Quote Link to comment Share on other sites More sharing options...
john_matrix Posted May 23, 2022 Share #3548 Posted May 23, 2022 Hello, I am currently upgrading my Proxmox node with a Ryzen CPU and I am facing issues for building DS1621+ loader: Can someone point me where I am mistaking? ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DS1621+ ./rploader.sh identifyusb now ./rploader.sh satamap now ./rploader.sh ext v1000-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/develop/redpill-virtio/rpext-index.json ./rploader.sh ext v1000-7.1.0-42661 add https://raw.githubusercontent.com/dodo-dk/rp-ext/main/acpid/rpext-index.json ./rploader.sh backup now ./rploader.sh build v1000-7.1.0-42661 I have tried with DS3622xs+ and it works properly but I would like to keep same CPU brand. Many thanks! Quote Link to comment Share on other sites More sharing options...
flyride Posted May 23, 2022 Share #3549 Posted May 23, 2022 4 hours ago, pocopico said: The 0 in first HBA is known to cause kernel panic. Try "SataPortMap": "1" and see how it goes @leang521 This issue was fixed recently in script. PocoPico is correct but you may not want to do manually. if you run ./rploader.sh update now (to get the latest script) and ./rploader.sh satamap now it will fix it automatically. Quote Link to comment Share on other sites More sharing options...
leang521 Posted May 24, 2022 Share #3550 Posted May 24, 2022 (edited) 15 hours ago, pocopico said: The 0 in first HBA is known to cause kernel panic. Try "SataPortMap": "1" and see how it goes 10 hours ago, flyride said: @leang521 This issue was fixed recently in script. PocoPico is correct but you may not want to do manually. if you run ./rploader.sh update now (to get the latest script) and ./rploader.sh satamap now it will fix it automatically. Thank you very much. I updated the "RedPill-Tinycore-loader" today, which can indeed be guided normally. But there is a small problem. The current execution of "./rploader.sh Satamap now" has no manual adjustment project. Automatic generated "SataPortMap": "11", "DiskIdxMap": "1010" Such configuration. If you directly use this configuration guidance, you can't find the hard disk. You also need to adjust the conf file manually. "SataPortMap": "14", "DiskIdxMap": "1002" Another suggestion. When compiling repeatedly, Synology limits the download speed of the PAT file, with a minimum of only 2kb/s. So I hope to manually upload the pat file to the system. And increase the mirror space to save the PAT file. Edited May 24, 2022 by leang521 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.