PCIe SATA card (1b21:0612): connected devices not available

[ipic]

I'm having a go at adding more SATA ports to my system.
I got this card . It is a six sata port card.

Although the card and the attached devices are "recognised", they do not show up as usable scsi devices.
If I was to guess, I would say that the card is acting as a multiplexer for several SATA devices, but the kernel doesn't 'understand' that. Possibly because I don't have something configured correctly.

If someone has experience with cards like these I'd appreciate some pointers, thanks.

-------
Details:

Motherboard is: ROG STRIX B550-F GAMING WIFI II
When I plugged the card in, I attached one of my spare SSD drives and a CD/DVR device.
On boot up, I could see both the spare drive and the CDR/DVD player showing up in the bios display. So far so good.

Boot into Gentoo, kernel 6.13.6, and the card shows up as follows:

Code: Select all

lspci -nn
...
06:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller [1b21:0612] (rev 01)
...

lspci -k
...
06:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller (rev 01)
	Subsystem: ASMedia Technology Inc. Device 1060
	Kernel driver in use: ahci
...

lspci -v
...
06:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller (rev 01) (prog-if 01 [AHCI 1.0])
	Subsystem: ASMedia Technology Inc. Device 1060
	Flags: bus master, fast devsel, latency 0, IRQ 46, IOMMU group 15
	I/O ports at d050 [size=8]
	I/O ports at d040 [size=4]
	I/O ports at d030 [size=8]
	I/O ports at d020 [size=4]
	I/O ports at d000 [size=32]
	Memory at fc610000 (32-bit, non-prefetchable) [size=512]
	Expansion ROM at fc600000 [disabled] [size=64K]
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [78] Power Management version 3
	Capabilities: [80] Express Legacy Endpoint, IntMsgNum 0
	Capabilities: [100] Virtual Channel
	Kernel driver in use: ahci
...

In dmesg I can see the two devices being found:

Code: Select all

## The CD/DVR drive 
dmesg | grep ata8.03
[    5.296404] ata8.03: hard resetting link
[    5.759574] ata8.03: SATA link up 1.5 Gbps (SStatus 113 SControl 330)
[    6.090109] ata8.03: ATAPI: DRW-24D5MT, 1.00, max UDMA/133
[    6.091674] ata8.03: configured for UDMA/133
[   10.712496] ata8.03: hard resetting link
[   11.184018] ata8.03: SATA link up 1.5 Gbps (SStatus 113 SControl 330)
[   11.515894] ata8.03: configured for UDMA/133
[   16.088445] ata8.03: hard resetting link
[   16.559954] ata8.03: SATA link up 1.5 Gbps (SStatus 113 SControl 330)
[   16.891977] ata8.03: configured for UDMA/133
[   21.472446] ata8.03: hard resetting link
[   21.943910] ata8.03: SATA link up 1.5 Gbps (SStatus 113 SControl 330)
[   22.276368] ata8.03: configured for UDMA/133
[   26.848444] ata8.03: hard resetting link
[   27.319960] ata8.03: SATA link up 1.5 Gbps (SStatus 113 SControl 330)
[   27.652886] ata8.03: configured for UDMA/133
[   30.657389] ata8.03: Check power mode failed (err_mask=0x40)

