summaryrefslogtreecommitdiffstats
path: root/atasmart.c
Commit message (Collapse)AuthorAgeFilesLines
* attributes: Add S.M.A.R.T attributes for Samsung SSDTobias Wolf2012-05-211-0/+9
| | | | | | | | | | | | | | | | | | | Taken from: http://www.samsung.com/global/business/semiconductor/products/SSD/downloads/ds_SS805_NSSD_100_SLC_SATA_II_rev11.pdf Description: Attribute Name 175 Program Fail Count (Chip) 176 Erase Fail Count (Chip) 177 Wear Leveling Count 178 Used Reserved Block Count (Chip) 179 Used Reserved Block Count (Total) 180 Unused Reserved Block Count (Total) 181 Program Fail Count (Total) 182 Erase Fail Count (Total) 183 Runtime bad block (Total) Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/885869
* quirks: add quirks for Intel SSD Serie 320Oleksij Rempel (Alexey Fisher)2012-05-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | According to Intel documantation, complete SSD Serie 320 use same SMART parameters. I tested it with one more drive: INETL_SSDSA2CT040G3. Also i collected serial numbers for Intel SSD Serie 320 deevices: serie 320: 40GB: SSDSA2CT040G3K5 SSDSA2CT040G301 SSDSA2CT040G3B5 SSDSA2CT040G310 SSDSA2BT040G3 80GB: SSDSA2CW080G3K5 SSDSA2CW080G301 SSDSA2CW080G3B5 SSDSA2CW080G310 SSDSA2BW080G3 120GB: SSDSA2CW120G3B5 SSDSA2CW120G3K5 SSDSA2CW120G301 SSDSA2CW120G310 160GB: SSDSA2CW160G3K5 SSDSA2CW160G3B5 SSDSA2BW160G3 300GB: SSDSA2CW300G3K5 SSDSA2CW300G3B5 SSDSA2BW300G3 600GB: SSDSA2CW600G3K5 SSDSA2CW600G301 SSDSA2CW600G3B5 SSDSA2CW600G310 this patch set RegExp for all this devices.
* atasmart: multiply by sector threshold by 1024 to avoid false positivesLennart Poettering2011-10-111-3/+4
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=25772
* Speed up get_overall() and get_bad()Martin Pitt2011-10-111-53/+44
| | | | | | | | | Instead of iterating through all attributes four times for an sk_disk_smart_get_overall() call, just do it once and store the results in SkDisk. This considerably speeds up libatasmart for common operations like smart_get_overall() and smart_get_bad(). https://bugs.freedesktop.org/show_bug.cgi?id=26834
* atasmart: sector field can never be larger then 48 bits, so no point in ↵Lennart Poettering2011-10-111-1/+1
| | | | comparing with (uint64_t) -1
* atasmart: ignore sector count if it is -1Lennart Poettering2011-10-111-1/+3
| | | | https://bugs.freedesktop.org/show_bug.cgi?id=25021
* Add quirk namesWojciech Piekutowski2011-04-131-0/+7
|
* Treat 'Media Wearout Indicator' as a percentageWojciech Piekutowski2011-04-121-1/+1
|
* Disable short time verification for Spin Up TimeWojciech Piekutowski2011-04-121-0/+14
|
* Support Timed Workload Media Wear, Timed Workload Host Reads, Workload TimerWojciech Piekutowski2011-04-121-18/+70
|
* Support Program Fail Count and Erase Fail Count attributesWojciech Piekutowski2011-04-121-0/+2
|
* Show MB, GB or TB depending on the valueWojciech Piekutowski2011-04-121-7/+12
|
* Start/Stop Count always shows 0 for Intel SSD G3Wojciech Piekutowski2011-04-121-1/+14
|
* Handle duplicated Available Reserved SpaceWojciech Piekutowski2011-04-121-0/+1
|
* Handle duplicated Total LBAs WrittenWojciech Piekutowski2011-04-121-16/+30
|
* Handle Total LBAs Written and Total LBSa ReadWojciech Piekutowski2011-04-121-1/+11
|
* Handle Media Wearout IndicatorWojciech Piekutowski2011-04-121-2/+16
|
* Handle Available Reserved SpaceWojciech Piekutowski2011-04-111-2/+22
|
* Display endurance-remaining as percentage decreasing from 100 to 0Wojciech Piekutowski2011-04-111-2/+9
|
* libatasmart patchGuy Taylor2010-02-171-0/+2
| | | | | | | | | | | | | | | hi I have made a patch for libatasmart to add support for attribute 184 and 188. just adds the name to them. Anyway I thought you might want to take a look at it. Iv attached the patch against the git master and here is the link to the Ubuntu's bug/patch https://bugs.launchpad.net/libatasmart/+bug/521864 Thanks Guy Taylor
* blacklist another bridgeLennart Poettering2009-12-181-4/+11
| | | | http://bugs.freedesktop.org/show_bug.cgi?id=24951
* fix return of uninitialized variableDavid Zeuthen2009-12-181-0/+1
| | | | | | | | | | | | | | | | | | atasmart.c: In function ‘init_smart’: atasmart.c:2556: warning: ‘ret’ may be used uninitialized in this function We apparently don't initialize the ret variable in init_smart() - unfortunately o this warning is never reported with using -O0 (thanks gcc - see http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings though) o we never run into this bug with just skdump(1) The bug does show up in the udisks (aka DeviceKit-disks) use of libatasmart and this patch fixes it. http://bugs.freedesktop.org/show_bug.cgi?id=25543
* make init_smart() staticLennart Poettering2009-10-271-2/+2
|
* more Apple SSD firmware versions are evil then originally thoughtLennart Poettering2009-10-271-2/+3
|
* Ignore attributes 5 and 190 on some Apple SSDLennart Poettering2009-10-241-0/+15
| | | | http://bugs.freedesktop.org/show_bug.cgi?id=24700
* check the right boolean when calculating blob sizeLennart Poettering2009-10-231-1/+1
|
* delay smart initialization until the first SMART call is doneLennart Poettering2009-10-231-20/+48
|
* blacklist: disable jmicron access mode for some more jmicron bridgesLennart Poettering2009-09-291-7/+16
| | | | | | This is a followup on: https://bugzilla.redhat.com/show_bug.cgi?id=515881
* blacklist 152d:2329 jmicron usb bridgesLennart Poettering2009-09-171-3/+9
|
* support some ssd smart attrsLennart Poettering2009-08-201-1/+10
|
* highlight if smart status is badLennart Poettering2009-08-061-3/+4
|
* fix parsing of power-on-minutesLennart Poettering2009-08-061-2/+2
|
* rework lgoic that determines verdict of driveLennart Poettering2009-08-061-32/+92
| | | | | | | | | | | Distuingish attributes that are failing now vs. failed in the past. Add 'warn' field that is used to signal UIs to highlight certain attributes. Beef up the "overall status" logic a bit. This breaks ABI. Depending on your client this might break API too.
* rename failed to badLennart Poettering2009-08-061-6/+6
|
* add MHY2250B/0085000B to quirk dbLennart Poettering2009-08-061-1/+4
| | | | https://bugzilla.redhat.com/show_bug.cgi?id=499265
* verify parsing of all attributesLennart Poettering2009-08-061-64/+128
|
* blacklist attribute 5 of an hitachi driveLennart Poettering2009-08-051-13/+24
| | | | https://bugzilla.redhat.com/show_bug.cgi?id=506254
* if the ID_ATA_SMART_ACCESS udev env var is set for a device read the access ↵Lennart Poettering2009-05-071-0/+22
| | | | method from it
* show full device string when dumping statusLennart Poettering2009-05-071-1/+3
|
* allow prefixing device strings with access methodsLennart Poettering2009-05-071-17/+77
|
* rename SK_DISK_TYPE_ATA to SK_DISK_TYPE_LINUX_IDELennart Poettering2009-05-071-6/+6
|
* black list a few attributes on FUJITSU MHY2120BH/0085000BLennart Poettering2009-05-061-2/+27
|
* look at lower 32 bit of current-pending-sector raw data only, similar to ↵Lennart Poettering2009-05-061-1/+2
| | | | reallocated-sector-count
* add another sunplus bridge to the list of supported sunplus bridgesLennart Poettering2009-04-241-1/+2
|
* add missing 'else'Lennart Poettering2009-04-241-1/+1
|
* Get rid of qurik 9_UNKNOWN againLennart Poettering2009-04-241-12/+3
| | | | | | | | | Apparently Seagate seems to use the MSB's of the raw data of the power-on-time field for something else on some disks, so let's just look at the lower 32bits of that field and we get a value that works on all disks including those from Seagate. 32bit should be more than enough to encode the power-on-time for almost all disks so this should not be much of a limitation.
* Seagate's ST9160821AS drive encodes something strange in attribute 9Lennart Poettering2009-04-231-1/+10
| | | | | | | | Attribute 9 of ST9160821AS apparently is not the power on time in hours. Since we have no idea what it is and how it is encoded this adds a quirk to mark the attribute as 'unknown' for this drive. See rhbz #497107.
* don't claim we would know what reallocated-event-count actually isLennart Poettering2009-04-231-3/+2
| | | | | | | | We don't reliably know what this actually is on many drives and since it is redundant to reallocated-sectors-count it's no loss to admit that we have no clue. See rhbz #497107.
* use only uppermost 32 bits for reallocated-sectors-count attribute pretty valueLennart Poettering2009-04-231-0/+2
| | | | | | | | | This seems to fix the attribute for Fujitsu drives. And those 32 bit should be enough to still encode bad sectors up to 2TB which should be more than enough. Hence it is probably safe to ignore the remaing 16 bit even on non-Fujitsu drives. See rhbz #496087.
* Support for JMicron ATA/USB bridgesLennart Poettering2009-04-221-13/+144
|
generated by cgit (git 2.34.1) at 2024-04-25 10:23:38 +0000