diskmonitor
diskmonitor copied to clipboard
papylhomme
nvme disk show as unknown
smartctlr show the disk and their properties (for example, --info)
└───╼ sudo smartctl --info /dev/nvme0n1
smartctl 7.0 2018-12-30 r4883 [x86_64-linux-5.2.0-arch2-1-ARCH] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Samsung SSD 960 EVO 500GB
Serial Number: S3EUNB0J557245E
Firmware Version: 2B7QCXE7
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Total NVM Capacity: 500.107.862.016 [500 GB]
Unallocated NVM Capacity: 0
Controller ID: 2
Number of Namespaces: 1
Namespace 1 Size/Capacity: 500.107.862.016 [500 GB]
Namespace 1 Utilization: 424.896.667.648 [424 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 002538 5571b2a498
Local Time is: Fri Aug 16 14:29:15 2019 CEST
Can you check if UDisks export the SMART attributes using a dbus client like qdbusviewer ? See https://github.com/papylhomme/diskmonitor/issues/19#issuecomment-480586071 for details on how to do that.
Looking more in debt into udisks I found the following issues that seem related: https://github.com/storaged-project/udisks/issues/433 and https://github.com/storaged-project/udisks/issues/649
Same problem here:
`sudo smartctl --info /dev/nvme0n1 [sudo] password for root: smartctl 7.0 2019-05-21 r4917 [x86_64-linux-5.3.18-lp152.33-default] (SUSE RPM) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION === Model Number: Samsung SSD 970 PRO 1TB Serial Number: S462NF0MA07665A Firmware Version: 1B2QEXP7 PCI Vendor/Subsystem ID: 0x144d IEEE OUI Identifier: 0x002538 Total NVM Capacity: 1,024,209,543,168 [1.02 TB] Unallocated NVM Capacity: 0 Controller ID: 4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 1,024,209,543,168 [1.02 TB] Namespace 1 Utilization: 469,198,090,240 [469 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 002538 5a91b2f807 Local Time is: Tue Aug 18 15:50:10 2020 CEST `
`cat /etc/os-release NAME=openSUSE Leap VERSION=15.2 ID=opensuse-leap ID_LIKE=suse opensuse VERSION_ID=15.2 PRETTY_NAME=openSUSE Leap 15.2 ANSI_COLOR=0;32 CPE_NAME=cpe:/o:opensuse:leap:15.2 BUG_REPORT_URL=https://bugs.opensuse.org HOME_URL=https://www.opensuse.org/
uname -a Linux 5.3.18-lp152.33-default #1 SMP Wed Jul 22 06:32:33 UTC 2020 (e5a8383) x86_64 x86_64 x86_64 GNU/Linux `
I am experiencing this issue as well in DisKMonitor 0.3.4...
- KDE Frameworks 5.84.0
- Qt 5.15.2 (built against 5.15.2)
- The xcb windowing system
$ sudo smartctl --info /dev/nvme0n1
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.5-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: WDS100T1X0E-00AFY0
Serial Number: ########################
Firmware Version: 613200WD
PCI Vendor/Subsystem ID: 0x15b7
IEEE OUI Identifier: 0x001b44
Total NVM Capacity: 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity: 0
Controller ID: 8224
NVMe Version: 1.4
Number of Namespaces: 1
Namespace 1 Size/Capacity: 1,000,204,886,016 [1.00 TB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 001b44 8b49390a73
Local Time is: Thu Aug 5 10:25:57 2021 CDT
$ sudo smartctl --info /dev/nvme1n1
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.13.5-1-MANJARO] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: WDS100T3X0C-00SJG0
Serial Number: ########################
Firmware Version: 102000WD
PCI Vendor/Subsystem ID: 0x15b7
IEEE OUI Identifier: 0x001b44
Total NVM Capacity: 1,000,204,886,016 [1.00 TB]
Unallocated NVM Capacity: 0
Controller ID: 8215
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 1,000,204,886,016 [1.00 TB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 001b44 8b4472fa2a
Local Time is: Thu Aug 5 10:26:39 2021 CDT
Operating System: Manjaro Linux
- KDE Plasma Version: 5.22.4
- KDE Frameworks Version: 5.84.0
- Qt Version: 5.15.2
- Kernel Version: 5.13.5-1-MANJARO (64-bit)
- Graphics Platform: X11
$ cat /etc/os-release
NAME="Manjaro Linux"
ID=manjaro
ID_LIKE=arch
BUILD_ID=rolling
PRETTY_NAME="Manjaro Linux"
ANSI_COLOR="32;1;24;144;200"
HOME_URL="https://manjaro.org/"
DOCUMENTATION_URL="https://wiki.manjaro.org/"
SUPPORT_URL="https://manjaro.org/"
BUG_REPORT_URL="https://bugs.manjaro.org/"
LOGO=manjarolinux
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) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: CT500P5PSSD8 Serial Number: 213731731B64 Firmware Version: P7CR402 PCI Vendor/Subsystem ID: 0xc0a9 IEEE OUI Identifier: 0x00a075 Total NVM Capacity: 500 107 862 016 [500 GB] Unallocated NVM Capacity: 0 Controller ID: 0 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 500 107 862 016 [500 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 00a075 0131731b64 Local Time is: Sun May 1 02:14:13 2022 MSK
Operating System: Manjaro Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.32-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × AMD Ryzen 3 PRO 2200G with Radeon Vega Graphics Memory: 13.6 ГиБ of RAM Graphics Processor: AMD Radeon Vega 8 Graphics
This issue is still blocked upstream by udisk but things might move on their side eventually : the related issue receveid an interesting update yesterday https://github.com/storaged-project/udisks/issues/386#issuecomment-1114116777
Seems to been have fixed some time ago (https://github.com/storaged-project/udisks/pull/975).
seems the udisk issue is fixed (libnvme is released with things fixed) . needs do something here?
greetings
Yes indeed, shipped with udisks2-2.10 (https://github.com/storaged-project/udisks/issues/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
https://github.com/storaged-project/udisks/issues/1063 https://github.com/storaged-project/libblockdev/pull/835 https://github.com/storaged-project/udisks/pull/1179
I faced the same problem:
DisKMonitor
Version 0.3.4
KDE Frameworks 5.68.0,
Qt 5.12.8,
Windows system xcb.
sudo smartctl --info /dev/nvme0n1
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.15.0-86-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: Micron MTFDHBA512TDV
Serial Number: 21032CA5C26D
Firmware Version: 3010P4LN
PCI Vendor/Subsystem ID: 0x1344
IEEE OUI Identifier: 0x00a075
Controller ID: 0
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512 110 190 592 [512 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 00a075 012ca5c26d
Local Time is: Fri Oct 20 09:02:00 2023 +06
Linux ThinkPad-P14s 5.15.0-86-generic #96~20.04.1-Ubuntu SMP Thu Sep 21 13:23:37 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Is there any solution to this problem?
