Seagate ST2000DM002 failed SeaTools test

[theorange]

Hey guys, I was running a long test on a drive that installing windows would not work on. I had a long test running for 30 minutes and 10 seconds when I get an error code: E0A4CD50

Also in the test info box, it says "Long test timed out!"

I'm not sure if that's a drive failure or I just messed up the test or something, though, because "timed out" doesn't really sound like a failure. The thing is, there is no explanation for this error code at all, on seagates error code page, it doesn't even list the code.

I actually tried installing windows on an ST500DM001 as well, it failed on that one as well, I have yet to long test it, but I find it unlikely that I was shipped two brand new DOAs. The fact that the windows installation failed on that drive as well, I am led to believe that this is not the problem.

 

[noidea_77]

Try with an other sata cable and on a different port.

 

[theorange]

Thanks for the help. I think I might run HDTune as well, and if that picks up an error too, then I'll try changing the ports.

 

[noidea_77]

Thanks for the help. I think I might run HDTune as well, and if that picks up an error too, then I'll try changing the ports.

Changing the port is a 10 second thing, no?

 

[theorange]

Yes, I suppose you are right, but I really hate facing the fact that I have a possible hardware failure instead of a software failure.

I just ran a long test on the 500gb as well, I got the same time out error as before, with the code E8ADDF58. I am now starting to face the fact that I was possibly shipped two bricks...

I'll run some more tests on them then see if switches around ports works.

Here is the thread in which I describe my problems installing windows, if that matters.

 

[noidea_77]

Yes, I suppose you are right, but I really hate facing the fact that I have a possible hardware failure instead of a software failure.

I just ran a long test on the 500gb as well, I got the same time out error as before, with the code E8ADDF58. I am now starting to face the fact that I was possibly shipped two bricks...

I'll run some more tests on them then see if switches around ports works.

Here is the thread in which I describe my problems installing windows, if that matters.

I don't think E0A4CD50 is an error code. It looks more like the memory address, where the process died. That would lead to a RAM problem instead of a disk problem.

 

[theorange]

Hmm, that's funny. I just tried installing windows on a blank 64gb ssd in the computer as well, and sure enough, the error didn't pop up anymore! I did end up with another error, "Windows could not prepare the computer to boot into the next phase of installation. To install Windows, restart the installation." but at least I fixed the first one.

I did run memtest86+ for only 2 passes yesterday because I was a bit short of time, but there were no errors from a quick test. I'll run it more thoroughly right now and see if I get an error.

Also, I just went and rechecked the error message and I now realize that I don't think that's an error code, it's some identifier unique to me. It says: "Your Seagate test code."

 

[noidea_77]

Hmm, that's funny. I just tried installing windows on a blank 64gb ssd in the computer as well, and sure enough, the error didn't pop up anymore! I did end up with another error, "Windows could not prepare the computer to boot into the next phase of installation. To install Windows, restart the installation." but at least I fixed the first one.

I did run memtest86+ for only 2 passes yesterday because I was a bit short of time, but there were no errors from a quick test. I'll run it more thoroughly right now and see if I get an error.

Different error message, same root cause - for sure.

 

[theorange]

What makes you say that? I haven't run any tests on the ssd yet.

 

[theorange]

Oh, I'm an idiot! I just remembered that I had unpacked the windows 8 iso onto the usb using rufus in an attempt to see if that fixed the problem, that might be why I'm getting that new error! I'll try creating a bootable usb straight from the upgrade assistant.

 

[noidea_77]

What makes you say that? I haven't run any tests on the ssd yet.

Because it has nothing to do with the disk, it's either a RAM error or a sata cable / port problem.

 

[theorange]

Nope, using the upgrade assistant to create the usb didn't help at all. I guess I'll try switching around the ports, and if that doesn't work, I'll run memtest.

What I don't get is why it would display a different error on the ssd than on the hd.

 

[theorange]

Just a quick question, my board (Asus z97-pro) has 4 sata III ports and a sata express, which you can plug two sata III cables into. I currently have nothing plugged into the sata express ports, and I have my st2000 in regular sataIII 1, the ssd in 2, and the st500 in 3. Do you think it would help to plug the st2000 and the ssd (my two main drives, the 500 was just for storage) into the sata express ports? I at first decided to just use the regular sata ports to avoid compatibility problems, but I guess I'm running into them now.

 

[theorange]

Well, I just switched around the cables, the install still failed. I guess I'll just run memtest for a couple hours now. I'll report back once I'm done with that.

 

[theorange]

It's been an hour and memtest86 hasn't even finished one pass yet, that's quite strange. It's been stuck on test 8 for at least the last 50 minutes... Usually it only takes 15 minutes for one pass, as I only have 8gb ram. I think I might just restart memtest.

 

[theorange]

So I've had memtest86+ running for more than 4 hours now, and it hasn't seemed to pick up any errors. I guess that rules out the memory then.

I'm now starting to believe it may be a usb problem, so I'm going to go and get a cheap external cd drive tomorrow and see if that fixes it.