Strange SSD S.M.A.R.T behavior
-
Hi everybody,
I got a very strange behavior of a little SSDs SMART values. Its a mSATA SSD. I had it in a mSATA -> SATA Adapter attached to a SATA Port-1. There the SMART value of LBA_written was about 0,x TBW (value is not important).
After a while I set the SSD in a dedicated mSATA Port-0 on the SAME Motherboard and I was astonished to read the LBA_written at a value of 0,000y TBW (about 1/1000 smaller then the value before and different).
I cannot explain myself how this can be! Have you encountered something like this? Could it be a internal SSD-Firmware glitch?Thanks for feedback and a nice Weekend,
fireodo -
Mmm, never seen that. It does sounds like a firmware issue. Odd SMART values are usually due to some manufacturer custom data that is misinterpreted but that shouldn't change just by connecting to it on a different port. Weird.
-
@stephenw10 said in Strange SSD S.M.A.R.T behavior:
but that shouldn't change just by connecting to it on a different port. Weird.
As you said ... I also searched the Net but I couldn't find anything similar ...
PS. the only thing I could imagine is that the mSATA -> SATA Adapter is not a 100% transparent bridge between the mSATA SSD and the motherboard SATA Port. But on the layout of the Adapter I can see only passive electronic elements. (except that tiny element on the bottom of the image (in b&w))
Have a fine Sunday,
fireodo -
Yeah, I would not expect anything different there. The adapter just connects the SATA lines on the mSATA connector. Those components are probably power related.
I could maybe believe that SMART can talk to the drive differently in the on-board mSATA slot if it has more pins connected. Like maybe over smbus/i2c. Though I don't know why it would return different values. -
@stephenw10 said in Strange SSD S.M.A.R.T behavior:
I could maybe believe that SMART can talk to the drive differently in the on-board mSATA slot if it has more pins connected. Like maybe over smbus/i2c.
This is a plausible explanation.
Though I don't know why it would return different values.
I can only explain (this is a early produced SSD from about 2009) this to me with a faulty firmware ...
Strange, Strange ...
