Open shindyczech opened 2 years ago
Hi,
can you send an lspci -nnq from tinycore ?
an lspci -nnk would be nice also
Yes :-) !
The card should work with default DSM ahci module.
TinyCore configuration say:
tc@box:~$ sudo ./rploader.sh satamap now HBA: 00:1f.2 Disks : 6 HBA: 00:1c.1 Disks : 2 SataPortMap=62 DiskIdxMap=0002 Should i update the user_config.json with these values ? [Yy/Nn] y tc@box:~$
user_config.json say:
{ "extra_cmdline": { "pid": "0x0736", "vid": "0x05e3", "sn": "1230LWNxxxxxx", "mac1": "001CC0xxxxxx", "SataPortMap": "62", "DiskIdxMap": "0002" }, "synoinfo": {
"internalportcfg" : "0xffff",
"maxdisks" : "16",
"support_bde_internal_10g" : "no",
"support_disk_compatibility" : "no",
"support_memory_compatibility" : "no"
}, "ramdisk_copy": {
}
}
But:
Just an idea: Can DSM 7.0.1 in DS3615xs work with two controllers at the same time? Isn't it necessary to disable the onboard controller?
I have to add information, all six ports are occupied on the onboard controller, only the first two on the ASMedia controller, which the DSM system does not display.
Can you share an fdisk -l from DSM ?
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: ST1000LM035-1RK172 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: 0x29b0d1ff
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 9437184 1953320351 1943883168 926.9G fd Linux raid autodetect
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: ST1000LM035-1RK172 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: 0xcfb821b5
Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdb2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdb3 9437184 1953320351 1943883168 926.9G fd Linux raid autodetect
Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: ST1000LM035-1RK172 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: 0x4f051388
Device Boot Start End Sectors Size Id Type /dev/sdc1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdc2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdc3 9437184 1953320351 1943883168 926.9G fd Linux raid autodetect
Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: ST1000LM035-1RK172 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: 0x15c85276
Device Boot Start End Sectors Size Id Type /dev/sdd1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdd2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdd3 9437184 1953320351 1943883168 926.9G fd Linux raid autodetect
Disk /dev/sdf: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: ST1000LM035-1RK172 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: 0xca1891ca
Device Boot Start End Sectors Size Id Type /dev/sdf1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sdf2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sdf3 9437184 1953320351 1943883168 926.9G fd Linux raid autodetect
Disk /dev/sde: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: ST1000LM035-1RK172 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: 0x4c31c750
Device Boot Start End Sectors Size Id Type /dev/sde1 2048 4982527 4980480 2.4G fd Linux raid autodetect /dev/sde2 4982528 9176831 4194304 2G fd Linux raid autodetect /dev/sde3 9437184 1953320351 1943883168 926.9G fd Linux raid autodetect
Disk /dev/synoboot: 1.9 GiB, 2002780160 bytes, 3911680 sectors Disk model: STORAGE DEVICE 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 2097151 1843200 900M 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 / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/zram0: 1.2 GiB, 1241513984 bytes, 303104 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, 1241513984 bytes, 303104 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/zram2: 1.2 GiB, 1241513984 bytes, 303104 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/zram3: 1.2 GiB, 1241513984 bytes, 303104 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 / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/md2: 4.5 TiB, 4976335585280 bytes, 9719405440 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 65536 bytes / 327680 bytes
Disk /dev/mapper/cachedev_0: 4.5 TiB, 4976335585280 bytes, 9719405440 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 65536 bytes / 327680 bytes
I found it in the file "modules.alias.4.json" that is written:
{
"name": "ahci",
"alias": "pci:v00001B21d00000622sv*sd*bc*sc*i*"
},
{
"name": "ahci",
"alias": "pci:v00001B21d00000621sv*sd*bc*sc*i*"
},
{
"name": "ahci",
"alias": "pci:v00001B21d00000612sv*sd*bc*sc*i*"
},
{
"name": "ahci",
"alias": "pci:v00001B21d00000611sv*sd*bc*sc*i*"
},
{
"name": "ahci",
"alias": "pci:v00001B21d00000602sv*sd*bc*sc*i*"
},
{
"name": "ahci",
"alias": "pci:v00001B21d00000601sv*sd*bc*sc*i*"
},
My question is, if there should be written also
"alias": "pci:v00001B21d00000624sv*sd*bc*sc*i*"
becouse of lspci -nnq output address of this discussed ASMedia controller.
Probably known for you. Nut I want to be helpful... https://linux-hardware.org/?id=pci:1b21-0624-1b21-1060
For better reading (without prompts): lspci -nnk 00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] 00:01.0 PCI bridge [0604]: Intel Corporation 82G33/G31/P35/P31 Express PCI Express Root Port [8086:29c1] (rev 02) Kernel driver in use: pcieport 00:03.0 Communication controller [0780]: Intel Corporation 82G33/G31/P35/P31 Express MEI Controller [8086:29c4] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] Kernel driver in use: mei_me 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC-2 Gigabit Network Connection [8086:294c] (rev 02) Subsystem: Intel Corporation Device [8086:0001] Kernel driver in use: e1000e 00:1a.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 [8086:2937] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] Kernel driver in use: uhci_hcd 00:1a.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 [8086:2938] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] Kernel driver in use: uhci_hcd 00:1a.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 [8086:2939] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] Kernel driver in use: uhci_hcd 00:1a.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 [8086:293c] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] Kernel driver in use: ehci-pci 00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02) Subsystem: Intel Corporation Device [8086:3001] 00:1c.0 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 [8086:2940] (rev 02) Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 [8086:2942] (rev 02) Kernel driver in use: pcieport 00:1c.2 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 [8086:2944] (rev 02) Kernel driver in use: pcieport 00:1c.3 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 [8086:2946] (rev 02) Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 [8086:2948] (rev 02) Kernel driver in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] Kernel driver in use: uhci_hcd 00:1d.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] Kernel driver in use: uhci_hcd 00:1d.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] Kernel driver in use: uhci_hcd 00:1d.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] Kernel driver in use: ehci-pci 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 92) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801IR (ICH9R) LPC Interface Controller [8086:2916] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] Kernel driver in use: lpc_ich 00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] Kernel driver in use: ahci 00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02) Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) Subsystem: Gigabyte Technology Co., Ltd Device [1458:36d6] 01:00.1 Audio device [0403]: NVIDIA Corporation GF119 HDMI Audio Controller [10de:0e08] (rev a1) Subsystem: Gigabyte Technology Co., Ltd Device [1458:36d6] 03:00.0 IDE interface [0101]: Marvell Technology Group Ltd. 88SE6101/6102 single-port PATA133 interface [11ab:6101] (rev b2) Subsystem: Marvell Technology Group Ltd. 88SE6101/6102 single-port PATA133 interface [11ab:6101] Kernel driver in use: pata_marvell 06:00.0 IDE interface [0101]: ASMedia Technology Inc. Device [1b21:0624] (rev 01) Subsystem: ASMedia Technology Inc. Device [1b21:1060] 07:03.0 FireWire (IEEE 1394) [0c00]: Texas Instruments TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] [104c:8023] Subsystem: Intel Corporation Desktop Board DP35DP [8086:5044] tc@box
This card uses the SATA multiplexer to expand two SATAS into ten. The compatibility of the current system(7.x) with the multiplexer is not very good, right?At least Jun's 1.03/4 boot explicitly states that multiplexers are not supported. hunnn,,7.x support multiplexers?
I think this card deserves to be added to the basic support of ahci interfaces. Can I hope so? If I could do it, I would do it myself. However, I am a professional musician, not a programmer (rather just a user pro) :-) Can I help with the implementation in any way?
https://www.wish.com/cz/product/pci-e-1x-to-10-port-sata30-expansion-card-sata-pcie-1x-adapter-computer-converter-high-speed-pcie-card-610903a5c3ac64f707d6b640?hide_login_modal=true&share=web
I tried 3615xs and 3617xs but without success. It works without errors in the TrueNAS system, but I don't want it.
... I am sorry for my bad English.