Filesystem corruption

[Ralf Mardorf]

On Tue, 25 Jun 2019 21:07:06 +0200, Volker Wysk wrote:
>I guess, I don't have to run the SMART daemon, do I?

On Ubuntu installing the package smartmontools automatically enables
smartd. Running

  systemctl status smartd.service

does show the status. On Linux distros that automatically enable
smartd, I disable it manually. However, to use smartctl, there is no
need to run smartd.

In addition to what compdoc already mentioned, even if all attributes
should be ok, the HDD could be broken. The systemctl output for the
attributes for almost all HDDs that failed in my machines was ok.

I can't comment on your corrupted files. In my experiences, if a HDD is
broken, you hear unexpected noises and/or performance, not only HDD
performance, but als GUI performance slows down rapidly.

I'm seldom using GUI file managers, usually I'm using command line.
Fish HDDs tend to cause input/output errors. At the beginning they
happen very seldom and in the end they always happen.

I don't know if this applies to SSDs, too. For the integrated drives I
completely migrated from HDDs to SSDs, but I don't have experience with
dying SSDs yet. At least I doubt that SSDs will make strange noises.