I purchased this one:

https://www.aliexpress.com/item/1005005225588036.html?spm=a2g0o.order_list.order_list_main.41.44d01802h5K7Su

Since I saw that ADMedia chip is being recommended, and it's not PCIe x1 like some other models.

I connected to it 2 identical WD 14TB 3.5" drives. (and the adapter itself is sitting in a x16 slot in the motherboard).

When I boot the PC there's a quick popup before the BIOS logo that shows that both drives were detected.

However, in Unraid I only get one of them detected. I'm turning one of them into parity, that will take like 24 hours to complete and I started running it, I'll start playing around with the system when it'll finish. Anything I need to do in Unraid to enable this adapter? It should be an ok adapter, right?

 

 

Edited June 18, 20242 yr by DrMor

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

Attached, thanks!

And now that I'm looking into the logs more carefully, I see in the syslog the line:

"ata10.00: disable device"

After it's getting some errors in the syslog. 

I see "failed to enable AA (error_mask=0x4)".

 

tower-diagnostics-20240618-1917.zip

Edited June 18, 20242 yr by DrMor

One of the disks is failing to identify:

 

Jun 18 18:31:10 Tower kernel: ata10.00: supports DRM functions and may not be fully accessible
Jun 18 18:31:10 Tower kernel: ata10.00: ATA-9: WDC WD140EDGZ-11B1PA0, 85.00A85, max UDMA/133
Jun 18 18:31:10 Tower kernel: ata10.00: qc timeout after 5000 msecs (cmd 0xef)
Jun 18 18:31:10 Tower kernel: ata10.00: failed to enable AA (error_mask=0x4)
Jun 18 18:31:10 Tower kernel: ata10.00: 27344764928 sectors, multi 0: LBA48 ÿ�
Jun 18 18:31:10 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jun 18 18:31:10 Tower kernel: ata10.00: supports DRM functions and may not be fully accessible
Jun 18 18:31:10 Tower kernel: ata10.00: ATA-9: WDC WD140EDGZ-11B1PA0, 85.00A85, max UDMA/133
Jun 18 18:31:10 Tower kernel: ata10.00: qc timeout after 15000 msecs (cmd 0x2f)
Jun 18 18:31:10 Tower kernel: ata10.00: Read log 0x00 page 0x00 failed, Emask 0x4
Jun 18 18:31:10 Tower kernel: ata10.00: NCQ Send/Recv Log not supported
Jun 18 18:31:10 Tower kernel: ata10.00: Read log 0x00 page 0x00 failed, Emask 0x40
Jun 18 18:31:10 Tower kernel: ata10.00: 27344764928 sectors, multi 0: LBA48 NCQ (depth 32)
Jun 18 18:31:10 Tower kernel: ata10.00: Security Log not supported
Jun 18 18:31:10 Tower kernel: ata10.00: Features: NCQ-sndrcv
Jun 18 18:31:10 Tower kernel: ata10.00: failed to set xfermode (err_mask=0x40)
Jun 18 18:31:10 Tower kernel: ata10: limiting SATA link speed to 3.0 Gbps
Jun 18 18:31:10 Tower kernel: ata10.00: limiting speed to UDMA/133:PIO3
Jun 18 18:31:10 Tower kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 320)
Jun 18 18:31:10 Tower kernel: ata10.00: supports DRM functions and may not be fully accessible
Jun 18 18:31:10 Tower kernel: ata10.00: qc timeout after 15000 msecs (cmd 0x2f)
Jun 18 18:31:10 Tower kernel: ata10.00: Read log 0x13 page 0x00 failed, Emask 0x4
Jun 18 18:31:10 Tower kernel: ata10.00: Read log 0x00 page 0x00 failed, Emask 0x40
Jun 18 18:31:10 Tower kernel: ata10.00: NCQ Send/Recv Log not supported
Jun 18 18:31:10 Tower kernel: ata10.00: Security Log not supported
Jun 18 18:31:10 Tower kernel: ata10.00: failed to set xfermode (err_mask=0x40)
Jun 18 18:31:10 Tower kernel: ata10.00: disable device

 

Swap cables between both and see where the problem follows.

That was silly, sorry to trouble you. I was super skeptical but did it anyway, swapped between the cables and now both drives are recognized. So maybe one of them just wasn't plugged properly or something. Everything is working now, thanks!