does not seem that easy, because rev.3135 requires 3133 which patches code that is completely different or does not exist at all. I'll look at this again on Monday and pull out all patches required or update smartmantools to svn snapshot, because there should be nearly zero risk

we will be going the snapshot update way, because for example debian uses the same update and updated version brings tool for updating driver database helping with similar issues in the future. I'll build updated packages, but they will be delayed from updates(-testing) until dependant bug is fixed

Thanks Michal,

I've downloaded smartmontools-5.39.1-2.r3169.fc13.x86_64 and it works nicely with my COZ Vertex2.
Now since smartmontools correctly detects my drive I noticed, that Gnome's "Disk Utility 2.30.1" doesn't support my drive either. Will report this bug as well.
Anyway, you can set the status of this bz to verified (or whatever the best status is...)

Helge

Hi Helge,

status of this bug should be MODIFIED = bug is fixed in git repository and (usually) new package is built. Next status will be ON_QA - this status is automatically set by bodhi update system once package is pushed to updates-testing repository. After successful testing it's pushed as regular update and bz status is set to CLOSED:ERRATA (we don't use VERIFIED for Fedora) and fixed in version is automatically set by bodhi update system. Some package maintainers (bug assignees) set this when changing bug status to MODIFIED. For this bz we're waiting for selinux-update because other way update package would cause selinux denials.

Thanks for testing.

smartmontools-5.40-1.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/smartmontools-5.40-1.fc13

smartmontools-5.40-1.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/smartmontools-5.40-1.fc14

smartmontools-5.40-1.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update smartmontools'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/smartmontools-5.40-1.fc14

I updated to smartmontools-5.40-1.fc14 and was still told that, "DISK IS BEING USED OUTSIDE DESIGN PARAMETERS" ... My SSD was recognized:

Model: ATA OCZ-VERTEX2 3.5
Firmware Version: 1.11
...
Rotation Rate: Solid-State Disk
Connection: ATA

/var/log/messages has this:
Oct 19 09:36:21 esau kernel: [ 4948.704043] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Oct 19 09:36:21 esau kernel: [ 4948.704053] ata1.00: failed command: SMART
Oct 19 09:36:21 esau kernel: [ 4948.704065] ata1.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
Oct 19 09:36:21 esau kernel: [ 4948.704067]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 19 09:36:21 esau kernel: [ 4948.704073] ata1.00: status: { DRDY }
Oct 19 09:36:21 esau kernel: [ 4948.704082] ata1: hard resetting link
Oct 19 09:36:22 esau kernel: [ 4949.009035] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 19 09:36:22 esau kernel: [ 4949.089502] ata1.00: configured for UDMA/133
Oct 19 09:36:22 esau kernel: [ 4949.089538] ata1: EH complete

