Disk Boot Failure....

Users who are viewing this thread

Guyzerr

Banned
Messages
12,928
Reaction score
0
Tokenz
0.00z
Guy, unless you heaved real hard on the cable I doubt that was the issue.. But hey anything is possible..

The reason I suspect the cable is because of the problem being intermittent and it happened on both the HD's I had in it. If it were a bad HD I doubt the problem would be duplicated in a brand new one.

I would suspect if anything the problem will reappear in a day or a few days if its what I think it might be.. Then you have issues that need hard drive software to find and see if the drive is still good or can be fixed..

You could and probably are right. Time will tell.

You still have not said what brand it is so can help further.. Some drives have more issues then others. Example Seagates are known for bad sectors, as for Western Digitals were bad in some series for controllers and just dieing.. Fujitsu had their issues as well..

Sorry about that Francis... The bad / original HD is a 40 gig Samsung. It was a killer when I built the system about 6 or 7 years ago. :24: ( I gave this system to my sister when I built my current one 4 years ago cuz I'm such a nice brother )

I know about the Western Digitals going bad. I've had a couple fail on me over the years.
 
  • 25
    Replies
  • 1K
    Views
  • 0
    Participant count
    Participants list

Francis

Sarcasm is me :)
Messages
8,367
Reaction score
1
Tokenz
2.08z
The reason I suspect the cable is because of the problem being intermittent and it happened on both the HD's I had in it. If it were a bad HD I doubt the problem would be duplicated in a brand new one.



You could and probably are right. Time will tell.



Sorry about that Francis... The bad / original HD is a 40 gig Samsung. It was a killer when I built the system about 6 or 7 years ago. :24: ( I gave this system to my sister when I built my current one 4 years ago cuz I'm such a nice brother )

I know about the Western Digitals going bad. I've had a couple fail on me over the years.

OK This is a bit more clear..

First I thought, by wording, it was the same drive causing the error.. :p

Not different drives..

If you want to find out if a cable is bad real fast, connect it to a CD ROM.. :D

What has happened to me, in the past, was putting the cable back in, some older IDE cables had a pin blocked off while others did not. I had not noticed this on the one I was putting it and it was cheap and had no guides to ensure only one way to push in.. So I crushed the pun inside the socket at the motherboard side.. Look to make side pins are no pushed out on either the Hard drive or in the socket in the motherboard.. :)
 

Guyzerr

Banned
Messages
12,928
Reaction score
0
Tokenz
0.00z
OK This is a bit more clear..

First I thought, by wording, it was the same drive causing the error.. :p

Not different drives..

If you want to find out if a cable is bad real fast, connect it to a CD ROM.. :D

What has happened to me, in the past, was putting the cable back in, some older IDE cables had a pin blocked off while others did not. I had not noticed this on the one I was putting it and it was cheap and had no guides to ensure only one way to push in.. So I crushed the pun inside the socket at the motherboard side.. Look to make side pins are no pushed out on either the Hard drive or in the socket in the motherboard.. :)
The pins were all ok from what I could see. You gotta remember that system with the original HD has been running fine for the last 6 or 7 years. A pin can't bend all by it's lonesome. They have the tower on a small cart beside the desk and it's possible my niece ( the user ) kicked it by accident or something. If she did she might have jarred something loose. I really don't know. It's all guesswork at this stage of the game.

So Francis.................. you got any software to analyze a Samsung HD? You forgot to tell me. :24:
 
78,874Threads
2,185,387Messages
4,959Members
Back
Top