I'm building a new machine with this being the base machine (with some changes including the above HBA):

https://www.ebay.com/itm/SuperMicro-4U-CSE-846-24-Bay-SAS2-BP-X9DRi-F-2x-W-2x-E5-2630Lv2-16GB-IT-MODE/153667736717?hash=item23c74f948d:g:iu4AAOSwWZFdQIVA

 

I see that some SSD's don't work with TRIM and the above HBA.

https://ichabod-origin.aws.broadcom.com/support/knowledgebase/1211161496937/trim-and-sgunmap-support-for-lsi-hbas-and-raid-controllers

 

Is there a current list somewhere of SSD's that will work with the HBA that I'm getting?

 

I have a spare 512GB Samsung 860 Pro that I'd like to use but I don't think it will work?

Trim on LSI SAS2008/2308 hasn't been working for a while, it appears to be a kernel/driver issue, it works on the newer LSI SAS3008 based controllers, or use onboard SATA if possible.

Bummer but thanks for the info!

 

I have a couple of Seagate 2.5" 1TB Constellation.2 drives that I could use for the Cache drives as well.

 

If I can't get the SSD's working via the on-board SATA I'll just use them even though they'll probably be slow.

Thanks to @johnnie.black for this info:

Up to Unraid 6.3.5, mpt3sas driver 13.100.00.00, TRIM works on LSI SAS2 and SAS3 HBAs, starting with Unraid 6.4.1, mpt3sas driver 15.100.00.00, TRIM stopped working on SAS2 HBAs, like the 9211-8i, 9207-8i, etc, but still works on SAS3 HBAs like the 9300-8i.     

 

But note that for all cases, TRIM with LSI HBAs only works on SSDs with deterministic read zeros after TRIM, for SSDs with no deterministic read after TRIM you get the standard TRIM unsupported error when running fstrim: 

the discard operation is not supported

When running fstrim with a SAS2 LSI HBA on an SSD with deterministic read trim support and latest drivers you get a different more cryptic error:

FITRIM ioctl failed: Remote I/O error

 

All Samsung consumer SSD models prior to the 860 EVO don't support deterministic reads after TRIM, so if for example you have an 850 EVO it will never be trimmed by an LSI HBA.

 

I believe the PRO models are different, and most support it, you can easily check with hdparm:

 

OK for LSI HBA:

hdparm -I /dev/sdc | grep TRIM * Data Set Management TRIM supported (limit 8 blocks) * Deterministic read ZEROs after TRIM

Not OK for LSI HBA:

hdparm -I /dev/sdb | grep TRIM * Data Set Management TRIM supported (limit 8 blocks)

 

 

It's been reported on other thread that it works with an older firmware, p16.00.00.00 IIRC, but still only with SSDs that support DRZAT.

On 10/9/2019 at 8:48 PM, johnnie.black said:

It's been reported on other thread that it works with an older firmware, p16.00.00.00 IIRC, but still only with SSDs that support DRZAT.

Does older HBAs firmware ( p16)  in addition to SSD DRZAT support only makes Trim work in JBOD mode or can it also work with other RAID  modes such as RAID10 ?

2 hours ago, yann said:

can it also work with other RAID  modes such as RAID10 ?

No, LSI only supports trim on HBAs using IT mode.

6 hours ago, johnnie.black said:

No, LSI only supports trim on HBAs using IT mode.

Hi, thank you for your reply. I am aware about IT mode being requested  to get Trim functionnality but I was asking more specifically about Trim availability in conjunction to Raid 10  (when IT mode, P16 bios and deterministic reads after TRIM SSDs are used).

Edited February 26, 20206 yr by yann
grammar mistake

about Trim availability in conjunction to Raid 10

Since IT mode doesn't support any kind of RAID I though I was being clear, but yes, trim won't work in any RAID mode with an LSI controller.

 

On 10/9/2019 at 9:28 AM, jpowell8672 said:

All Samsung consumer SSD models prior to the 860 EVO don't support deterministic reads after TRIM, so if for example you have an 850 EVO it will never be trimmed by an LSI HBA.

I was wondering why I only had trim on my 860 EVO but not on my 850 EVO. Although this is not good news to me it's still better than being left wondering why. I'm glad I found this post randomly while searching for answers, I appreciate the info.

 

Cheers! 

Haven't read much feedback about people actually using P16 for SSD trim, so here's mine.

 

I've had a single server running  3 x LSI controllers on P16 and one on P7 (whoops!) running a mix of ~60 SAS disk, SATA disk/SSD for about 6 months now.  30-disk array and two ZFS pools.  Haven't had any issues running the older firmware as far as I know.

 

kernel: mpt2sas_cm0: LSISAS2008: FWVersion(16.00.00.00), ChipRevision(0x03), BiosVersion(07.11.10.00)
kernel: mpt2sas_cm1: LSISAS2008: FWVersion(07.15.08.00), ChipRevision(0x03), BiosVersion(07.11.10.00)
kernel: mpt2sas_cm2: LSISAS2308: FWVersion(16.00.00.00), ChipRevision(0x05), BiosVersion(07.11.10.00)
kernel: mpt2sas_cm3: LSISAS2308: FWVersion(16.00.00.00), ChipRevision(0x05), BiosVersion(07.11.10.00)
 

I'm about to upgrade/consolidate somewhat, but I'll be sticking with P16 firmware (no usable motherboard SATA ports)