Discussion Locked

Boot Disk Failure on First Boot

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Have built many systems with usually no hitches. Just put the following together (ALL NEW):

Antec Aria
Biostar TForce6100-939
Athlon64 3200+ Venice
Corsair 1GB ValueRam
Seagate SATA 300GB
Lite-On DVD/RW+
Media Reader on Aria case
No Floppy Drive

Posts correctly. Sees everything in BIOS. Have toyed with settings (changed boot order every way), checked all cables, etc. Will NOT boot? Same message each time: BOOT DISK FAILURE, INSERT SYSTEM DISK AND PRESS ENTER.

Have read the stories of failing HDD's and/or MOBO/controller/etc. At a loss now. This is my second MoBo in a week (first was MSI RS482M4), which I RMA'ed due to Tech Support telling me the board was bad. Now I'm not so sure it was bad, but another problem. Or just whether my luck has run out with this build. This one seems basic, but it's a doozy.

Any logical and detailed help would be appreciated.

Thanks,
Frank

5 replies

by mjd420nova

With out a floppy to boot to, you have to use
the CD to start and then checkout the HDD.
If you have a floppy, stick it in and boot
to a start up disk, do FDISK and see if the
drive is even ready.. I have seen failures
of the DMA controller chips, and they were
cheap MOBO that were over clocking the devices
to save money. I have not seen a failed SATA
chip yet but I'm sure it happens.

by jodym1

This seems odd but sometimes when trying to boot to cd I have had to change from the newer cd/dvd roms to an old one that doesn't write to cd. I came across the problem while trying to image machines and ended up carrying the old cd rom with me to image the computers. I also had the same problem with a new dvd/rw that I was trying to boot to a WIN XP cd. Once I changed the dvd/rom to an old cd/rom I was able to boot and install XP with no problem.

by jodym1

I'm glad it worked out. How funny though. I can't count how many Maxtor drives have died on me. I like Western Digital as that's the brand that I haven't had trouble with.

by frothsc1

I appreciate the comments given and initially thought some of the info given was of help. However, after another marathon evening, the situation evolved as follows:

Tried to change DVD/RW to old CD-Rom drive, wouldn't work. Got Biostar tech support on line, ran several tests, was told board is fine, but DVD drive or cable is bad. Swapped again with another DVD drive and new cable, and "voila" it booted. Thinking that was the issue, I was thrilled.

Loaded OS, drivers, software, and updates. 3 hours and many reboots later, decided to swap cable back as a test - back to "boot disk failure". Say what? Culprit must be the cable, so switch back - still boot failure. In disbelief, several more reboots and each time the Seagate 300GB starts to whine, click, and make more scary noises. Needless to say, I'm SHOCKED the culprit, or so it seems, was the HDD.

Have had many drives fail over the years (IBM, WD, etc.) but never a Seagate, which I hadn't used in years. Back to Maxtor, which has proven to be most reliable to me.

I guess the custom-build gods have conspired to inflict every possible issue on me with this new build.

Appreciate everyone's input and hope this helps someone in the future.

by hal 9000

Welcome to AMD Hell.
Most problems that I run across with AMD setups are chip set incompatibility and a lot of screwy things happen here.

I would fit a floppy even if only temporally and run the makers Sea tools to test the HDD before spitting the dummy on this one. It is possible that the drive is working perfectly and you should test it in a known good computer before you RMA the drive.

Having said that however recently I had 6 out of 8 Seagate HDD DOA but honestly that is more of an exception than the rule as generally the current crop of Seagate Drives are fairly reliable. If you try Sea tools on the existing setup and you get an error message try it in another known good computer as all that the error message will be telling you is that either the HDD controller, lead or drive is faulty so you'll need to try it in a known working computer before returning the drive as you can end up with egg all over your face when it checks out as perfect.

Incidentally when you have a solution you should end the question as it will remain open and you'll keep getting responses to it until you accept/reject the answers given or award the points.

Col

This discussion is closed to new replies.