Hello everyone,
I wanted to share my observation while using my Plasma installation, I've read some forums and I've noticed it isn't Solus problem, at best it could just be KDE problem.
Here is a picture I took what happens but not always only sometimes like 2/5 logins I get this notification at the startup after I login :
Nothing really happens I can use my system as normal, just wanted to hear a thought about all this.
Cheers !
I never saw something like this to be fair
Could be the drive is starting to fail and Plasma is indicating it's having trouble reading parts of it. Check SMART data, do a check on it, etc.
Justin I'll check it out using smartctl ?Never done this, tho I had a feeling the disk would start failing pretty soon.
When it was bought 7 years ago it had 500 Gb storage , now over this past years of using it I can only see 465GB available.
Edit: Command used sudo smartctl --all /dev/sda2 should this output be enough? I didn't want to post everything , but juding by this my HDD is still fine.
SMART overall-health self-assessment test result: PASSED
Justin WetGeek Both your responses are different sides of the same coin--sectors don't populate---if any of my smartypants verbiage is correct--I don't know. . I found out when it happened to me recently; by that I mean the signs.
laky --but you could be right with the smartctl, but I wonder if SMART in gnome-disks tells a different story. and even if it did tell a different story I wouldn't know what to believe. A random sample (different benchmark testing apps) of a specific thing (hdd) done 3 ways usually helps me from an opinion. When it comes to opening my wallet I require a consensus
brent You can trust smartctl. It reads directly from your disk. The whole point of SMART is to provide a uniform interface for HDD/SSDs to report their health. If SMART is reporting that your drive has problems, it's your drive telling you it thinks it has a problem and you should probably listen.
If the drive has all PASSES then that's good, maybe try boot the Solus live ISO and run fsck on the installed partition.
Ok, I must confess regarding my previous post laky
Just installed new nvme drive with 500gb storage it is reporting as 465gb in lsblk .
But I've read on some forums that it is normal thing because of "over-provisioning" which ssd's are assigned.
Meaning in short speech that bad cells are replaced with the good ones. (I had no idea my HDD had that kind of thing, could swear I saw full 500gb while using Win7 back in the day) 
laky Well it's also a unit conversion thing. Gigabyte (GB) is an SI Unit and thus is a multiple of a power of 10. Gibibyte is the unit most of us think of, which is a multiple of a power of 2. HDD and SDD manufacturers typically report the drive capacity in GB or TB because it's a larger number. In your case, some of the difference in capacity will also be the over-provisioning, the rest is lsblk reporting GiB not GB.
So here they are