Filesystem corruption

[Ralf Mardorf]

On Wed, 26 Jun 2019 10:09:11 +0200, Volker Wysk wrote:
>You mean "Fishy"?

Hi,

yes, I'm typing with two fingers, but faster than the Flash could run,
too fast for the keyboard.

>My HDD is 3,5 years old. The SSD is 1,5 years old. This doesn't sound
>very old, does it?

You never know, anything can happen, or as you and I say in German,
man hat schon Pferde vor der Apotheke kotzen gesehen.

>Now i'm wondering if I should buy a new hard disk, before I reinstall
>Ubuntu...

3 ½ years could be a long time for a HDD, if it often needed to spin
down and spin up. IOW if the machine is running 24/7, then 3½ years
isn't old. If you shut down/power off and start up the machine several
times a day or the HDD goes asleep and you or for example the evil gvfs
of your GNOME install (or KDE's equivalent) wakes up the drive several
times a day, than the drive could be old, already after ½ year or
earlier.

>And I wonder if my backup is corrupted too. Probably...

You are probably using a bad backup strategy. You should be able to
restore from different old backups. The files from the latest backups
are most likely corrupted, too, but a backup from 4 weeks ago might be
ok.

On Wed, 26 Jun 2019 08:52:22 +0200, Volker Wysk wrote:
>This is for /dev/sdb, which is an SSD

Your SSD is not in the smartctl data base. The SSDs I'm using are also
not in its data base. The vendor of my SSDs provides proprietary,
but free as in beer Linux software.

If I run

  sudo ocz-ssd-utility

or gksudo..., I can access smart data, update the firmware while the
SSDs are used etc., for Arch Linux I'm using a PKGBUILD from the AUR,
https://aur.archlinux.org/packages/ocz-ssd-utility/. If you take a look
at the PKGBUILD, it's just a script, you can see the source,
https://ssd.toshiba-memory.com/download/software/ssd-utility/${pkgver}/SSDUtility_${pkgver}_Linux.zip
replace "${pkgver}" with "2.3.2963", IOW use
https://ssd.toshiba-memory.com/download/software/ssd-utility/2.3.2963/SSDUtility_2.3.2963_Linux.zip
assuming you should have an OCZ SSD.

The raw value for the Current_Pending_Sector attribute of your HDD
should be 0.

For the SSD all smart "functunality" related values should be 0, resp.
my SSDs show idiotic unexpected power loss count values and I ignore
those values, but the bad block count etc. values are 0 and should be 0
for your SSD, too.

On what drive are the corrupted files?
Are you using SATA cables with or without clips?
I don't know if you should purchase a new drive, but it doesn't harm to
reconnect the SATA and power cables and to replace SATA cables without
clips by those with clips.

Regards,
Ralf