pigr8

and what version of ESXi do you have? 7.0?

what HBA card do you have? If an LSI SAS2008, what firmware do you use?

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

sorry to bother, are the issues with the LSI passthrou card still present with the 3622 build?

do mpt2sas and lsi card in passthrough still have problems in esxi? Thorgroup definitive MIA eh?

so you must be in the wrong place playing with the wrong toys, this is a developer section on not an even alpha argument, if you cant follow and undestand that then that’s not for you, it’s easy to understand. imho, without even refering to any brand but generally speaking, sharing copyrighted stuff is plain stupid. still no words about ttg hey? almost 2 months of silence, i hope at least they are ok.

for my testings with an LSI, yes.

that config is not better than what he has, the 1240v2 is even older.. :S

edit: ops didn't see the other replies sorry

inside the container add the extension ( ./ext-manager.sh add 'https://raw.githubusercontent.com/RedPill-TTG/redpill-sas-activator/master/rpext-index.json' ) and then do "make -C /opt/ build_all" if you exit the container it's normal that any mod you did is lost, so build from inside

try the sas-activator extension, should autodetect the card and load the correct one from the stock dsm modules

you can find it in redpill-load folder inside the container.

will do today if i manage thanks

i made some tests with the 6.2.4 loader for ds3615xs, that is based on 3.10.105 like 6.2.3 so the kernel "should" be the same? using the stock mpt2sas.ko that comes with dsm the hba loads, all disks can be seen but still not more than 2tb and fdisk gives the same error "fdisk: device has more than 2^32 sectors, can't use all of them"... and the "want_idx 1 index N" spam error after every disk detect is still there. so i tried to load the mpt2sas.ko that comes with 6.2.3 currently in use with jun's loader DiskStation> insmod mpt2sas.ko [ 405.096449] mpt2sas: Unknown symbol syno_disk_start_time_set (err 0) insmod: can't insert 'mpt2sas.ko': unknown symbol in module, or unknown parameter so i guess that's a fail too.. last i tried to use the new @pocopico mpt2sas.ko compiled on v14.1 (240kb module or so), but on 6.2.4 it crashes Loading kmod #0 "mpt2sas.ko" for pocopico.mpt2sas (args: ) [ 2.836262] mpt2sas version 14.100.00.00 loaded [ 2.837953] scsi1 : Fusion MPT SAS Host [ 2.841747] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (6084704 kB) [ 2.843552] mpt2sas 0000:0b:00.0: irq 73 for MSI/MSI-X [ 2.844836] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 73 [ 2.846311] mpt2sas0: iomem(0x00000000fd3f0000), mapped(0xffffc90008160000), size(65536) [ 2.846815] mpt2sas0: ioport(0x0000000000005000), size(256) [ 2.962906] mpt2sas0: Allocated physical memory: size(7418 kB) [ 2.963909] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432) [ 2.965323] mpt2sas0: Scatter Gather Elements per IO(128) [ 3.024478] mpt2sas0: LSISAS2008: FWVersion(16.00.00.00), ChipRevision(0x03), BiosVersion(00.00.00.00) [ 3.025410] mpt2sas0: Dell 6Gbps SAS HBA: Vendor(0x1000), Device(0x0072), SSVID(0x1028), SSDID(0x1F1C) [ 3.026746] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 3.028508] mpt2sas0: sending port enable !! [ 3.035735] mpt2sas0: host_add: handle(0x0001), sas_addr(0x590b11c027f7ff00), phys(8) [ 3.042340] scsi 1:0:0:0: Direct-Access WDC WD30EFRX-68EUZN0 0A82 PQ: 0 ANSI: 6 [ 3.044192] scsi 1:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x50014ee26320545e) [ 3.046965] scsi 1:0:0:0: SATA: enclosure_logical_id(0x590b11c027f7ff00), slot(3) [ 3.049091] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 3.050033] scsi 1:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 3.052209] BUG: unable to handle kernel paging request at ffffffffa00cd238 [ 3.053086] IP: [<ffffffff8136d4f0>] syno_sata_pmp_read_emid+0x1f0/0x1f0 [ 3.053896] PGD 1810067 PUD 1811063 PMD 1b4946067 PTE 0 [ 3.054984] Oops: 0000 [#1] SMP [ 3.055004] Modules linked in: mpt2sas(OF+) usb_storage xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common [ 3.057984] CPU: 0 PID: 19 Comm: kworker/u4:1 Tainted: GF O 3.10.105 #25556 his mpt2sas.ko works ok for 7.0 and 7.0.1 (3.10.108) and does not have the "want_idx 1 index N" error while loading the disks on boot, but still not more than 2tb. Loading kmod #0 "mpt2sas.ko" for pocopico.mpt2sas (args: ) [ 1.999107] mpt2sas version 14.100.00.00 loaded [ 2.000670] scsi1 : Fusion MPT SAS Host [ 2.004494] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (6084496 kB) [ 2.005976] mpt2sas 0000:0b:00.0: irq 73 for MSI/MSI-X [ 2.007928] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 73 [ 2.008930] mpt2sas0: iomem(0x00000000fd3f0000), mapped(0xffffc90008360000), size(65536) [ 2.010764] mpt2sas0: ioport(0x0000000000005000), size(256) [ 2.025982] tsc: Refined TSC clocksource calibration: 2394.551 MHz [ 2.027356] Switching to clocksource tsc [ 2.128032] mpt2sas0: Allocated physical memory: size(7418 kB) [ 2.129031] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432) [ 2.130888] mpt2sas0: Scatter Gather Elements per IO(128) [ 2.190638] mpt2sas0: LSISAS2008: FWVersion(16.00.00.00), ChipRevision(0x03), BiosVersion(00.00.00.00) [ 2.192069] mpt2sas0: Dell 6Gbps SAS HBA: Vendor(0x1000), Device(0x0072), SSVID(0x1028), SSDID(0x1F1C) [ 2.194285] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 2.198186] mpt2sas0: sending port enable !! [ 2.205992] mpt2sas0: host_add: handle(0x0001), sas_addr(0x590b11c027f7ff00), phys(8) [ 2.212685] scsi 1:0:0:0: Direct-Access WDC WD30EFRX-68EUZN0 0A82 PQ: 0 ANSI: 6 [ 2.214318] scsi 1:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x50014ee26320545e) [ 2.217098] scsi 1:0:0:0: SATA: enclosure_logical_id(0x590b11c027f7ff00), slot(3) [ 2.217308] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 2.218117] scsi 1:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 2.219936] sd 1:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) [ 2.221619] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 2.225891] sd 1:0:0:0: [sdb] Write Protect is off [ 2.227269] sd 1:0:0:0: [sdb] Mode Sense: 7f 00 10 08 [ 2.229265] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA [ 2.454299] mpt2sas0: port enable: SUCCESS :: Loading kernel modules from extensions ... [ OK ] :: Executing "on_boot" custom scripts ... Running "check-mpt2sas.sh" for pocopico.mpt2sas->on_boot Loading module MPT 2 SAS -> Module MPT 2 SAS loaded succesfully Ran "check-mpt2sas.sh" for pocopico.mpt2sas->on_boot - exit=0 Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot Confirmed a valid-looking /dev/synoboot device Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0 Running "load-builtin-sas.sh" for thethorgroup.sas-activator->on_boot Loading SAS controller(s) driver(s) Ran "load-builtin-sas.sh" for thethorgroup.sas-activator->on_boot - exit=0 DiskStation> fdisk -l Disk /dev/synoboot: 128 MB, 134217728 bytes, 262144 sectors 16 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/synoboot1 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux /dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux /dev/synoboot3 15,205,63 16,81,1 253952 262143 8192 4096K 83 Linux fdisk: device has more than 2^32 sectors, can't use all of them Disk /dev/sdb: 2048 GB, 2199023255040 bytes, 4294967295 sectors 267349 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/sdb1 0,0,1 1023,254,63 1 4294967295 4294967295 2047G ee EFI GPT fdisk: device has more than 2^32 sectors, can't use all of them

