It is running much better though.
Of course, I like the sound of that!
But read failure errors are still a concern.... it's hard to put faith and trust in it, although you might use it for many months and not really experience any problems.
Wizard will be up soon having his morning "cuppa" and I'd like to have his thoughts on another step to take below. GSmartControl and
badblocks do not "mark" bad blocks, from what I can find online. There is another command,
e2fsck, that will run
badblocks and then try to mark those blocks as bad. From what I can read, modern hard drives should be doing this automatically and using a built-in store of good spare blocks as replacements... but if it has already used all the good spares (which we do not know), then this step may "mark" the bad blocks you have and keep them from further use. If new bad blocks continue to develop, well, the game will be over at some point I'm afraid, and probably sooner rather than later. (Sometimes I am just too darn pessimistic! Sorry!)
Okay, the
e2fsck command cannot be run on a mounted drive, so you will have to boot on your USB to do this, if Wizard concurs with this idea (and that I have the proper code below). After the process is finished (and it might take a long while)... then you can reboot back to the hard drive and we'll try the GSmartControl short and long tests again. The command to run (from the Live USB) is:
Code:
sudo su # do this first to get root
e2fsck -c /dev/sda1
Of course, please write down any reports that the test may generate if they aren't too long. I've never done this so I don't really know what to expect. There is a slightly different version that is a read-write test, but I'm a bit too gun shy about that so as not to damage any data that you have on the drive now. The above command is just a read test and will mark the bad blocks that it finds that way.
I'll be in and out, off and on... going to work night shift tonight. The fun never stops!
Cheers