OCZ Vertex: Device: /dev/sdX [SAT], same Attribute has different ID numbers:

Bug #661434 reported by RK
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
smartmontools (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: smartmontools

Smartd regularly complains about the attributes being inconsistent:

Oct 15 21:37:08 rk smartd[3161]: Device: /dev/sdc [SAT], same Attribute has different ID numbers: 177 = 177 = 181
Oct 15 21:37:08 rk smartd[3161]: Device: /dev/sdc [SAT], same Attribute has different ID numbers: 181 = 181 = 182
Oct 15 21:37:08 rk smartd[3161]: Device: /dev/sdc [SAT], same Attribute has different ID numbers: 182 = 182 = 187
Oct 15 21:37:08 rk smartd[3161]: Device: /dev/sdc [SAT], same Attribute has different ID numbers: 187 = 187 = 194
Oct 15 21:37:08 rk smartd[3161]: Device: /dev/sdc [SAT], same Attribute has different ID numbers: 194 = 194 = 195
Oct 15 21:37:08 rk smartd[3161]: Device: /dev/sdc [SAT], same Attribute has different ID numbers: 231 = 231 = 233
Oct 15 21:37:08 rk smartd[3161]: Device: /dev/sdc [SAT], same Attribute has different ID numbers: 233 = 233 = 234
Oct 15 21:37:08 rk smartd[3161]: Device: /dev/sdc [SAT], same Attribute has different ID numbers: 234 = 234 = 241
Oct 15 21:37:08 rk smartd[3161]: Device: /dev/sdc [SAT], same Attribute has different ID numbers: 241 = 241 = 242

The disc in question is an OCZ Vertex 2 SSD. The reason is that the smartmontools treat the new SandForce based OCZ discs the same as the old Indilinx based discs, but the SandForce ones use a different variant of the attributes.

Please update smartmontools or at least the drivedb.h file to a newer version. Here's the relevant upstream change:

http://sourceforge.net/apps/trac/smartmontools/changeset/3135/trunk/smartmontools/drivedb.h

(There are smaller changes to this section later.)

Thanks.

RK (kubuntu-rk)
tags: added: drivedb.h
removed: driverdb
Revision history for this message
Christian Franke (christian-franke) wrote :

The warning messages appear because the threshold of attribute 177 is missing in the SMART threshold data reported by SandForce based SSDs. Updating drivedb.h won't suppress the messages.

Smartmontools now accepts missing attributes. The change will be included in upcoming release 5.40
http://sourceforge.net/apps/trac/smartmontools/changeset/3132
http://sourceforge.net/apps/trac/smartmontools/roadmap

Revision history for this message
Christian Franke (christian-franke) wrote :

Fixed in smartmontools 5.40 released 2010-10-16.

Changed in smartmontools (Ubuntu):
status: New → Confirmed
Revision history for this message
DigiAngel (jlay) wrote :

I've started seeing this myself...very strange as they started the 29th of this October.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.