Well, folks @FranciscoD, @t0xic0der, @wylbur, @simmon, @boricua, @vits95,
This topic became a multi-faceted issue which is demanding a lot of patience, study and intuition.
This is the thing.
Two machines, both with Athlon 64 X2 AMD processor and 8 GB DDR2 RAM
ASRock AM2-NFG6 VSTA mobo and 1.5 TB Barracuda Seagate SATAII HDD.
ASUS M2A-VM HDMI mobo and 2 TB Barracuda Seagate SATAII HDD.
ASRock presented some disk failure some years ago.
Two months ago I started revitalizing it.
So, I got a 1 TB 7200 rpm Barracuda Seagate disk, installed it and setup Fedora 32.
To my surprise, the new disk failed.
Claimed guarantee and got a replacement.
Meanwhile, ASUS was presenting the uncertain halts.
Thanks to your advises I was able to install NVIDIA drivers and solved the stallings.
So, then I gave it a try to the 1.5 TB disk and run a write-to-zero process and badblocks reported 0 errors.
Put it on ASRock.
I then installed Fedora 32 on it and was able to install the Nvidia drivers.
The computer worked fine…
until last Monday.
ASRock started a constant single beep.
Replaced 1.5 TB with new 1 TB disk.
And did all the setup process again.
To my surprise I was not able to finish properly.
Once Fedora 32 started I was not able to go install the NVIDIA drivers on newly setup ASRock.
HDD started a very slight click.
I am connected it to ASUS and am currently running badblocks.
At 80% is shows just 32 errors.
Meanwhile I tested ASRock PSU.
Yellow cables show a 11.3 V output.
A new Thermaltake PSU I have as backup shows 12.7 V output.
¿Can the PSU be causing the HDD’s errors?
I now will put the 1 TB disk to a low level write-to-zeroes format.