New windows XP install with 2 sata drives. Disk failure upon reboot?

By fiiibra ·

After 4 installs and 4 hours of troubleshooting, I need some help. Company got a new system with 2 Seagate 250g sata drives.

Disk 1 and 2 set up and verified on controller 1 and 2. DVD/RW and old Maxtor drive set up on IDE (DVD (master), Maxtor (slave). Bios is enabled for sata (w/o raid) All drives are recognized by the bios and are set to boot in the following order: DVD drive, Sata1.

Installed Windows XP and their version was too old to recognize past the 130g barrier. Used a newer version with SP2 and extras, drive size became correct.

Install runs perfectly, installed new mb drivers (sata, nic, sm bus and video). Upon 1st reboot, I get "disk boot failure, insert system disk". Tried installing with just xp default drivers, same error. Tried booting with just one sata drive, just 2 sata drives and the same error.

I tried installing 3rd party sata drivers during install, but of course you need a floppy drive which we don't have anymore. As xp and the bios correctly sees all the drives and boots initally, I don't think that's the issue.

Any ideas?? Thank you

AMD 3800
2 g of RAM
2 250g Seagate HD's
Asus M2-Ne mb w/Nvidia chipset

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

You may need to

by animatech In reply to New windows XP install wi ...

Get and old floppy drive and create the sata driver files and load them during the install as I think this is the problem

Collapse -

Re. Disk failure upon reboot?

There is another way without using a floopy:
Get hold of a "IDE" hdd and load Windows onto this, once loaded you can do a copy/clone over to the sata drives (once you have loaded sata drivers from motherboard cd/dvd rom disk(s)). Hope this helps you. Make sure you have a extra hdd for a backup, this does help.

Collapse -

The only time I got something like this it was a Ram issue

by karmashock In reply to New windows XP install wi ...

harddrives corrupt really quickly if your ram is bad... and it's very very very hard to detect bad ram sometimes. The last time I had this the ONLY way I knew it was the ram in hte end was that I took the ram out of the machine and put ram I just bought in it...

Sometimes it's just the port as well. So the ram might be good but the mobo port for that ram is broken.

In any event, it sounds like either the mobo is broken... perhaps the harddrive controller... or port... or it's a ram issue with either on the ram itself or the ram port.

In either case... I believe this is a hardware and not a software issue. I'd give the whole thing back to whomever you bought it from, tell them you want a COMPLETELY different machine, and hope you're not unlucky with that one as well. you might do yourself a favor, tell them what happened, and then ask them to make sure the new one doesn't have that problem. or you could just give it back, get a refund, and buy it from someone that does proper testing.

I personally just buy the parts and build them myself from the ground up every single time. I find that buying prebuilt systems generally leads to headaches. Even when you buy from someone like dell there's always bs to deal with... when you build it yourself, you know it's been done right. And that is worth the time investment. If you don't have the time for that, then pay someone you KNOW to do it. Or you're talking to india when there are issues or otherwise don't have control.

Is it more expensive to do it this way? No. Because while you pay more upfront you pay less over time in wasted tech support, faulty construction, faulty design, or having to explain to someone how to spell your name when you name happens to be something basic like "Ben"... or "Joe"...

Anyway, I've been burned almost every single time I haven't had a machine custom built. I'm always hunting for drivers not included in the package, talking to lackwits through an IP phone in india, or something equally annoying that eats up more hours then I'd like to mention of my finite life. Do it right the first time.

Collapse -

Similar situation...same problem...same MB

by NaughtyMonkey In reply to New windows XP install wi ...

I upgraded a friend's computer and had the same issue with the new SATA drives and old IDE drive. Basically it would not work with both the SATA and IDE drive in it. Ended up getting an image of the old IDE and took it out. Once I loaded Windows on the new SATA drives, I mounted the image and recovered his data. I could never get it to work with both drives in it. I did get different errors depending on the jumper placement and the SATA settings, but it never would work.

Collapse -

Issue resolved...

by fiiibra In reply to New windows XP install wi ...

So it turned out to be the sata drivers after all. I downloaded Nlite, and did a slipstreamed windows xp install with the mb drivers (and display because I'm lazy by this point), and voila, no problems. Seems XP has issues with nforce sata drivers.

In any case, thanks for the help guys and hope this thread helps someone else.

Related Discussions

Related Forums