My root partition seems to be getting corrupted often. It's the second time this week. I would like to see the S.M.A.R.T. stats for the whole drive, but I am able to do it only for all the non-root disks (whilst using the Disks Utility).
How can I do a S.M.A.R.T. check on the whole drive?
Asked
Active
Viewed 362 times
1

jeyko
- 111
1 Answers
0
You should be able to see the result of the most recent self-test through the gnome disks utility (run sudo gnome-disks
from the CLI). To run a new test on the root disk, you'll need to run the test from a live USB.

Minty
- 1,208
-
This was my method of inspection already, prior to your suggestion (gnome-disk without sudo). The S.M.A.R.T. option is greyed out for the root partition though. Is that normal? It is a USB HDD. – jeyko Mar 17 '19 at 17:32
-
@jeyko, It works for me (without
sudo
). I tested right now from my USB SSD with Lubuntu 18.04 (installed system). But if you want to run a program with a graphical user interface, you should usesudo -H GUI-program
, because plainsudo
might damage your user's configuration files. -- See also this link – sudodus Mar 17 '19 at 18:08 -
It is greyed out for me on Ubuntu 18.10 (system-disk external SSD). In the end I used a Live USB to do a SMART inspection and the outcome is that the disk is damaged.
Maybe edit the answer about ``sudo GUI``` so people don't damage their configs? I am not able to run the command.
– jeyko Mar 19 '19 at 08:28 -
An external SSD might not be SMART enabled in the first place; it's uncommon for internal drives not to have it but external drives might not conform to that standard. Check the manufacturer's website/FAQ – Minty Mar 19 '19 at 10:23
fsck
to fix my hdd - Ubuntu made me do it last time. It seems to be corrupted also currently, but I am still running it. On next restart, I am sure it will force fsck again, because my Chrome user files are already broken. There are a bunch of broken sectors.This is an issue unrelated to the question. I would like to see the SMART data from within Ubuntu to learn whether this is a software or a hardware issue. – jeyko Mar 17 '19 at 17:52
fsck
results logged at boot time, after/forcefsck
? – Pablo Bianchi Feb 03 '24 at 03:14