Occasional "no boot drive found"

FerdFarckle

Junior Member
Dec 27, 2003
6
0
0
Help,

I have a Sony Vaio that I got awhile back from Costco. Its a P-4, 3ghz, 1g ram, 250g maxtor hd...
I added a AIW 9000 pro. Installed XP pro over the home edition that it came with.

I've had a recurring problem with it.

After about 5 months daily use it started having an intermittent problem where it would not find the boot drive when starting up. I did all the sony and ms updates, virus scans etc but nothing seemed to help. I figured it could possibly be a hardware problem so I changed the cable (no help) swapped hd power cables (no help), added my old maxtor 60g hd as master and put the 250g drive as slave. That seemed to work for awhile but the problem came back a month later. I swapped the two drives and the problem didn't come back for another month or so. At this point I figured I better call Sony support but they were no help at all. They said if I wanted make a warrantee claim I had to put it back to its original (as sold) configuration and use the restore cds. Out of frustration I did as they asked, a couple of weeks into it, I put back xp pro. The boot problem didn't come back for a couple months. At this point I reinstalled the 60g drive as slave and then whenever it didn't recognize the 250g hd at boot up it would boot to the 60g hd (funny thing is that when it did boot to the slave 60g hd, the 250g hd was shown (and usable) in windows after the boot.) Thinking again that it was the 250g hd, I went and bought another one. This one came with a ATA133 card (not raid). I first put it in without the ata card (but using the maxtor overlay) and all worked well for awhile. The problem came back so I put both hds on the ATA133 card thinking that its not a hd problem but a motherbd or ide problem,.

Well after all that, the problem is back.

When it does not boot-up, I do the cntl-alt-del to restart and it takes anywhere from 1 restart to around a dozen restarts before it recognizes the hd (either one).

Can anyone help me???
Ferd
 

Harvey

Administrator<br>Elite Member
Oct 9, 1999
35,059
73
91
I have seen this a few times, and in each case, reseating the IDE cable helped. If that fixes it permanently, you just had a dirty connector. If not, and you're lucky the problem is in the cable, not the connector on the motherboard or drive.

Hope that helps. :)
 

FerdFarckle

Junior Member
Dec 27, 2003
6
0
0
Harvey,
Thanks for the response but I replaced the cable then I put both drives on the ATA133 card with a new cable.
It appears to be something else.
Ferd
 

FerdFarckle

Junior Member
Dec 27, 2003
6
0
0
Harvey,
Thanks for the response but I replaced the cable then I put both drives on the ATA133 card with a new cable.
It appears to be something else.
Ferd
 

FerdFarckle

Junior Member
Dec 27, 2003
6
0
0
OOOps, sorry for the double post.

So... I have used 3 different hard drives, 3 different cables, connected to IDE port, and connected to ATA133 card in a PCI slot.

I think I can rule out the drives. I think I can rule out the cables. The connections to the motherboard may have been the problem but when I moved from IDE to PCI(ATAcard) I would have expected to have solved the problem. I kinda doubt that I have a hardware problem. Could it be software??

A problem with the BIOS? I looked for a BIOS update from Sony but they only had their original version.

ANY IDEAS????
thanks, Ferd
 

Looney

Lifer
Jun 13, 2000
21,938
5
0
Could be the onboard controller on the motherboard itself. Extremely hard to test something like this, best to just buy a new motherboard or PCI IDE controller.
 

FerdFarckle

Junior Member
Dec 27, 2003
6
0
0
I appreciate the response, but...

I don't understand... you say "best to just buy a new motherboard or PCI IDE controller".

I now have the drives on a ATA133 card in a PCI slot.

Isn't that kinda like the PCI IDE controller that you mention?

Doesn't that send me down a different path on the motherboard? (ie different controller) or am I missing something?

thanks,
Ferd
 

Looney

Lifer
Jun 13, 2000
21,938
5
0
Ah yeah, i skipped the last couple of sentences of your post, since i don't like reading paragraphs as large as that. Well, i have no idea then. I've run into the same problem as you, but i've always been able to solved it by using new IDE cables, or PCI controller.
 

FerdFarckle

Junior Member
Dec 27, 2003
6
0
0
I appreciate the responces I got...
But, someone out there must have had a similar problem...

Please help,
Ferd