## The SSD drive:
dmesg | grep ata8.02
[    4.830897] ata8.02: hard resetting link
[    5.295565] ata8.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[    6.075065] ata8.02: Model 'Samsung SSD 870 EVO 2TB', rev 'SVT03B6Q', applying quirks: noncqtrim zeroaftertrim noncqonati
[    6.076380] ata8.02: supports DRM functions and may not be fully accessible
[    6.076676] ata8.02: ATA-11: Samsung SSD 870 EVO 2TB, SVT03B6Q, max UDMA/133
[    6.077767] ata8.02: 3907029168 sectors, multi 1: LBA48 NCQ (depth 32), AA
[    6.082353] ata8.02: Features: Trust Dev-Sleep NCQ-sndrcv
[    6.083628] ata8.02: supports DRM functions and may not be fully accessible
[    6.088628] ata8.02: configured for UDMA/133
[   10.241011] ata8.02: hard resetting link
[   10.711964] ata8.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[   11.500869] ata8.02: supports DRM functions and may not be fully accessible
[   11.507113] ata8.02: supports DRM functions and may not be fully accessible
[   11.512532] ata8.02: configured for UDMA/133
[   15.616952] ata8.02: hard resetting link
[   16.087903] ata8.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[   16.877893] ata8.02: supports DRM functions and may not be fully accessible
[   16.883297] ata8.02: supports DRM functions and may not be fully accessible
[   16.888706] ata8.02: configured for UDMA/133
[   21.001458] ata8.02: hard resetting link
[   21.471945] ata8.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[   22.261038] ata8.02: supports DRM functions and may not be fully accessible
[   22.267254] ata8.02: supports DRM functions and may not be fully accessible
[   22.272632] ata8.02: configured for UDMA/133
[   26.376726] ata8.02: hard resetting link
[   26.847967] ata8.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[   27.637572] ata8.02: supports DRM functions and may not be fully accessible
[   27.643509] ata8.02: supports DRM functions and may not be fully accessible
[   27.649378] ata8.02: configured for UDMA/133
[   30.657139] ata8.02: Check power mode failed (err_mask=0x40)

But, no scsi devices are created for the attached devices.

Code: Select all

lsscsi 
[0:0:0:0]    disk    ATA      FIKWOT FS810 4TB 30A8  /dev/sda 
[1:0:0:0]    disk    ATA      CT4000MX500SSD1  046   /dev/sdb 
[2:0:0:0]    disk    ATA      CT2000MX500SSD1  046   /dev/sdc 
[3:0:0:0]    disk    ATA      CT2000MX500SSD1  046   /dev/sdd 
[8:0:0:0]    disk    Generic- SD/MMC           1.00  /dev/sde 
[8:0:0:1]    disk    Generic- Compact Flash    1.01  /dev/sdf 
[8:0:0:2]    disk    Generic- SM/xD-Picture    1.02  /dev/sdg 
[8:0:0:3]    disk    Generic- MS/MS-Pro        1.03  /dev/sdh 
[N:0:8224:1] disk    WD_BLACK SN850X 4000GB__1                  /dev/nvme0n1

Full dmesg output for ata8 is as follows::

Code: Select all

