Orphée Posted August 22, 2021 Share #651 Posted August 22, 2021 37 minutes ago, hoangminh88 said: Can you write a tutorial? We are not yet at "tutorial stage" Keep away from it until it is at least considered as a stable beta... 1 Link to comment Share on other sites More sharing options...
Orphée Posted August 22, 2021 Share #652 Posted August 22, 2021 @ilovepancakes I was able to do the same as you with Burp to bypass unknown result and I confirm this "workaround" work on ESXi ... I have yet to try with LSI board passthrough but I don't have a spare drive to test currently... Link to comment Share on other sites More sharing options...
wahabe Posted August 22, 2021 Share #653 Posted August 22, 2021 59 minutes ago, hoangminh88 said: Can you write a tutorial? for test only replace the user_config.json.template (docker folder) and changed vid pid sn mac user_config.json.zip 1 Link to comment Share on other sites More sharing options...
Orphée Posted August 22, 2021 Share #654 Posted August 22, 2021 So I tried to passthrough LSI 8i IT card directly to 6.2.4 and 7.0 beta VMs No luck, no disk detected here are logs from 7.0 VM telnet_7.0_21_lsi.log dmesg_hba.txt messages_hba.txt Link to comment Share on other sites More sharing options...
haydibe Posted August 22, 2021 Share #655 Posted August 22, 2021 Does `lspci -k` even show that the .ko is assigned to the controller? Link to comment Share on other sites More sharing options...
yanjun Posted August 22, 2021 Share #656 Posted August 22, 2021 35 minutes ago, Orphée said: 所以我尝试将 LSI 8i IT 卡直接传递到 6.2.4 和 7.0 beta VM 没有运气,没有检测到磁盘 这是来自 7.0 VM 的日志 telnet_7.0_21_lsi.log 198.24 kB · 3 次下载 dmesg_hba.txt 202.17 kB · 3 次下载 消息_hba.txt 427.86 kB · 5 次下载 Current stage redpill deficiency HBA Demand mpt2sas / mpt3sas driver, the reason why it is impossibleIn this 1 Link to comment Share on other sites More sharing options...
Orphée Posted August 22, 2021 Share #657 Posted August 22, 2021 1 minute ago, haydibe said: Does `lspci -k` even show that the .ko is assigned to the controller? I have to re-stop my PROD Jun's Xpenology, stop ESXi, remove my 4 prod disks, place my temp test disk, reboot ESXi, and start 7.0 test VM... Comparing dmesg from Jun's loader with redpill I don't see in redpill dmesg any reference to : mpt2sas From my Jun's loader dmesg [ 1.445556] megasas: 06.506.00.00-rc1 Sat. Feb. 9 17:00:00 PDT 2013 [ 1.449366] mpt2sas version 20.00.00.00 loaded [ 1.449589] scsi31 : Fusion MPT SAS Host [ 1.451133] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (4055204 kB) [ 1.523249] mpt2sas0: MSI-X vectors supported: 1, no of cores: 2, max_msix_vectors: -1 [ 1.523262] mpt2sas 0000:0b:00.0: irq 77 for MSI/MSI-X [ 1.524207] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 77 [ 1.524209] mpt2sas0: iomem(0x00000000fd3fc000), mapped(0xffffc90008240000), size(16384) [ 1.524211] mpt2sas0: ioport(0x0000000000005000), size(256) [ 1.560214] tsc: Refined TSC clocksource calibration: 3492.075 MHz [ 1.560217] Switching to clocksource tsc [ 1.638116] mpt2sas0: Allocated physical memory: size(7445 kB) [ 1.638119] mpt2sas0: Current Controller Queue Depth(3305), Max Controller Queue Depth(3432) [ 1.638121] mpt2sas0: Scatter Gather Elements per IO(128) [ 1.696633] mpt2sas0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00) [ 1.696635] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 1.696766] mpt2sas0: sending port enable !! [ 1.700974] mpt2sas0: host_add: handle(0x0001), sas_addr(0x5003005703dbf193), phys(8) [ 1.707097] mpt2sas0: port enable: SUCCESS Do I miss something about mtp2sas ? I'm still trying to understand how DiskIdxMap and SataPortMap works... maybe I'm missing something with it... Link to comment Share on other sites More sharing options...
psychoboi32 Posted August 22, 2021 Share #658 Posted August 22, 2021 yes there is no mpt2sas and mpt3sas and megaraid.ko on redpill you have to inserted on them while building you can get those .ko from @ig-88 extra.lzma pack and then paste there and in loader you have to load it last time i loaded it was stuck at booting so i will apply patch very caution [emoji3544] Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
haydibe Posted August 22, 2021 Share #659 Posted August 22, 2021 (edited) 22 minutes ago, Orphée said: I'm still trying to understand how DiskIdxMap and SataPortMap works... maybe I'm missing something with it... DiskIdxMap is a two digit hex value that indicates per SataPort where its first device start. StatPortMap is a single digit integer value that indicates how many ports a sata controller provides. `DiskIdxMap=0008 SataPortMap=82` for instance would provide 8 ports starting at 00 (=drive 1 in the ui) and a second controller with two ports starting at 08 (=drive 9 in the ui). You should check with lcpsi how many controllers are actualy detected and assign values for each of them! I always though their number in the pci bus would indicate their possition in DiskIdxMap and SataPortMap, but it apears to be not the case. I alway have to play arround to find out which Port is which controller... Though, I am currious what `sata_uid=1 sata_pcislot=5` actualy means? Does it specify the location of the sata_dom drive? On my Proxmox bromollow + lsi box with june's loader, I used usb boot instead of sata_dom and did not specify these two settings and it still work as desired - but I had to specify DiskIdxMap and SataPortMap to get the right order. Edited August 22, 2021 by haydibe 1 1 Link to comment Share on other sites More sharing options...
mcdull Posted August 22, 2021 Share #660 Posted August 22, 2021 (edited) May I know what is the targeted minimum hardware for redpill project? I am curious if my idle QNAP TS-439 Pro II+ with 32bit atom (cpu:D410) is able to boot 6.2.4. Thanks. Edited August 22, 2021 by mcdull Link to comment Share on other sites More sharing options...
haydibe Posted August 22, 2021 Share #661 Posted August 22, 2021 (edited) According https://ark.intel.com/content/www/us/en/ark/products/43517/intel-atom-processor-d410-512k-cache-1-66-ghz.html, it is a x86_64 cpu with an astonishing passmark value of 164 - I didn't knew that numbers could go that low ^^. Just for comparison the Celeron J3455 in a DS918+ has a passmark of 2259. Given that DSM is already bloody slugish on original boxes, you don't want to put it on a system that is 13 times slower than an original DS918+ Edited August 22, 2021 by haydibe 2 Link to comment Share on other sites More sharing options...
mcdull Posted August 22, 2021 Share #662 Posted August 22, 2021 oh, thx... some discussion on web said it was 32bit. And I checked it was x86-64. hope it works. 1 Link to comment Share on other sites More sharing options...
flyride Posted August 22, 2021 Share #663 Posted August 22, 2021 (edited) 2 hours ago, mcdull said: I am curious if my idle QNAP TS-439 Pro II+ with 32bit atom (cpu:D410) is able to boot 6.2.4. FWIW it is not a 32-bit chip, it's a 64-bit chip (EDIT: someone else pointed out already). It's also the same CPU that the DS212+/DS412+/DS1812+ models used and they can run 6.2.4. Edited August 22, 2021 by flyride Link to comment Share on other sites More sharing options...
haydibe Posted August 22, 2021 Share #664 Posted August 22, 2021 (edited) Hmm, according https://www.synology-wiki.de/index.php/Welchen_Prozessortyp_besitzt_mein_System? only DS710+ used a D410. The specs for QNAP TS-439 Pro II+ seem hard to track.. So you mean it didn't use a Atom D410 cpu? Edited August 22, 2021 by haydibe url required encoding of the ? character Link to comment Share on other sites More sharing options...
flyride Posted August 22, 2021 Share #665 Posted August 22, 2021 Hmm I must have had a mini PC of the same vintage that used the D410, that is what stuck in my head. D410 is pretty anemic - only 1 HT core. QNAP TS-439 Pro II used the D410, the II+ used the D425. Only difference is a slight clock speed bump. Link to comment Share on other sites More sharing options...
tbc0309 Posted August 23, 2021 Share #666 Posted August 23, 2021 The reason for this installation error is that there is an error in executing the external "update" binary file. The specific operation method is: manually modify "scemd" in the "/usr/syno/bin" directory, prohibit him from executing the "update" binary file, and instead point to a script defined by himself to solve the file parsing during installation. Link to comment Share on other sites More sharing options...
tbc0309 Posted August 23, 2021 Share #667 Posted August 23, 2021 Use IDA Pro decompile software to modify "scemd". God told me that only by doing so can the physical machine be installed normally. but I don't know how to modify it... Link to comment Share on other sites More sharing options...
jukito Posted August 23, 2021 Share #668 Posted August 23, 2021 On 8/20/2021 at 1:24 PM, scoobdriver said: OK , I will try with 6.2.4 . With 7.0 I get a message that the drive does not meet requirements , to create a pool / volume . . (it has been reported) my user_config.json is similar. Try this: https://github.com/RedPill-TTG/redpill-lkm/issues/14#issuecomment-903683483 Link to comment Share on other sites More sharing options...
Orphée Posted August 23, 2021 Share #669 Posted August 23, 2021 44 minutes ago, jukito said: Try this: https://github.com/RedPill-TTG/redpill-lkm/issues/14#issuecomment-903683483 I tried and it works, but same a "Burp". It is a workaround as you then have the warning message Link to comment Share on other sites More sharing options...
jukito Posted August 23, 2021 Share #670 Posted August 23, 2021 1 hour ago, Orphée said: I tried and it works, but same a "Burp". It is a workaround as you then have the warning message Sure, but useful for testing. Link to comment Share on other sites More sharing options...
Orphée Posted August 23, 2021 Share #671 Posted August 23, 2021 regarding mpt2sas and LSI passthrough It is in /usr/lib/modules/ Do I just have to add some modprobe at boot ? Link to comment Share on other sites More sharing options...
Orphée Posted August 23, 2021 Share #672 Posted August 23, 2021 (edited) So I added in : /usr/lib/modules-load.d/ a new file named : 70-disk-0000-mpt2sas.conf with content : mpt2sas then I tried again to boot and check Card is detected, disk is also detected : root@Xpen_70:/usr/lib/modules-load.d# fdisk -l Disk /dev/synoboot: 128 MiB, 134217728 bytes, 262144 sectors Disk model: TYPE D 3SE Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xf110ee87 Device Boot Start End Sectors Size Id Type /dev/synoboot1 2048 100351 98304 48M 83 Linux /dev/synoboot2 100352 253951 153600 75M 83 Linux /dev/synoboot3 253952 262143 8192 4M 83 Linux Disk /dev/sda: 16 GiB, 17179869184 bytes, 33554432 sectors Disk model: Virtual SATA Hard Drive Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x36b8558a Device Boot Start End Sectors Size Id Type /dev/sda1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sda2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sda3 9177088 33554431 24377344 11.6G 83 Linux Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sas1: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: ST1000DM003-XXXXXX Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xeXXXXXX Disk /dev/zram0: 1.2 GiB, 1236271104 bytes, 301824 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram1: 1.2 GiB, 1236271104 bytes, 301824 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md2: 11.6 GiB, 12480151552 bytes, 24375296 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/cachedev_0: 11.6 GiB, 12480151552 bytes, 24375296 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes But disk not seen in DSM GUI. (my disk is damaged actually I don't have a good spare one to test) So better but I still probably miss something. [ 5.316418] mpt2sas version 20.00.00.00 loaded [ 5.316534] scsi34 : Fusion MPT SAS Host [ 5.316583] I/O scheduler elevator not found [ 5.316715] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (4022232 kB) [ 5.391363] mpt2sas0: MSI-X vectors supported: 1, no of cores: 2, max_msix_vectors: -1 [ 5.392412] mpt2sas 0000:0b:00.0: irq 74 for MSI/MSI-X [ 5.393445] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 74 [ 5.393589] mpt2sas0: iomem(0x00000000fd3fc000), mapped(0xffffc90008128000), size(16384) [ 5.394417] mpt2sas0: ioport(0x0000000000005000), size(256) [ 5.510288] mpt2sas0: Allocated physical memory: size(7445 kB) [ 5.511278] mpt2sas0: Current Controller Queue Depth(3305), Max Controller Queue Depth(3432) [ 5.512292] mpt2sas0: Scatter Gather Elements per IO(128) [ 5.575413] mpt2sas0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00) [ 5.576712] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) [ 5.578687] mpt2sas0: sending port enable !! [ 5.581711] mpt2sas0: host_add: handle(0x0001), sas_addr(0x5003005703dbf193), phys(8) [ 5.590217] mpt2sas0: port enable: SUCCESS [ 5.590431] I/O scheduler elevator not found [ 5.591265] I/O scheduler elevator not found [ 5.593443] scsi 34:0:0:0: Direct-Access ATA ST1000DM003-XXXXXX HP51 PQ: 0 ANSI: 6 [ 5.594263] scsi 34:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221103000000), phy(3), device_name(0x5000c500874478b3) [ 5.595160] scsi 34:0:0:0: SATA: enclosure_logical_id(0x5003005703dbf193), slot(0) [ 5.595304] scsi 34:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y) [ 5.596203] scsi 34:0:0:0: serial_number(Z4YAGGC6 ) [ 5.597172] scsi 34:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1) [ 5.597434] <redpill/sata_boot_shim.c:305> Probing SCSI device using sd_probe_shim [ 5.598171] <redpill/sata_boot_shim.c:307> sd_probe_shim: new SCSI device connected - it's not a SATA disk, ignoring [ 5.599174] <redpill/sata_boot_shim.c:321> Handing over probing from sd_probe_shim to sd_probe [ 5.600385] sd 34:0:0:0: [sas1] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) actually it is a SATA disk : sd_probe_shim: new SCSI device connected - it's not a SATA disk, ignoring dmesg_mpt2sas.txt messages_mpt2sas.txt Edited August 23, 2021 by Orphée Link to comment Share on other sites More sharing options...
Dreadnought Posted August 23, 2021 Share #673 Posted August 23, 2021 5 hours ago, Orphée said: I tried and it works, but same a "Burp". It is a workaround as you then have the warning message I get the notification that Disk 2 is reidentified every minute. I hope that one day this issue is also beeing fixed. Link to comment Share on other sites More sharing options...
psychoboi32 Posted August 23, 2021 Share #674 Posted August 23, 2021 regarding mpt2sas and LSI passthrough It is in /usr/lib/modules/ Do I just have to add some modprobe at boot ?can you share with me mpt2sas.ko i will try to put in bootloader hope it load automatically when fresh boot i have spare drive don’t worry [emoji6]Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Orphée Posted August 23, 2021 Share #675 Posted August 23, 2021 15 minutes ago, psychoboi32 said: can you share with me mpt2sas.ko i will try to put in bootloader hope it load automatically when fresh boot i have spare drive don’t worry Sent from my iPhone using Tapatalk it is already inside ds3615xs redpill image. # ll /usr/lib/modules/mpt2sas.ko -rw-r--r-- 1 root root 432932 Nov 13 2020 /usr/lib/modules/mpt2sas.ko You may try yourself to : /usr/lib/modules-load.d/ a new file named : 70-disk-0000-mpt2sas.conf with content : mpt2sas # ll /usr/lib/modules-load.d/70-disk-0000-mpt2sas.conf -rw-r--r-- 1 root root 8 Aug 23 15:38 /usr/lib/modules-load.d/70-disk-0000-mpt2sas.conf # cat /usr/lib/modules-load.d/70-disk-0000-mpt2sas.conf mpt2sas Link to comment Share on other sites More sharing options...
Recommended Posts