Juststart it via you start menu, press the Start menu button and type gsmartcontrol.
sudo gsmartcontrol reports that in cannot open a display because the DISPLAY environment variable from your bash session is not passed to the sudo root session.
Limit to suite:[buster][buster-updates][buster-backports][bullseye][bullseye-updates][bullseye-backports][bookworm][bookworm-updates][bookworm-backports][trixie][sid][experimental]Limit to a architecture: [alpha] [amd64] [arm] [arm64] [armel] [armhf] [avr32] [hppa] [hurd-i386] [i386] [ia64] [kfreebsd-amd64] [kfreebsd-i386] [m68k] [mips] [mips64el] [mipsel] [powerpc] [powerpcspe] [ppc64] [ppc64el] [riscv64] [s390] [s390x] [sh4] [sparc] [sparc64] [x32] You have searched for packages that names contain gsmartcontrol in all suites, all sections, and all architectures.Found 2 matching packages.
In other distributions (names redacted to protect the guilty) the S.M.A.R.T tools are included in so-called recovery images. Most of the tools useful to deal with hard disk problems are already in the TryUbuntu image. Missing are the S.M.A.R.T tools "smartctl" and "gsmartcontrol".
During a troubleshooting session, I was able to copy smartctl(8) to a thumb drive formatted for EXT4, and was able to execute it to find my problem. I know this is not everyone's cup of tea, and most of the time one doesn't need it...until one does. Particularly if one can't boot one's system.
Hey guys, I bought myself a new Samsung Evo 970 Plus NVMe SSD today. Installation of Solus went fine and performance is good.
The thin which bothers me is, the device is not properly recognised by the system, as hdparm does not list it at all and GSmartControl only lists it as "unknown device". As result of this, I can not read smart parameters and my options in setting device parameters is limited.
I don't think it is a hardware issue though, as UEFI and Windows do recognize it correctly. Could this be related to SSD firmware or some Solus related stuff? There are some topics on Solus and NVMe SSDs in this forum, but none is targeted at the same issue. Has anyone had similar experiences and Ideas how to get Solus to recognize the SSD correctly?
Same issue here - gsmartcontrol lists it as unknown even though hdparm -x does show the data.
I'm running gsmartcontrol 1.1.3 (which is latest), and updated the device DB today - but it's not in there, that may be the issue.
SCSI/SAS and NVMe drives do not provide ATA/SATA-like SMART Attributes. Therefore the drive database does not contain any entries for these drives. This may change in the future as some drives provide similar info via vendor specific commands (see ticket #870).
I have the same problem on my machine. I have 64bit archlinux, and I had updated it just now. smartctl from console works fine, but the gsmartcontrol crashes 1-2 sec after starting. This is the output of my console:
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Search in specific suite:[focal][focal-updates][focal-backports][jammy][jammy-updates][jammy-backports][mantic][mantic-updates][mantic-backports][noble][noble-updates][noble-backports][oracular]Limit search to a specific architecture: [i386] [amd64] [powerpc] [arm64] [armhf] [ppc64el] [riscv64] [s390x] You have searched for packages that names contain gsmartcontrol in all suites, all sections, and all architectures.Found 1 matching packages.
3a8082e126