dmesg | grep ata8
[    1.140417] ata8: SATA max UDMA/133 abar m512@0xfc610000 port 0xfc610180 irq 46 lpm-pol 0
[    4.207408] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    4.208557] ata8.15: Port Multiplier 1.2, 0x197b:0x5755 r0, 5 ports, feat 0x5/0xf
[    4.209785] ata8.00: hard resetting link
[    4.517627] ata8.00: SATA link down (SStatus 0 SControl 330)
[    4.518973] ata8.01: hard resetting link
[    4.829620] ata8.01: SATA link down (SStatus 0 SControl 330)
[    4.830897] ata8.02: hard resetting link
[    5.295565] ata8.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[    5.296404] ata8.03: hard resetting link
[    5.759574] ata8.03: SATA link up 1.5 Gbps (SStatus 113 SControl 330)
[    5.760869] ata8.04: hard resetting link
[    6.069577] ata8.04: SATA link down (SStatus 0 SControl 330)
[    6.075065] ata8.02: Model 'Samsung SSD 870 EVO 2TB', rev 'SVT03B6Q', applying quirks: noncqtrim zeroaftertrim noncqonati
[    6.076380] ata8.02: supports DRM functions and may not be fully accessible
[    6.076676] ata8.02: ATA-11: Samsung SSD 870 EVO 2TB, SVT03B6Q, max UDMA/133
[    6.077767] ata8.02: 3907029168 sectors, multi 1: LBA48 NCQ (depth 32), AA
[    6.082353] ata8.02: Features: Trust Dev-Sleep NCQ-sndrcv
[    6.083628] ata8.02: supports DRM functions and may not be fully accessible
[    6.088628] ata8.02: configured for UDMA/133
[    6.090109] ata8.03: ATAPI: DRW-24D5MT, 1.00, max UDMA/133
[    6.091674] ata8.03: configured for UDMA/133
[    9.151396] ata8.15: qc timeout after 3000 msecs (cmd 0xe8)
[    9.151816] ata8.15: failed to write PMP_FEAT_EN (Emask=0x5)
[    9.152167] ata8.15: hard resetting link
[    9.615408] ata8.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    9.616889] ata8.00: hard resetting link
[    9.928211] ata8.00: SATA link down (SStatus 0 SControl 330)
[    9.929703] ata8.01: hard resetting link
[   10.239704] ata8.01: SATA link down (SStatus 0 SControl 330)
[   10.241011] ata8.02: hard resetting link
[   10.711964] ata8.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[   10.712496] ata8.03: hard resetting link
[   11.184018] ata8.03: SATA link up 1.5 Gbps (SStatus 113 SControl 330)
[   11.184680] ata8.04: hard resetting link
[   11.496049] ata8.04: SATA link down (SStatus 0 SControl 330)
[   11.500869] ata8.02: supports DRM functions and may not be fully accessible
[   11.507113] ata8.02: supports DRM functions and may not be fully accessible
[   11.512532] ata8.02: configured for UDMA/133
[   11.515894] ata8.03: configured for UDMA/133
[   14.527729] ata8.15: qc timeout after 3000 msecs (cmd 0xe8)
[   14.528361] ata8.15: failed to write PMP_FEAT_EN (Emask=0x5)
[   14.528756] ata8.15: hard resetting link
[   14.991726] ata8.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   14.992634] ata8.00: hard resetting link
[   15.303152] ata8.00: SATA link down (SStatus 0 SControl 330)
[   15.303712] ata8.01: hard resetting link
[   15.616284] ata8.01: SATA link down (SStatus 0 SControl 330)
[   15.616952] ata8.02: hard resetting link
[   16.087903] ata8.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[   16.088445] ata8.03: hard resetting link
[   16.559954] ata8.03: SATA link up 1.5 Gbps (SStatus 113 SControl 330)
[   16.560480] ata8.04: hard resetting link
[   16.872223] ata8.04: SATA link down (SStatus 0 SControl 330)
[   16.877893] ata8.02: supports DRM functions and may not be fully accessible
[   16.883297] ata8.02: supports DRM functions and may not be fully accessible
[   16.888706] ata8.02: configured for UDMA/133
[   16.891977] ata8.03: configured for UDMA/133
[   19.903721] ata8.15: qc timeout after 3000 msecs (cmd 0xe8)
[   19.904259] ata8.15: failed to write PMP_FEAT_EN (Emask=0x5)
[   19.904647] ata8.15: hard resetting link
[   20.375733] ata8.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   20.376638] ata8.00: hard resetting link
[   20.687855] ata8.00: SATA link down (SStatus 0 SControl 330)
[   20.688445] ata8.01: hard resetting link
[   21.000467] ata8.01: SATA link down (SStatus 0 SControl 330)
[   21.001458] ata8.02: hard resetting link
[   21.471945] ata8.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[   21.472446] ata8.03: hard resetting link
[   21.943910] ata8.03: SATA link up 1.5 Gbps (SStatus 113 SControl 330)
[   21.944419] ata8.04: hard resetting link
[   22.256275] ata8.04: SATA link down (SStatus 0 SControl 330)
[   22.261038] ata8.02: supports DRM functions and may not be fully accessible
[   22.267254] ata8.02: supports DRM functions and may not be fully accessible
[   22.272632] ata8.02: configured for UDMA/133
[   22.276368] ata8.03: configured for UDMA/133
[   25.279722] ata8.15: qc timeout after 3000 msecs (cmd 0xe8)
[   25.280244] ata8.15: failed to write PMP_FEAT_EN (Emask=0x5)
[   25.280670] ata8.15: hard resetting link
[   25.751742] ata8.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   25.752765] ata8.00: hard resetting link
[   26.063699] ata8.00: SATA link down (SStatus 0 SControl 330)
[   26.064472] ata8.01: hard resetting link
[   26.376068] ata8.01: SATA link down (SStatus 0 SControl 330)
[   26.376726] ata8.02: hard resetting link
[   26.847967] ata8.02: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[   26.848444] ata8.03: hard resetting link
[   27.319960] ata8.03: SATA link up 1.5 Gbps (SStatus 113 SControl 330)
[   27.320468] ata8.04: hard resetting link
[   27.632546] ata8.04: SATA link down (SStatus 0 SControl 330)
[   27.637572] ata8.02: supports DRM functions and may not be fully accessible
[   27.643509] ata8.02: supports DRM functions and may not be fully accessible
[   27.649378] ata8.02: configured for UDMA/133
[   27.652886] ata8.03: configured for UDMA/133
[   30.655752] ata8.15: qc timeout after 3000 msecs (cmd 0xe8)
[   30.656306] ata8.15: failed to write PMP_FEAT_EN (Emask=0x5)
[   30.656641] ata8: failed to recover PMP after 5 tries, giving up
[   30.656890] ata8.15: Port Multiplier detaching
[   30.657139] ata8.02: Check power mode failed (err_mask=0x40)
[   30.657389] ata8.03: Check power mode failed (err_mask=0x40)
[   30.657633] ata8.00: disable device
[   31.119759] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   31.120198] ata8: EH complete

