rssLink RSS for all categories
 
icon_red
icon_green
icon_red
icon_red
icon_blue
icon_green
icon_green
icon_red
icon_red
icon_red
icon_orange
icon_green
icon_green
icon_green
icon_green
icon_blue
icon_red
icon_orange
icon_red
icon_red
icon_red
icon_red
icon_green
icon_red
icon_red
icon_red
icon_red
icon_orange
icon_green
 

FS#96 — FS#3467 — smartctl & SSD

Attached to Project— Dedicated servers
Maintenance
all (dedicated servers)
CLOSED
100%
Concerning the SSD servers: we found an incompatibility
between the smartctl software AND some SSD 32nm discs (happens sometimes).
Basically, the smartctl soft allows to look upon the disc status and
potential errors. Sometimes, smartctl cannot recover that
disk status and the request arrives in a timeout, which causes a hard SATA2 reset
of the disk. It's a minor bug which does not prevent the smooth functioning of the
server. However, we advice not to use
smartctl until Intel engineers fix this minor bug.

Date:  Friday, 21 May 2010, 17:34PM
Reason for closing:  Done
Comment by OVH - Friday, 21 May 2010, 17:28PM

We deactivate the smartd and smartctl software on the new installations and
reinstallations for all the machines that have SSD drives.


Comment by OVH - Friday, 21 May 2010, 17:28PM

conformation from Intel of a bug.

"I have replicated the issue with Debian 5 using a laptop not a desktop board
and I escalated your issue to the US-engineers. Currently I am awaiting
feedback."


Comment by OVH - Friday, 21 May 2010, 17:29PM

Intel case 9399705 - Intel X25-M Solid State Drive


Comment by OVH - Friday, 21 May 2010, 17:30PM

Update of case 9399705 with Intel:

"We received response from the escalation regarding the SMART error when using the Intel?? Solid-State-Drive.
The issue has been investigated and it appears to be related to the fact that the drive does not support READ LOG EXTcommands.
The only workaround at this point is not to use READ LOG EXT. The performance of the drives should not be affected by this."

We wait to have a correction date for the problem from Intel.


Comment by OVH - Friday, 21 May 2010, 17:34PM

Update of case 9399705 with Intel:

"The issue has been reproduced and confirmed again that it is caused by the solid state drives not supporting Read Log Ext ATA.

The command smartctl -a /dev/sda displays all SMART information from the drive, including the SMART self-test log which is what is calling
the Read Log Ext ATA and it fails then.

So, it is possible to use other smartctl commands and get all the other SMART information without causing the failure.

For example, the following commands will work fine:
smartctl --attributes /dev/sda - displays all SMART attributes
smartctl --health /dev/sda - displays overall SMART health status of the drive

It appears that a fix is planned in a future firmware version of the solid state drives but I cannot tell exactly when we can expect that
firmware release."