I'm curious, Rich. What you find out when you pulled the drive out?
Actually I wrote one of my longest posts yesterday detailing what happened, then unintentionally lost it. Got disgusted with myself and gave up.
But, today's another day and I'll give it a shot. I got the EURS Thursday and took the two year old (Amazon can show you every purchase you made, in detail, for many years) EVDS out of the 24-500 and put the EURS in its place. Haven't had any problems with the 24-500 since. So, the easiest part went well.
Prior to getting the EURS, TheRatPatrol
sent me a PM telling me that he had a similar problem and VOS
had suggested he try running the Surface Scan utility. I've ignored the diagnostics and was gonna do the same thing again, just toss the HDD and use the new EURS, but then I thought if it worked for him...
So, I entered the diagnostic pages after installing the "bad" EVDS in a TT docking station on my old, weary 21-200. Now that was a trial. I used a new spare TT docking station and set it up as I always do. Boot up and get a blue screen that tells me my HDD is shot. Sit there looking at that screen and wondering why the 24-500 didn't show the same screen. That made no sense, so I shut the 200 and docking station down and put a small level on top of the HDD. Not level, the table and docking station showed level, but the HDD was not level. I took the HDD out of the TT and reinserted it with a slight smack on the top of the HDD to make sure it was seated properly. Now the HDD was level.
Now, I'm sure the 200 will recognize the HDD, so I boot up and get the same message. This is why I don't have guns in the house. Two Advils and a tranquilizer later, I calm down and go back to troubleshooting. Still troubled by the fact that the 24-500 wouldn't show the same screen as my 21-200 keeps showing me. Makes no sense.
Took an EARS that I knew was good an put it in the docking station and booted the TT and the 21-200 up...same screen comes up. I know the EARS is good. Only one thing left, something I've never had happen before. Could it be a bad eSATA to eSATA jumper cable? I've said many times I've never had a bad jumper cable. Replaced the cable that came with the dock with an old Cavalry jumper cable and the damn thing worked after booting up.
Let me apologize to all the good folks that I've derided about "bad" jumper cables over the years. I finally got one that wouldn't work. My next step would have been to take my sledgehammer to the EVDS and be done with it.
Took a few minutes to figure out how to use the diagnostics and ran the test. No results. Other than no problems found. So I ran the long Smart scan. I guess you don't get told what happens or what problems are found on either scan. But, the EVDS is working now and working well. No massive pixellations as I was seeing when it was in the 24-500, so I have to assume that the scans actually worked. I've watched several Yankee games since, and no problems at all.
My thanx to TheRatPatrol
for recognizing the problem and telling me how he fixed his problems with the scans and to VOS
for his suggestions to him.
I gotta admit I still don't know "why" all this happened or "what" the scans did, but it worked and that's really all I need to know.
Now, I gotta try that "bad" jumper cable on another HR with a dock and see if it works on that. Betcha it will.....:lol:
I really dislike long posts such as this one. I usually ignore them. I've tried to make this one readable. I think there's something to be learned from this experience. I know I learned quite a bit