-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nvme disk show as unknown #22
Comments
Can you check if UDisks export the SMART attributes using a dbus client like Looking more in debt into udisks I found the following issues that seem related: storaged-project/udisks#433 and storaged-project/udisks#649 |
seems this storaged-project/udisks#386 |
Same problem here: `sudo smartctl --info /dev/nvme0n1 === START OF INFORMATION SECTION === `cat /etc/os-release uname -a |
I am experiencing this issue as well in DisKMonitor 0.3.4...
Operating System: Manjaro Linux
|
The same for me in DisKMonitor 0.3.4: sudo smartctl --info /dev/nvme0n1 smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.32-1-MANJARO] (local build) Operating System: Manjaro Linux |
This issue is still blocked upstream by udisk but things might move on their side eventually : the related issue receveid an interesting update yesterday storaged-project/udisks#386 (comment) |
Seems to been have fixed some time ago (storaged-project/udisks#975). |
yes. but not released (only in GIT build) |
seems the udisk issue is fixed (libnvme is released with things fixed) . needs do something here? greetings |
Yes indeed, shipped with udisks2-2.10 (storaged-project/udisks#1121), available on Arch but not yet on Manjaro. Definitely some work to do on diskmonitor as the Drive.Ata and NVMe.Controller interfaces have some differences. Can you try to list SmartGetAttributes using QDDusViewer ? On my drive I get errors when trying to call the methods, the properties are fine though. |
seems need something with libatasmart or a future implementation in libblockdev with smartmontools plugin storaged-project/udisks#1063 |
Any news on this one? NVMEs are pretty common these days. |
Hello, tested this today and I got some results. Not much, but better than nothing. I'll try to find some time to work on this again in the coming weeks. Can you try the following python script with your drive and see if you get more attributes ? from pydbus import SystemBus
bus = SystemBus()
remote_object = bus.get("org.freedesktop.UDisks2", "/org/freedesktop/UDisks2/drives/CT1000P2SSD8_2102E4E73A82")
remote_object.Introspect()
print(remote_object.SmartGetAttributes(dict())) On my drive I get the following
|
Nice. For my Crucial CT4000T500 NVME I get: {
"avail_spare": 100,
"spare_thresh": 5,
"percent_used": 2,
"total_data_read": 1232784327168000,
"total_data_written": 97919358464000,
"ctrl_busy_time": 16240,
"power_cycles": 3,
"unsafe_shutdowns": 1,
"media_errors": 0,
"num_err_log_entries": 0,
"temp_sensors": [
324,
0,
0,
0,
0,
0,
0,
0
],
"wctemp": 359,
"cctemp": 361,
"warning_temp_time": 0,
"critical_temp_time": 0
} And for Crucial CT2000T500 NVME: {
"avail_spare": 100,
"spare_thresh": 5,
"percent_used": 17,
"total_data_read": 4163753544704000,
"total_data_written": 270169098240000,
"ctrl_busy_time": 43295,
"power_cycles": 64,
"unsafe_shutdowns": 45,
"media_errors": 0,
"num_err_log_entries": 0,
"temp_sensors": [
323,
0,
0,
0,
0,
0,
0,
0
],
"wctemp": 359,
"cctemp": 361,
"warning_temp_time": 0,
"critical_temp_time": 0
} |
smartctlr show the disk and their properties (for example, --info)
The text was updated successfully, but these errors were encountered: