Opened 5 weeks ago
Last modified 5 weeks ago
#1983 new defect
SSD drives listed in drivedb.h as using Sandforce controller, when they don't...
| Reported by: | joaolopesgomes | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | undecided |
| Component: | drivedb | Version: | |
| Keywords: | ssd | Cc: |
Description (last modified by )
drivedb.h
"SandForce Driven SSDs" in:
"Corsair Force LS SSD"
https://www.techpowerup.com/review/corsair-force-ls-240-gb/2.html
Phison PS3108-S8 controller
"SanDisk SDSSDA(120|240|480)G|"
https://www.tomshardware.com/reviews/dramless-ssd-roundup,4833.html
Silicon Motion SM2246XT
"SanDisk SD8S[BFN]AT128G1(00|12)2"
https://www.tomshardware.com/reviews/sandisk-z400s-dram-less-ssd,4316.html
Silicon Motion's SM2246XT
TIA
Change History (3)
comment:1 by , 5 weeks ago
| Keywords: | ssd added |
|---|---|
| Milestone: | → undecided |
comment:2 by , 5 weeks ago
Sorry that currently i don't have any of those drives available anymore to retrieve such information, i had them in past. The matter is, it's from the public knowledge that none of those drives are based on a Sandforce controller, as proven in my previous drives review links, meaning that specific information "SandForce Driven SSDs" in drivedb.h on those three drives is incorrect, that's the point here. Thank you.
comment:3 by , 5 weeks ago
| Description: | modified (diff) |
|---|

This information is not sufficient because exact model name and firmware revision strings from ATA IDENTIFY command are required.
Please create separate trac tickets or GH issues (preferred) for each affected drive series and provide sample
smartctl -x -aoutputs. See also the FAQ.