disk boot failure, insert system disk and press enter

[master62]

Everytime I turn on my computer it would finish verifying DMI Pool Data and then Say
Boot from CD :
Disk Boot Failure, Insert System Disk and Press Enter

My bios boot sequence devices
First Boot Device: CDROM
Second Boot Device: Hard Disk
Third Boot Device: LS120
Boot Other Device: Disabled

Can anyone help me?

[snooker]

Hi ... Set your boot order with hard drive first and see if that help

[bluefire91]

I am having the same problem. I have set my boot order in every conceivable way, to no avail. I am using the same HDD I have had for 3 years, and it isn't dead. Once I get the error, I put in the OS disk and it boots whatever it may need and starts the system up. Here's what caused the problem: I installed a RAID card in anticipation of my switch to a new mobo. XP didn't recognize the drive, or my second drive until XP was loaded (with a floppy that contained NTLDR, NTDETECT, and boot.ini)

So, I figure: That's easy, I need to change the boot.ini to reflect the change in address. It made no difference. I used Recovery console and did fixmbr after thinking the boot record by chance needed to be corrected, still nothing. I reconfigured. My RAID card functions as an IDE controller (which will handle my CD-ROM drives) I'm running my HDD's on the new mobo IDE and CD-ROM's on the card.

Needless to say, I have even gone so far as to repair the copy of XP I have by "Upgrading" from the OS disk, and now it doesn't boot from the floppy, it will only boot if I use the OS disk, and have the boot order (logically) set to: Floppy, CD-ROM, HDD.

I'm running out of ideas, and patience, no less. Wondering if anyone has any ideas, I haven't thought of. (Preferrably, without repartitioning the HDD, which will cause data loss. I like clean installs, but this one's clean enough)

[bluefire91]

oh, yeah, one more prudent point to make is: now I can't seem to get into recovery console. Once the starts to boot I receive a "Could not find NTLDR" but it still boots into the system. I can't make sense of it. And the floppy no longer boots into the system like it once did. So, something HAS changed, I can't say that it's a good thing though

[snooker]

Originally Posted by bluefire91

I am having the same problem. I have set my boot order in every conceivable way, to no avail. I am using the same HDD I have had for 3 years, and it isn't dead. Once I get the error, I put in the OS disk and it boots whatever it may need and starts the system up. Here's what caused the problem: I installed a RAID card in anticipation of my switch to a new mobo. XP didn't recognize the drive, or my second drive until XP was loaded (with a floppy that contained NTLDR, NTDETECT, and boot.ini)

So, I figure: That's easy, I need to change the boot.ini to reflect the change in address. It made no difference. I used Recovery console and did fixmbr after thinking the boot record by chance needed to be corrected, still nothing. I reconfigured. My RAID card functions as an IDE controller (which will handle my CD-ROM drives) I'm running my HDD's on the new mobo IDE and CD-ROM's on the card.

Needless to say, I have even gone so far as to repair the copy of XP I have by "Upgrading" from the OS disk, and now it doesn't boot from the floppy, it will only boot if I use the OS disk, and have the boot order (logically) set to: Floppy, CD-ROM, HDD.

I'm running out of ideas, and patience, no less. Wondering if anyone has any ideas, I haven't thought of. (Preferrably, without repartitioning the HDD, which will cause data loss. I like clean installs, but this one's clean enough)

Sorry bud but I'm not familiar with Raid cards but from what I gather from your post the bios set up isn't recognizing your hardware set up , It could be a setting in the bios that isn't set up right, it could be drivers issues, Again I wish I could help and maybe someone here whom is familiar with Raid can assist ...

[Jeremy78]

I am experiencing a similar problem and I will share with you what I've discovered thus far.

A.) this problem may have occured if you are upgrading from a previous installation of win98

B.) you had a previous installation of win ME, or 2000

The problem is perhaps your Main Board (MB) is trying to boot one of those previous versions of windows and not your win XP. I am currently in email contact with an MSI rep (my MB manufacturer) to resolve this issue and will post the final solution.

PS.
You should also make sure that your boot order is CD 1st 2nd HHD, 3rd Floppy. The reason is because if your HHD should fail or become corrupted, you can insert the OS disk and do a recovery on the HHD. You cannot do that if your HHD is set to boot first. You'll be locked into a rock and a hard place.

[phil]

Try booting with the distribution DVD in the drive. It works for me. The system does NOT try to do the installation -- it boots normally. This is for a 160G Western Digital drive with a fresh installation on an ECS motherboard. A different drive (just using one at a time) works fine for a different operating system.

[Kevin_gibson]

Disk boot failure
This can be a number of reasons:

1: Your HDD has had it and needs replacing
2: It is trying to boot from another source, i.e. printer with memory card slots
3: A Memory card / usb stick which is in your PC.

It can be a number of things

First thing I always tell customers to do is:

1: Check in BIOS and make sure the HDD IS detected
2: Make sure the boot order seems OK, make sure the HDD is set to first boot device as a simple check.
3: Make sure no peripherals are pluggged in, i.e. printer (to rule out any 3rd booting options)

If everything seems OK, then that's when we'd try a system recovery, stick in the recovery CD / XP CD depending on the OS and recovery method.

If it boots into the recovery and we can do chkdsk /r - If that comes back OK, try and run the complete restore.
If it goes through OK and in to Windows then problem sorted just a software issue.

If it goes through OK but then comes up with the same issue, could be a fault with the HDD / Mobo (Not recognising a HDD is detected properly)

Hope this information helps.

Kev