[pietinger]

Do you use our Gentoo distribution kernel, or a self-configured kernel?

1) If it is our Gentoo dist-kernel and it does not work, then throw away this card.

2) If the latter is the case, please check whether you have activated these options:

Code: Select all

CONFIG_CHR_DEV_SG
CONFIG_SATA_AHCI_PLATFORM

If these are enabled, please boot with our GentooLiveCD and check if it works. If not -> (1)

3) If it works do a "lsmod" and check every module with sata and scsi in the name.

(Possible list: CONFIG_SCSI_SPI_ATTRS, CONFIG_SATA_PMP, CONFIG_SCSI_MVUMI, CONFIG_SATA_ACARD_AHCI)

[ipic]

Thanks for the pointers, appreciated.

I downloaded and booted the Gentoo liveCD, and got the same result.
Rather than throw the card in the trash, I disconnected the CD/DVR device, and then this happened:

Code: Select all

[    4.183401] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    4.184571] ata8.15: Port Multiplier 1.2, 0x197b:0x5755 r0, 5 ports, feat 0x5/0xf
[    4.185758] ata8.00: hard resetting link
[    4.493806] ata8.00: SATA link down (SStatus 0 SControl 330)
[    4.495132] ata8.01: hard resetting link
[    4.807538] ata8.01: SATA link down (SStatus 0 SControl 330)
[    4.808880] ata8.02: hard resetting link
[    5.119910] ata8.02: SATA link down (SStatus 0 SControl 330)
[    5.121228] ata8.03: hard resetting link
[    5.591808] ata8.03: SATA link up 6.0 Gbps (SStatus 133 SControl 330)
[    5.593107] ata8.04: hard resetting link
[    5.901560] ata8.04: SATA link down (SStatus 0 SControl 330)
[    5.906513] ata8.03: Model 'Samsung SSD 870 EVO 2TB', rev 'SVT03B6Q', applying quirks: noncqtrim zeroaftertrim noncqonati
[    5.907423] ata8.03: supports DRM functions and may not be fully accessible
[    5.907909] ata8.03: ATA-11: Samsung SSD 870 EVO 2TB, SVT03B6Q, max UDMA/133
[    5.908672] ata8.03: 3907029168 sectors, multi 1: LBA48 NCQ (depth 32), AA
[    5.913255] ata8.03: Features: Trust Dev-Sleep NCQ-sndrcv
[    5.913972] ata8.03: supports DRM functions and may not be fully accessible
[    5.919591] ata8.03: configured for UDMA/133
[    5.921074] ata8: EH complete
[    5.921924] scsi 7:3:0:0: Direct-Access     ATA      Samsung SSD 870  3B6Q PQ: 0 ANSI: 5
[    5.922726] sd 7:3:0:0: Attached scsi generic sg4 type 0
[    5.922727] ata8.03: Enabling discard_zeroes_data
[    5.922737] sd 7:3:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[    5.924530] sd 7:3:0:0: [sde] Write Protect is off
[    5.925060] sd 7:3:0:0: [sde] Mode Sense: 00 3a 00 00
[    5.925071] sd 7:3:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    5.925534] sd 7:3:0:0: [sde] Preferred minimum I/O size 512 bytes
[    5.926288] ata8.03: Enabling discard_zeroes_data
[    5.945263]  sde: sde1 sde2 sde3 sde4 sde5 sde6
[    5.946623] sd 7:3:0:0: [sde] Attached SCSI disk

