Hi! I just got a new NVMe enclosure and since I was upgrading its firmware I decided to upgrade this one too.
I chose the one that has support for suspending the drive, as it is the default behaviour mine had and I’d like it to continue that way because the drive is connected continuously.
To test some things though, I plugged in a 2.5’’ Samsung EVO. It works as expected as well, even though the device is intended for bigger 3.5’’ drives. However I noticed something odd, hence the request for a newer firmware (if at all possible, I know these things aren’t cut and dried).
The thing is, when an SSD is connected to it, Windows doesn’t recognize it as an SSD. TRIM or unmap does seem to work, but Windows still thinks it’s a mechanical hard drive so it won’t issue those commands on a regular basis.
I have another adapter, not enclosure, from a different vendor, that also employs the ASM1153e bridge/chipset. As opposed to the USB3-SATA-UASP1, SSDs are correctly detected over there.
The way it can be seen is for example in the “Defragment and Optimize Drives” program that comes with Windows (I’m running 2004, in case you want to replicate it over there). This is how it reads when using the USB3-SATA-UASP1:
It even allows it to be “analyzed” for fragmentation.
If necessary I can state the name and model of the other adapter (maybe via PM?) I hesitate because I don’t like drawing comparisons between companies and I’m fond of Plugable.
In any case, thank you for your time and for considering the petition, whether it ends up materializing or not.