it's the same config as usual, stock debian vm fresh install snapshot, docker, fresh extracted redpill-tool-chain_x86_64_v0.11, in the bromolow_user_config just added sn and mac, then launched build gives that error, meh.. does not apply on the 7.0 build, those work fine. teach me master!

now i'm curious to check redpill on 6.2.4 that on bromolow has kernel 3.10.105 same as 6.2.3 with jun's and mpt2sas.ko should be the same. since on jun's everything works fine the same stuff should work on redpill, not giving bugs like the >2Tb edit: @haydibe mm is there a problem with 0.11? => [extract 2/2] ADD downloads/ / 15.8s => [stage-1 3/8] RUN git clone https://github.com/RedPill-TTG/redpill-lkm.git -b master /opt/redpill-lkm && git clone https://github.com/r0bb10/redpill-load. 3.3s => [stage-1 4/8] COPY --from=extract /opt/kernel-bromolow-6.2.4-25556 11.3s => ERROR [stage-1 5/8] RUN if [ "apollolake" = "bromolow" ]; then echo '+' > /opt/kernel-bromolow-6.2.4-25556/.scmversion; fi && if [ "kernel" = "kernel" ]; th 0.3s ------ > [stage-1 5/8] RUN if [ "apollolake" = "bromolow" ]; then echo '+' > /opt/kernel-bromolow-6.2.4-25556/.scmversion; fi && if [ "kernel" = "kernel" ]; then cp /opt/kernel-bromolow-6.2.4-25556/synoconfigs/bromolow /opt/kernel-bromolow-6.2.4-25556/.config && make -C /opt/kernel-bromolow-6.2.4-25556 oldconfig && make -C /opt/kernel-bromolow-6.2.4-25556 modules_prepare ; fi: #11 0.277 cp: cannot stat '/opt/kernel-bromolow-6.2.4-25556/synoconfigs/bromolow': No such file or directory ------ executor failed running [/bin/sh -c if [ "apollolake" = "$TARGET_PLATFORM" ]; then echo '+' > ${LINUX_SRC}/.scmversion; fi && if [ "$COMPILE_WITH" = "kernel" ]; then cp ${LINUX_SRC}/synoconfigs/${TARGET_PLATFORM} ${LINUX_SRC}/.config && make -C ${LINUX_SRC} oldconfig && make -C ${LINUX_SRC} modules_prepare ; fi]: exit code: 1 same error building apollolake