So, no exchangeble drive and only one SDD attached == working SDD device.

I'll experiment a bit more.

[ipic]

I think it's certain that the CD/DVR was causing issues with this card.
To be fair to it, it doesn't claim to support CD type devices, just HDD and SDD.

I have attached my hot swap drive bay to the card.
When inserting a drive, a /dev/sdX device is created in the same was as when the bay is connected to the motherboard.
When removing the drive the /dev/sdX device is removed, and the 'fixed' SDD is not changed or lost.

Moral of the story seems to be: take the sales description VERY literally

[john970]

I have the same card and am having the same issue, and it also works with only one drive attached (I am only attaching SATA spinning media). It seems to have started with 6.13, I am actually using Fedora's build 6.13.6-200.

I have the pci card and an m.2 sata adapter that also has the ASM1166 controller and no apparent issues with the M.2 adapter.

6.13 dropped some deprecated pci functions, not sure if that is related. Maybe the card has older firmware? Not sure why one drive works, two don't, and the other controller works fine.

[ipic]

I have the same card and am having the same issue, and it also works with only one drive attached (I am only attaching SATA spinning media). It seems to have started with 6.13, I am actually using Fedora's build 6.13.6-200.

I have the pci card and an m.2 sata adapter that also has the ASM1166 controller and no apparent issues with the M.2 adapter.

6.13 dropped some deprecated pci functions, not sure if that is related. Maybe the card has older firmware? Not sure why one drive works, two don't, and the other controller works fine.

When you have more than one drive attached, is the problem you see that they are not recognised as scsi devices, or that they are recognised but fail when used?

My experience with this card so far is that it recognises both a SSD and a HDD when attached.
I added the SDD to my RAID-1 array, and that worked.
I did a backup to two separate hot plugged HDD drives, and both backups worked - driving the HDD at around 98% (according to atop).
('backup' here means a dd command, source logical volume, target image file on the HDD drive)

The only thing I have found that definitely does not work is attaching a SATA CD/DVR drive - that causes the whole device to fail with no attached drives recognised.

[john970]

When you have more than one drive attached, is the problem you see that they are not recognised as scsi devices, or that they are recognised but fail when used?

My experience with this card so far is that it recognises both a SSD and a HDD when attached.
I added the SDD to my RAID-1 array, and that worked.
I did a backup to two separate hot plugged HDD drives, and both backups worked - driving the HDD at around 98% (according to atop).
('backup' here means a dd command, source logical volume, target image file on the HDD drive)

The only thing I have found that definitely does not work is attaching a SATA CD/DVR drive - that causes the whole device to fail with no attached drives recognised.

I see several different errors in the kernel log, I see no kernel messages on boot but then this happens when I try to import a ZFS pool (which fails):

Code: Select all

