Windows 10: Make Windows 10 realize USB 3.0 connected drive is an SSD, not an HDD.

I have an SSD inside an Inateck FE2006 case, and Windows recognizes it fine. *But* when I look under drive optimization, it says it's an HDD and not an SSD (and will thereby try to defragment it instead of sending TRIM commands). Now, when I run CrystalDiskInfo, it realizes that it is an SSD, which one, that it supports TRIM, etc. - just like if it was connected via SATA 3. So the USB 3.0 to SATA 3 controller doesn't seem to generally block these things.

Now I'm wondering, is there a way to make Windows 10 [Version 10.0.14393] realize that it's talking to an SSD and not to a hard drive/make it send TRIM commands to it?

:)

 

will windows 10 recognize a usb 5.25 inch drive

Hi,

I realize that you want to know if USB 5.25 inch drive is recognized on the PC. I will try to help you with this issue.

I would like to let you know that as the size of the HDD does not matter as long as it has the USB cable connected to the PC. When the USB cable either 2.0 or 3.0 is plugged in then Windows 10 PC will for sure recognize the
external HDD.

Keep us informed to help you further.

Thank you.

 

WINDOWS 10-SSd boot disc and SSd backup discs are showing up as removable discs.

Method 1 and 2 did not fix the problem. In addition, win 10 misidentifies my type of drives so that in Optimize it classifies 1 of the 3 SSD drives as HDD and defrags it. It properly classifies the other 2 as SSD and trims. This misclassified drive
was initialized using a usb 3.0 ssd connector before installing in the PC.

 

Something you could try:

Plug in your ext. SSD, open a command prompt and try the following where # is the drive number you see in disk management.
Then reboot your system, and see if Windows sees the disk as an SSD, because it now knows how fast it is.

Code: winsat disk -n #[/quote] Example:

I want to check my Disk 2




winsat disk -n 2

 

Well, I tried it (including restart), but that didn't do anything unfortunately.

Code: winsat disk -n 4 Windows System Assessment Tool > Running: Feature Enumeration '' > Run Time 00:00:00.00 > Running: Storage Assessment '-n 4 -ran -read' > Run Time 00:00:00.16 > Running: Storage Assessment '-n 4 -seq -read' > Run Time 00:00:01.92 > Running: Storage Assessment '-n 4 -seq -write' > Run Time 00:00:02.14 > Running: Storage Assessment '-n 4 -flush -seq' > Run Time 00:00:00.56 > Running: Storage Assessment '-n 4 -flush -ran' > Run Time 00:00:00.55 > Disk Random 16.0 Read 199.25 MB/s 7.7 > Disk Sequential 64.0 Read 325.79 MB/s 7.8 > Disk Sequential 64.0 Write 320.35 MB/s 7.8 > Average Read Time with Sequential Writes 0.233 ms 8.5 > Latency: 95th Percentile 0.470 ms 8.7 > Latency: Maximum 1.058 ms 8.9 > Average Read Time with Random Writes 0.233 ms 8.8 > Total Run Time 00:00:05.38[/quote]

 

Sorry that's all I could think of.
Maybe someone else has an idea.
WINSAT is so the system learns what the capabilities of your system hardware are, and then usually makes settings in the OS, according to the scores. I always run it after driver upgrades, or when I install new parts.

 

Hi,

If that case uses UAS protocol then that would explain why it doesn't support TRIM and hence treat your drive as if it were a HDD.

While you CAN defrag a SSD like you would a HDD, you really shouldn't as it just doesn't need it because latency is so low you'd hardly notice a difference.

To find out if the case supports UAS open device manager and check for an UAS entry under Storage controllers.

Cheers, *Wink

 

Uhh... you're confusing me a bit. I'm pretty sure UASP supports both UNMAP and direct ATA command passthrough, which could both be used to support TRIM? I mean, as far as I know UASP was pretty much made to do this. Did you mean to ask if it is not using UASP?

 

Hi,

No, I would like to know if it supports UASP for that would explain what you are experiencing.

Checked it and yes it does use UAS which does not support TRIM so Windows looks at it as if it were a HDD as far as optimization is concerned.
Other then that it should be faster than a USB 3.0 connection though.

Cheers, *Wink

 

What makes you think UASP doesn't support TRIM? UASP supports TRIM fine via two different methods, like I wrote above... and as I wrote in my entry post, CrystalDiskInfo is able to detect that just fine.

 

Hi,

It does not support it natively, hence the use of the UNMAP hardware command which not all UASP hardware supports.
Windows however will treat your drive as if it were a HDD when you want to optimize it.

Short answer: No.
The main reason being that SCSI devices are unaware of trim command so these need to be translated.

Cheers, *Wink

 

You can TRIM it manually using the /L switch while using the defrag command Code: defrag X: /L /U /V[/quote] Where X: is the partition letter
/L Perform retrim on the specified volumes. Only for a SSD. /U Print the progress of the operation on the screen. /V Print verbose output containing the fragmentation statistics.

 

Damn it actually worked, thanks! It seems to re-trim every unused sector every time you run it, but that's fine honestly, only takes a few seconds.

Code: defrag D: /L /U /V Microsoft Drive Optimizer Copyright (c) 2013 Microsoft Corp. Invoking retrim on data (D... Performing pass 1: Retrim: 100% complete. The operation completed successfully. Post Defragmentation Report: Volume Information: Volume size = 698.50 GB Cluster size = 4 KB Used space = 179.57 MB Free space = 698.33 GB Retrim: Backed allocations = 698 Allocations trimmed = 696 Total space trimmed = 695.85 GB[/quote] Without defrag:
Code: trimcheck.exe \\.\D: D:\ D:\trim.dat Sectors per cluster: 8 Bytes per sector: 512 Number of free clusters: 183063403 Total number of clusters: 183110399 Testing TRIM with file 'D:\trim.dat' ExtentCount: 1 StartingVcn: 0 NextVcn: 1 Lcn: 41 Volume file type: 1 (0) Old file pointer: 167936 New file pointer: 167936 61 62 63 64 65 66 67 68 Press any key to continue . . . 61 62 63 64 65 66 67 68[/quote] With defrag:
Code: trimcheck.exe \\.\D: D:\ D:\trim.dat Sectors per cluster: 8 Bytes per sector: 512 Number of free clusters: 183063403 Total number of clusters: 183110399 Testing TRIM with file 'D:\trim.dat' ExtentCount: 1 StartingVcn: 0 NextVcn: 1 Lcn: 41 Volume file type: 1 (0) Old file pointer: 167936 New file pointer: 167936 61 62 63 64 65 66 67 68 Press any key to continue . . . 00 00 00 00 00 00 00 00[/quote] So it actually works. (This program just writes a new file with this pattern into exactly one cluster, opens the volume directly, seeks to the file location, reads the cluster directly from the volume, waits for you to TRIM, and then reads the cluster again.)

Thanks a lot man! The only question that remains is why Windows doesn't realize this by default, but oh well maybe it'll get fixed eventually.

 

You're welcome, you could save it as a .bat file(make sure to select "Run as admin" in advanced) and make a shortcut for it to your desktop or pin it to Start.