I did this, but it wasn't giving interface errors, it was giving system faults. I shot the Scannerz people an e-mail for help and they told me to create a Phoenix volume, which is their version of an emergency boot drive and do interface tests on the internal drive to see if it was the cable and then send them the logs. This time I got a copy of Scannerz and started running tests on the drive and about 3 minutes into the test it goes ballistic reporting errors. I don't have anything against SSDs, I just don't think that kind of advice at that point was very good. Then came the barrage of "replace it with an SSD," which fortunately I didn't do.
I wish I had listened to him at that time because like an idiot I ordered a new drive cable and no change was detected after I installed it. At this point, one guy chimed in and suggested I run system tests on it with a product named Scannerz because it could detect weird problems and if I didn't isolate the problem I could end up just throwing money at a it. Then people started telling me to replace the drive cable because that was the problem. I went to another web site and everybody kept telling me to replace the HDD because that was the problem. The system wouldn't fail, it would just delay, sometimes for what seemed like a minute, then come back to life. Before I do, I'd like to get some input from this site's users.Ībout a year ago I started getting weird lockups. The logic board in my 2010 MacBook Pro has failed and I need to replace it.