[  +0.000010] [Sat Mar 15 02:24:59 2025] sd 4:0:0:0: [sde] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  +0.000005] [Sat Mar 15 02:24:59 2025] sd 4:0:0:0: [sde] tag#7 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[Mar15 02:25] [Sat Mar 15 02:25:04 2025] sd 6:0:0:0: [sdg] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  +0.000008] [Sat Mar 15 02:25:04 2025] sd 6:0:0:0: [sdg] tag#21 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00
[  +0.000112] [Sat Mar 15 02:25:04 2025] sd 7:0:0:0: [sdh] tag#22 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK cmd_age=0s
[  +0.000007] [Sat Mar 15 02:25:04 2025] sd 7:0:0:0: [sdh] tag#22 CDB: ATA command pass through(16) 85 06 2c 00 00 00 00 00 00 00 00 00 00 00 e5 00

And

Code: Select all

res 41/84:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
[  +0.000004] [Fri Mar 14 21:42:19 2025] ata1.00: status: { DRDY ERR }
[  +0.000001] [Fri Mar 14 21:42:19 2025] ata1.00: error: { ICRC ABRT }
[  +0.000003] [Fri Mar 14 21:42:19 2025] ata1: hard resetting link
[  +0.307131] [Fri Mar 14 21:42:19 2025] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 310)
[  +0.004250] [Fri Mar 14 21:42:19 2025] ata1.00: configured for UDMA/33
[  +0.010135] [Fri Mar 14 21:42:19 2025] ata1: EH complete
[  +0.027470] [Fri Mar 14 21:42:19 2025] ata1.00: exception Emask 0x11 SAct 0x400000 SErr 0x0 action 0x6 frozen
[  +0.000008] [Fri Mar 14 21:42:19 2025] ata1.00: irq_stat 0x48000008, interface fatal error
[  +0.000002] [Fri Mar 14 21:42:19 2025] ata1.00: failed command: READ FPDMA QUEUED
[  +0.000001] [Fri Mar 14 21:42:19 2025] ata1.00: cmd 60/08:b0:d8:09:00/00:00:00:00:00/40 tag 22 ncq dma 4096 in
                                    res 41/84:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
[  +0.000003] [Fri Mar 14 21:42:19 2025] ata1.00: status: { DRDY ERR }
[  +0.000001] [Fri Mar 14 21:42:19 2025] ata1.00: error: { ICRC ABRT }
[  +0.000003] [Fri Mar 14 21:42:19 2025] ata1: hard resetting link
[  +0.310821] [Fri Mar 14 21:42:19 2025] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 310)
[  +0.003831] [Fri Mar 14 21:42:19 2025] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x40)
[  +0.000005] [Fri Mar 14 21:42:19 2025] ata1.00: revalidation failed (errno=-5)
[  +4.998559] [Fri Mar 14 21:42:24 2025] ata1: hard resetting link
[  +0.309149] [Fri Mar 14 21:42:25 2025] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 310)
[  +0.004247] [Fri Mar 14 21:42:25 2025] ata1.00: configured for UDMA/33
[  +0.035341] [Fri Mar 14 21:42:25 2025] ata1: EH complete

I tried rotating cables, drives, ports, and I ended up ordering an LSI card to replace it, I lost a day troubleshooting this and not worth the $100 the LSI board costs.

[john970]

While waiting for the LSI card to arrive i replaced the ASMedia card with this one. Works fine now.

https://www.amazon.com/dp/B08DFK4LZ7?re ... asin_title

[NeddySeagoon]

john970,

Your log fragments tell two different stories.
One is a tale of woe about three different drives.

The other is the error handler for one drive.
We cannot relate them as we don't know your port to sd mapping.
Its possible that the error handler is for a fourth drive.

[john970]

john970,

Your log fragments tell two different stories.
One is a tale of woe about three different drives.

The other is the error handler for one drive.
We cannot relate them as we don't know your port to sd mapping.
Its possible that the error handler is for a fourth drive.

It wasn’t a drive failure, it was a controller failure. This is what had me chasing my tail for so long. I would unplug some drives, the error would change but not go away. I tried new cables, moving drives, and eventually I changed out the controller and everything began working again so I put everything back the way it was. All the things I searched on for those failures assumes a drive failure, which let me down many rabbit holes.