Extend smart by adding a timestamp when last successful smart test finished
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- c
- Domain
- infrastructure
Research direction
Start with the SMART plugin, which now shells out to smartmontools, and find where it reads device attributes. The issue's sample smartctl -a output shows the Self-test log with a LifeTime(hours) column; that value is the one to capture for the last completed test. Done means the plugin reports that value, and it needs a decision on how to expose it through the D-Bus API. Expect maintainer input on that API choice before writing code.
Written by the indexing model from the issue text.
Description
Since the SMART plugin is now implemented by using smartmontools it would be nice to include a timestamp of the last finished self test.
When I use smartctl -a /dev/sda to check status of my disk I can see a history of self-tests and it includes a LifeTime timestamp when the tests was finished. The LifeTime number corresponds to the disk power-on-hours value.
SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 4539 -
# 2 Short offline Completed without error 00% 4372 -
# 3 Short offline Completed without error 00% 4132 -
...
It would be nice if this value was then available in the udisks dbus api.
- Dominant language
- C
- Stars
- 137
- Forks
- 64
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from storaged-project/libblockdev
-
fails to build with libnvme3 (nvme-cli 3.0)Possibly taken @tbzatek claimed this 43 days ago. Open
storaged-project/libblockdev#1211 · 4 comments · 1 assignee ·
-
Difficulty 4/5 Over a week Newbie friendliness 18/100
storaged-project/libblockdev#1067 ·
-
Difficulty 3/5 Half a day Newbie friendliness 40/100
storaged-project/libblockdev#1060 · 1 comment ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 12/100
storaged-project/libblockdev#977 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
storaged-project/libblockdev#966 · 3 comments ·
All issues in storaged-project/libblockdev
Similar issues
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
enhancement ui
Difficulty 1/5 Under an hour Newbie friendliness 72/100
ChupathingyCE/chupathingyce#485 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
eclipse-paho/paho.mqtt.c#1727 ·
Maintainers usually reply within 6 days