Bug 1103179 - incorrect SMART event desriptors (inconsistent with smartctl)
Summary: incorrect SMART event desriptors (inconsistent with smartctl)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: libatasmart
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1140791 (view as bug list)
Depends On:
Blocks: 1140791
TreeView+ depends on / blocked
 
Reported: 2014-05-30 12:27 UTC by Przemek Klosowski
Modified: 2018-11-30 18:15 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-30 18:15:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Przemek Klosowski 2014-05-30 12:27:31 UTC
Description of problem:
skdump reports incorrect SMART attribute names for Crucial/Micron RealSSD m4/C400/P400 SSD

Version-Release number of selected component (if applicable):
libatasmart-0.19-5.fc20.x86_64


How reproducible: every time


Steps to Reproduce:
1. skdump /dev/sda
2. attributes 170, 173,174, 181, 183, 189, 202, 206 are reported incorrectly


Actual results:
170	available-reserved-space
173	attribute-173
174	attribute-174
181	program-fail-count-total
183	runtime-bad-block-total
189	high-fly-writes
202	ta-increase-count
206	flying-height


Expected results:
170	Grown_Failing_Block_Ct
173	Wear_Leveling_Count
174	Unexpect_Power_Loss_Ct
181	Non4k_Aligned_Access
183	SATA_Iface_Downshift
189	Factory_Bad_Block_Ct
202	Perc_Rated_Life_Used
206	Write_Error_Rate


Additional info:

Comment 1 Przemek Klosowski 2014-05-30 12:35:57 UTC
I see that libatasmart website http://git.0pointer.de/?p=libatasmart.git shows very little activity--last commit was 2012-05-20. 

I originally started using libatasmart/skdump because it had better support for USB bridges (getting SMART data from external USB enclosures). Now, however, smartmontools caught up, it seems to be more actively developed, has a well defined mechanism for updating its disk database and even allows real-time updates of the disk information via /usr/sbin/update-smart-drivedb 

Is there still a reason for libatasmart as an independent SMART toolset?

Comment 2 Przemek Klosowski 2014-09-11 17:24:55 UTC
The symptoms are identical to gnome-disks bug 
https://bugzilla.redhat.com/show_bug.cgi?id=1140791

I am not sure if libatasmart is used in gnome-disks (it's not on its ldd list of shared libs). If it is used there, it'd be an argument to 'backport' smartmontools approach for updating the SMART parameter mapping.

Thoughts?

Comment 3 Michael Catanzaro 2015-03-24 02:02:23 UTC
*** Bug 1140791 has been marked as a duplicate of this bug. ***

Comment 4 Fedora End Of Life 2015-05-29 11:59:05 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Przemek Klosowski 2015-05-29 14:36:23 UTC
This is still a problem in F21 ( libatasmart-0.19-7.fc21.x86_64 )

Comment 6 Przemek Klosowski 2015-09-15 01:27:57 UTC
This is still a problem in F22 ( libatasmart-0.19-7.fc22.x86_64 )

Comment 7 Fedora End Of Life 2016-07-19 11:35:23 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 8 Przemek Klosowski 2016-07-19 15:45:58 UTC
This is an ongoing issue, still present in F23 (libatasmart-0.19-8.fc23.x86_64)

Comment 9 Fedora End Of Life 2016-11-24 11:10:29 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 10 Przemek Klosowski 2016-11-25 15:17:34 UTC
This is still a problem in F22 ( libatasmart-0.19-9.fc24.x86_64 )

Comment 11 Przemek Klosowski 2016-11-25 15:20:31 UTC
(In reply to Przemek Klosowski from comment #10)
> This is still a problem in F22 ( libatasmart-0.19-9.fc24.x86_64 )
s/F22/F25/ of course

Comment 12 Fedora End Of Life 2017-11-16 19:12:40 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 13 Przemek Klosowski 2017-11-16 19:26:54 UTC
This is still a problem in Fedora 27 and libatasmart-0.19-13.fc27.x86_64

Comment 14 Ben Cotton 2018-11-27 18:13:22 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Ben Cotton 2018-11-30 18:15:23 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.