(In reply to comment #8)
> I updated to smartmontools-5.40-1.fc14 and was still told that, "DISK IS BEING
> USED OUTSIDE DESIGN PARAMETERS" ... 

what do you mean by this? could you paste here complete smartctl output?


and that messages in /var/log/messages, do they appear only when you use smartctl or do they happen independently on smartctl?

Sorry -- the top messages were from the gnome tool that keeps telling me my disk is failing.  The /var/log/messages happen when smartctl is run.  They also appear when the gnome tool tries to update the SMART status in the GUI.    It appears that I missed the first line last time:

Oct 19 10:27:24 esau kernel: [ 8011.744053] ata1.00: NCQ disabled due to excessive errors

Smartctl reports this:

# smartctl --all /dev/sda
smartctl 5.40 2010-10-16 r3189 [x86_64-redhat-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     SandForce Driven SSDs
Device Model:     OCZ-VERTEX2 3.5
Serial Number:    OCZ-CTANH1539IQUPU0T
Firmware Version: 1.11
User Capacity:    90,028,302,336 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Tue Oct 19 10:27:04 2010 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Error SMART Values Read failed: Input/output error
Smartctl: SMART Read Values failed.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.

Error SMART Error Log Read failed: Input/output error
Smartctl: SMART Error Log Read Failed
Error SMART Error Self-Test Log Read failed: Input/output error
Smartctl: SMART Self Test Log Read Failed
Device does not support Selective Self Tests/Logging

could you add output of:

smartctl -P show /dev/sda

and output of

smartctl -a -P ignore /dev/sda

and output of 

skdump /dev/sda

thanks

Sorry it took me so long to get to this...

# smartctl -P show /dev/sda
smartctl 5.40 2010-10-16 r3189 [x86_64-redhat-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

Drive found in smartmontools Database.  Drive identity strings:
MODEL:              OCZ-VERTEX2 3.5
FIRMWARE:           1.11
match smartmontools Drive Database entry:
MODEL REGEXP:       SandForce 1st Ed\.|Corsair CSSD-F(40|60|80|120|160|240)GBP?2.*|OCZ[ -](AGILITY2|VERTEX2|VERTEX-LE)( .*)?|UGB(88P|99S)GC...H[BF].
FIRMWARE REGEXP:    .*
MODEL FAMILY:       SandForce Driven SSDs
ATTRIBUTE OPTIONS:  001 Raw_Read_Error_Rate
                    005 Retired_Block_Count
                    009 Power_On_Hours_and_Msec
                    013 Soft_Read_Error_Rate
                    100 Gigabytes_Erased
                    170 Reserve_Block_Count
                    171 Program_Fail_Count
                    172 Erase_Fail_Count
                    174 Unexpect_Power_Loss_Ct
                    177 Wear_Range_Delta
                    181 Program_Fail_Count
                    182 Erase_Fail_Count
                    184 IO_Error_Detect_Code_Ct
                    195 ECC_Uncorr_Error_Count
                    198 Uncorrectable_Sector_Ct
                    199 SATA_CRC_Error_Count
                    201 Unc_Soft_Read_Err_Rate
                    204 Soft_ECC_Correct_Rate
                    230 Life_Curve_Status
                    231 SSD_Life_Left
                    233 SandForce_Internal
                    234 SandForce_Internal
                    235 SuperCap_Health
                    241 Lifetime_Writes_GiB
                    242 Lifetime_Reads_GiB
[root@esau ~]# smartctl -a -P ignore /dev/sda
smartctl 5.40 2010-10-16 r3189 [x86_64-redhat-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Model Family:     SandForce Driven SSDs
Device Model:     OCZ-VERTEX2 3.5
Serial Number:    OCZ-CTANH1539IQUPU0T
Firmware Version: 1.11
User Capacity:    90,028,302,336 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 6
Local Time is:    Thu Oct 21 22:58:36 2010 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Error SMART Values Read failed: Input/output error
Smartctl: SMART Read Values failed.

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.

Error SMART Error Log Read failed: Input/output error
Smartctl: SMART Error Log Read Failed
Error SMART Error Self-Test Log Read failed: Input/output error
Smartctl: SMART Self Test Log Read Failed
Device does not support Selective Self Tests/Logging
# skdump /dev/sda
Device: sat16:/dev/sda
Type: 16 Byte SCSI ATA SAT Passthru
Size: 85857 MiB
Model: [OCZ-VERTEX2 3.5]
Serial: [OCZ-CTANH1539IQUPU0T]
Firmware: [1.11]
SMART Available: yes
Quirks:
Awake: yes
SMART Disk Health Good: yes
Off-line Data Collection Status: [Off-line data collection activity was never started.]
Total Time To Complete Off-Line Data Collection: 0 s
Self-Test Execution Status: [The previous self-test routine completed without error or no self-test has ever been run.]
Percent Self-Test Remaining: 0%
Conveyance Self-Test Available: no
Short/Extended Self-Test Available: no
Start Self-Test Available: no
Abort Self-Test Available: no
Short Self-Test Polling Time: 0 min
Extended Self-Test Polling Time: 0 min
Conveyance Self-Test Polling Time: 0 min
Bad Sectors: No such file or directory
Powered On: No such file or directory
Power Cycles: No such file or directory
Temperature: No such file or directory
Attribute Parsing Verification: Good
Overall Status: GOOD
ID# Name                        Value Worst Thres Pretty      Raw            Type    Updates Good Good/Past
 48 attribute-48                 48    48   n/a   n/a         0x302c30303030 old-age offline n/a  n/a 
 48 attribute-48                 44    48   n/a   n/a         0x303030303030 old-age offline n/a  n/a 
 44 attribute-44                 48    48   n/a   n/a         0x303030302c30 old-age offline n/a  n/a 
 48 attribute-48                 48    48   n/a   n/a         0x302c30303030 old-age offline n/a  n/a 
 48 attribute-48                 44    48   n/a   n/a         0x303030303030 old-age offline n/a  n/a 
 44 attribute-44                 48    48   n/a   n/a         0x303030380a00 old-age offline n/a  n/a 
#

smartmontools-5.40-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

smartmontools-5.40-1.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

(In reply to comment #12)

Today, I got (almost) the same ssd as you have. The device you have should be working in normal circumstances. However ssd manufacturer did not make these devices perfect, but they fixed some issues in recent firmware updates. Also firmware seem quite old. Recent version fixed for example:

* Fixed a rare condition in which a drive could hang on a SLEEP command.

and this is just change from 1.21 -> 1.23 but your firmware is even older (1.11).

Anyway, new firmware should make it better, but still not perfect as it's written in known issues section. For example:

* SMART command B0 occasionally returns incorrect status.
* Resetting SMART PHY event counters has no effect.
* Sleep followed by non-data commands can sometimes cause the drive to fail to respond to the non-data command.
...

(see http://www.ocztechnology.com/files/ssd_tools/OCZ%20SSD%20v1%2023%20Firmware%20Release%20Notes.pdf )

So my advice is: try to update firmware and if you're lucky all issues you see will be gone.

for "scary" information gnome-disk-utility (aka palimsest) shows:

> "DISK IS BEING USED OUTSIDE DESIGN PARAMETERS"

it seems it's libatasmart's bug, because based on it's own logic it should show this if it finds any attribute that is failing, but skdump (which shows the the data libatasmart read) shows it did not find any failing attribute, but just no attribute it understands:


> # skdump /dev/sda
...
> Bad Sectors: No such file or directory
> Powered On: No such file or directory
> Power Cycles: No such file or directory
> Temperature: No such file or directory
> Attribute Parsing Verification: Good
> Overall Status: GOOD
> ID# Name                        Value Worst Thres Pretty      Raw           
> Type    Updates Good Good/Past
>  48 attribute-48                 48    48   n/a   n/a         0x302c30303030
> old-age offline n/a  n/a 
>  48 attribute-48                 44    48   n/a   n/a         0x303030303030
> old-age offline n/a  n/a 
>  44 attribute-44                 48    48   n/a   n/a         0x303030302c30
> old-age offline n/a  n/a 
>  48 attribute-48                 48    48   n/a   n/a         0x302c30303030
> old-age offline n/a  n/a 
>  48 attribute-48                 44    48   n/a   n/a         0x303030303030
> old-age offline n/a  n/a 
>  44 attribute-44                 48    48   n/a   n/a         0x303030380a00
> old-age offline n/a  n/a 
> #