| Summary: | encrypted drives are not checked for SMART data | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | zxvb12z <zxvb12z> |
| Component: | Disk failure/S.M.A.R.T. notification | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | nate, sitter |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
screenshot
command output sudo smartctl --all /dev/sdd QT_LOGGING_RULES="org.kde.plasma.disks=true" kded6 --replace Maybe it will be clearer |
||
What's the output of solid-hardware6 list details Created attachment 178260 [details]
command output
All disks found. I will add a file with the command output, I have removed everything that does not relate to disks and replaced some fields like name and uuid with "don’t say"
And what's the output of sudo smartctl --all /dev/sdd Created attachment 178282 [details]
sudo smartctl --all /dev/sdd
Fun. What's the output of QT_LOGGING_RULES="org.kde.plasma.disks=true" kded6 --replace (you may wish to logout and back in again after running that since it screws with your session a bit) Created attachment 178292 [details]
QT_LOGGING_RULES="org.kde.plasma.disks=true" kded6 --replace
"bad type Solid::StorageVolume::FileSystem" Probably in this message he complains about Luks I guess that explains it then. Because the entire drive is encrypted it fails an assumption about the type and gets skipped. Not sure what the best solution here is, but I guess we need to combine data from storagevolumes and block devices to find all possible devices reliably. (In reply to Harald Sitter from comment #8) > I guess that explains it then. Because the entire drive is encrypted it > fails an assumption about the type and gets skipped. > > Not sure what the best solution here is, but I guess we need to combine data > from storagevolumes and block devices to find all possible devices reliably. I’m not sure that’s the reason, because all my drives use luks. (In reply to orangeanatola from comment #9) > I’m not sure that’s the reason, because all my drives use luks. Not according to the output in comment 2 Created attachment 178308 [details]
Maybe it will be clearer
Difference I see that the first 3 disks are divided into several luks sections with with a file system inside. At the same time TOSHIBA drive consists of one luks partition fully covering disk, with file system inside. |
Created attachment 178228 [details] screenshot SUMMARY My computer has 4 hard drives: 2 Seagate BarraCuda 3.5 (ST1000DM010-2EP102), Seagate Barracuda 7200 (ST1000DM003-9YN162), TOSHIBA DT02ACA200 (X3K2S5Y8SBEJ). All 4 disks are fine and displayed without problems in gsmartcontrol and smartctl. But the kinfocenter shows smart status only for the first 3 disks and does not report status for TOSHIBA DT02ACA200 disk. STEPS TO REPRODUCE 1. start kinfocenter 2. select smart status 3. See that the number of disks is less than should be OBSERVED RESULT kinfocenter shows smart status not for all hard drives EXPECTED RESULT kinfocenter shows the state of the smart for all hard drives SOFTWARE/OS VERSIONS Linux: Manjaro 25.0 KDE Plasma Version: 6.3, wayland KDE Frameworks Version: 6.10 Qt Version: 6.8.2 Nvidia video driver: 570.86.16 witch close kernel module ADDITIONAL INFORMATION