kernel it the same, try to clone the ds918p_41890.json recipe to ds918p_42218.json maybe he can test and report if works (should).

yeah but still not clear why the .105 .ko works fine on jun's loader (i assume he didn't touch that .ko and it's synologys untouched) and the synologys .108 does not.

@jumkey fork does does not have Bootwait in the bundled-exts.json so why your building fails integrating it is probably your side problem..

oh wow 😮 the ancient kernel could explain why >2tb not working but in jun's loader with 3.10.105 everything works 😮 so not sure what to guess. yeah i banged my head around this a lot trying understanding why it does that (reserving /dev/sdA), a bug could explain this and jun's loader fixes that, will add an issue on gh as requested. that sata_shim patch just gives that error on the stock mpt2sas.ko, it does not affect @pocopico compiled driver even if it's older (again guessing here). again, that explains a lot, gonna ditch this method immediately. yeah -_- thanks hp, noticed this long time ago.. like the missing pcie bifurcation option that could really improve the microserver -_- oh have to check this out.

mpt2sas.ko is already present on the ds3615xs, with the latest redpill there is a patch to fix names so you can use that .ko simply using supportsas=yes (this activates the load of that .ko on boot). sas-activator just loads the same .ko without the need of supportsas=yes, it autodetects the LSI if present and load the correct .ko accordingly. using the latest redpill with the patch probably breaks something in that .ko, so you could use the mpt2sas ext from @pocopico that is compiled in v14 (stock is v20) and does not have that break. from my testing, you should test also and report.

ah no i did not add ds918+ on my fork, just the ds3615xs, it's a personal fork to handle just my hw.. you can find the proper config for that on jumkeys github what you mean with proper config folder? https://github.com/jumkey/redpill-load/blob/develop/config/DS918%2B/7.0.1-42218/config.json

70-disk are not loaded too, well i tried one didn't work so..

https://github.com/r0bb10/rp-ext there you have some extensions that work with 7.0.1-42218, sas-activator too badly patched the work from others, credits to them. edit: if you want i have also the redpill-loader here https://github.com/r0bb10/redpill-load that has everything to build 7.0.1-42218, just add this code to @haydibe0.11 builder and it works. if you build it without ani extra extension the build proceeds with only "thethorgroup.boot-wait" in the bundled-exts { "id": "bromolow-7.0.1-42218", "platform_version": "bromolow-7.0.1-42218", "user_config_json": "bromolow_user_config.json", "docker_base_image": "debian:8-slim", "compile_with": "toolkit_dev", "redpill_lkm_make_target": "prod-v7", "downloads": { "kernel": { "url": "https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/bromolow-source/linux-3.10.x.txz/download", "sha256": "18aecead760526d652a731121d5b8eae5d6e45087efede0da057413af0b489ed" }, "toolkit_dev": { "url": "https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.bromolow-7.0.dev.txz/download", "sha256": "a5fbc3019ae8787988c2e64191549bfc665a5a9a4cdddb5ee44c10a48ff96cdd" } }, "redpill_lkm": { "source_url": "https://github.com/RedPill-TTG/redpill-lkm.git", "branch": "master" }, "redpill_load": { "source_url": "https://github.com/r0bb10/redpill-load.git", "branch": "master" } },

oh, this makes sense.. that's why the bootloader disk can be adjusted to 0C and gets out of the way leaving /dev/sda free.. btw i have a fork of redpill with dsm 7.0.1-42218 badly patching stuff from pocopico and jumkey repos if anyone wants to try..