https://bugs.kde.org/show_bug.cgi?id=429331
--- Comment #7 from Luiz Angelo De Luca <luizl...@gmail.com> --- (In reply to Harald Sitter from comment #6) > Whoops. Hit save too soon. You could have smartd send notifications to > journal and then pick them out via trivial scripting. If the user can script that, plasma-disk is just an additional feature. I was thinking about those users that does not know how to do that (and does not even know S.M.A.R.T. exists. If plasma has a tool that reads smart data, it would not make sense to have a new tool to do just the same, but better. A repeated error at the same position would tell the user that if there is info info stored there, it is gone as CRC is not matching. Is it a HW failure? Maybe not. It could be generated by a power outage, and external interference scrambling bits, firmware bug... who knows? As an advanced user, I would look for badblocks, fsck the filesystem or ever recreate the FS. It would be nice if the read error message could identify the affected filepath, offer to run check tools (fsck, badblocks, ....), suggest a backup... plasma-disks is a nice feature for a cli user but it will be the only monitor tool for non-cli plasma users. In my case, I zero-filled the disk and now it is working as usual. However, I don't trust that HDD anymore to store anything important. My filesystem got irrecoverably corrupted and I did a backup and recreated the FS. -- You are receiving this mail because: You are watching all bug changes.
