I just received a controller based on the ASM1062 chipset (ST LAB A-590). It has two internal mini-SAS connectors SFF-8087 and accomodates 8 drives in total.
It detects all drives when booting into Windows 11, but it cannot be configured in BIOS due to my MB chipset not supporting legacy option rom properly. I connected it to a different system forcing legacy BIOS (non-UEFI) and it is configurable there.
I am only intending to use this controller as an HBA.
In TrueNAS Scale the following logs during boot with 1 drive attached:
It does not detect any disks when finally booted.
lspci shows the controller:
I found a post on the ubuntu bug tracker that describes this exact problem, indicating that this was a bug introduced in Ubuntu at the launch of 22.04, perhaps due to an upgrarded kernel. Could this also apply to TrueNAS Scale? (I know Scale runs debian under the hood)
There was also a github post from a couple of years ago showing this same error where the user stated it was sorted out by disabling IOMMU and any power-saving features. I tried this and it made no difference.
Any ideas other than buying an LSI-card? Did anyone have any success with this after upgrading the firmware on the ASM1062, and if so, which firmware version? (my controller is currently on 0.95)
It detects all drives when booting into Windows 11, but it cannot be configured in BIOS due to my MB chipset not supporting legacy option rom properly. I connected it to a different system forcing legacy BIOS (non-UEFI) and it is configurable there.
I am only intending to use this controller as an HBA.
In TrueNAS Scale the following logs during boot with 1 drive attached:
disks on "ASMedia Technology Inc. ASM1062" controller:
ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata12.00: link online but device misclassified
ata12: link online but 1 devices misclassified, retrying
ata12: reset failed (errno=-11), retrying in 10 secs
ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata12.00: link online but device misclassified
ata12: link online but 1 devices misclassified, retrying
ata12: reset failed (errno=-11), retrying in 10 secs
ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata12.00: link online but device misclassified
ata12: link online but 1 devices misclassified, retrying
ata12: reset failed (errno=-11), retrying in 35 secs
ata12: limiting SATA link speed to 1.5 Gbps
ata12: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata12.00: link online but device misclassified
ata12: link online but 1 devices misclassified, device detection might fail
It does not detect any disks when finally booted.
lspci shows the controller:
05:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
07:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
08:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
I found a post on the ubuntu bug tracker that describes this exact problem, indicating that this was a bug introduced in Ubuntu at the launch of 22.04, perhaps due to an upgrarded kernel. Could this also apply to TrueNAS Scale? (I know Scale runs debian under the hood)
There was also a github post from a couple of years ago showing this same error where the user stated it was sorted out by disabling IOMMU and any power-saving features. I tried this and it made no difference.
Any ideas other than buying an LSI-card? Did anyone have any success with this after upgrading the firmware on the ASM1062, and if so, which firmware version? (my controller is currently on 0.95)