Skip to content
This repository has been archived by the owner on Jun 17, 2023. It is now read-only.

SMART self-test not working on OCZ SSD as cache device #10

Open
jonpanozzo opened this issue Nov 24, 2014 · 3 comments
Open

SMART self-test not working on OCZ SSD as cache device #10

jonpanozzo opened this issue Nov 24, 2014 · 3 comments

Comments

@jonpanozzo
Copy link
Collaborator

This is extremely odd as it is only affecting this particular SSD on one of the test systems. Its a 120GB OCZ-VERTEX3 SSD that I'm using as the cache device with BTRFS (single device, no pool).

It's not malfunctioning or anything like that, but SMART self-tests don't seem to work through the webGui on it. The test "runs" in that it moves through the percentages, but when it completes, nothing shows up on the self-test log page and "Last SMART test result" still shows "No self-tests logged on this disk."

Trying this with other SSDs on another test system and they seem to work just fine. Tried clearing my cache and another browser (tested both Chrome and Safari so far) and this doesn't resolve the issue.

Disk identity sub-page
Model Family: SandForce Driven SSDs
Device Model: OCZ-VERTEX3
Serial Number: OCZ-83X3BLPQ1M7YJ2YG
LU WWN Device Id: 5 e83a97 c33a5ec1b
Firmware Version: 2.22
User Capacity: 120,034,123,776 bytes [120 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS, ACS-2 T13/2015-D revision 3
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Mon Nov 24 16:11:52 2014 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
SMART overall-health : PASSED

@jonpanozzo jonpanozzo added bug and removed bug labels Nov 24, 2014
@limetech
Copy link
Owner

SMART self-tests don't seem to work through the webGui on it.

Does it work if you invoke smartctl on the command line? Probably this is a bug with this particular model SSD. Google "OCZ-VERTEX3 SSD no smart log" reveals maybe you need to update the bios on the SSD:
http://ocz.com/consumer/download/firmware

@jonpanozzo
Copy link
Collaborator Author

That was something I had suspected as well (firmware update needed). I will test tomorrow as I need to bring the drive to Eric’s to do so.

You are correct that this is a problem with SMART on this particular SSD. When I run smartctl -a on that device, I see the following at the end of the page:

SMART Error Log not supported

SMART Self-test Log not supported

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

We might want to put handling code in there to detect this message and if we see that, grey out the self test buttons and indicate this on the logs screen (suggest checking with the drive manufacturer for a firmware update / official SMART support).

On Nov 24, 2014, at 5:13 PM, tom mortensen notifications@github.com wrote:

SMART self-tests don't seem to work through the webGui on it.

Does it work if you invoke smartctl on the command line? Probably this is a bug with this particular model SSD. Google "OCZ-VERTEX3 SSD no smart log" reveals maybe you need to update the bios on the SSD:
http://ocz.com/consumer/download/firmware http://ocz.com/consumer/download/firmware

Reply to this email directly or view it on GitHub #10 (comment).

@jonpanozzo
Copy link
Collaborator Author

Bringing this ticket full circle, even after attaching the drive to a Windows PC directly and applying the firmware update, the drive still does not support SMART self-testing / logging. I think Eric has what he needs to implement a way to detect the lack of support for this now and not offer those features for devices that do not support them (prompt the user that their device has no support and that they should check with the device mfg for firmware updates to see if support has been added).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants