boot disk failure - very strange

twitchee2

Platinum Member
Dec 29, 2004
2,135
0
0
So I walked in me room and my computer has rebooted with a boot disk failure. I'm going great now what is it. I had just installed 2gb of OCZ ram so I thought that might be the problem, so I took it out and re installed my patriot ram which I know has no problems. No go. So next I got my windows CD thinking there might be a problem with windows so I attempted to do a repair install it didnt do anything. So I unplugged my just back from RMA seagate drive, and what do you know boots up perfectly. So I am completly stumped on how to fix this so that I can use my drive still. If anyone has some sugestions that would be great. Thanks for all your help.


Edit - It gets better. I just plugged the seagate back in and all is going just fine. hmmm any ideas what is going on?
 

billsbury

Member
Dec 27, 2005
46
0
0
Let me try to understand the problem a little better. You left the room while your machine was in Windows, came back, and it had already kicked out of Windows indicating a boot disk failure?

And when you said 'no go,' does that mean it gave the same error or you got the bsod or it didn't boot at all?
 

twitchee2

Platinum Member
Dec 29, 2004
2,135
0
0
yes I left for literally 5 mins, come back it has already re-booted and says "boot disk failure, insert boot disc and press enter"
 

ta8689

Golden Member
Feb 5, 2006
1,116
0
0
No way dude, same problem. It will be fine. I have a hitachi deskstar 160 sata. The plug just came loose. Then boot disk failure cause it wont read the drive properly. As long as it doesnt happen often, dont worry. You probably knocked it loose when you were working in it.
 

JimPhelpsMI

Golden Member
Oct 8, 2004
1,261
0
0
Hi, Just proves that electronics is capable of 1,000,000 errors per milisecond. Jim

Seriously, that could be an indication that your hard drive has bearing or head problems and is having trouble spinning up. I always told my Service Guys that if something happend once just forget it. If it happened again think about it awhile and then forget it. Next time get busy and fix it. Good Luck, Jim
 

billsbury

Member
Dec 27, 2005
46
0
0
I'd say give it a little time to see if it does it again. There is a slight possibility that the SATA cable (or IDE) wasn't in all the way at one of the ends. But if that were the case, something had to have made it come out the rest of the way after you left the room. So I know this sounds simplistic and stupid, and I don't mean to sound condescending, but make sure it's in all the way and see if it happens again. If it does, the people that RMA'd your drive back to you may have run a weak test on it, said it was good, and sent it back to you. Maybe.

Memory tests never hurt, but I know you used 2 sets of memory and had the same problem.

So I think if it seems to be running ok right now, it needs some time to prove itself stable. Then make some judgement calls.
 

ta8689

Golden Member
Feb 5, 2006
1,116
0
0
Originally posted by: billsbury
I'd say give it a little time to see if it does it again. There is a slight possibility that the SATA cable (or IDE) wasn't in all the way at one of the ends. But if that were the case, something had to have made it come out the rest of the way after you left the room. So I know this sounds simplistic and stupid, and I don't mean to sound condescending, but make sure it's in all the way and see if it happens again. If it does, the people that RMA'd your drive back to you may have run a weak test on it, said it was good, and sent it back to you. Maybe.

Memory tests never hurt, but I know you used 2 sets of memory and had the same problem.

So I think if it seems to be running ok right now, it needs some time to prove itself stable. Then make some judgement calls.

Basically what i said, just smarter and longer :)
 

twitchee2

Platinum Member
Dec 29, 2004
2,135
0
0
Im hoping it was just a cable that got bumped, but I thought I checked all teh cables Because that was my frist guess. I will just give it some time and see what happens. I dont think it was anything major.