Sign in with
Sign up | Sign in
Your question
Closed

"DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER."

Last response: in Systems
Share
February 27, 2008 9:03:29 PM

I've been having this problem for a few days now (and doing personal research in addition to requests for help on EggXpert and Anandtech) and I was wondering if any users on Tom's could help me out with this issue.

I have the ASUS P5N-D motherboard and after installing Windows (and formatting all the drives) my computer tells me "DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER."

So when this pops up, I found that if I leave the Windows XP CD in, it asks to boot from CD (which I just let it run without pressing enter) and Windows starts up normally. I changed the boot sequence so it goes HDD, CD, then REMOVABLE... but it didn't seem to solve anything.

I have 3x 250GB WD Caviars (all OEM from Newegg) and from what I've seen they read/write/function normally in Windows. Two of the HDDs are set in RAID 0 and in the boot sequence, this is the first HDD listed (with the backup being second).

I tried taking out hte battery on the MB and put it back in to reset the CMOS as has been suggested. Now instead of loading Windows while having the CD in, it loads the XP installation CD instead of the OS itself.

With no luck finding any solutions, I totally reformatted everything -- I deleted and reinstalled two of my HDDs and put them back in a RAID 0 setup and partitioned that setup to a C/D type of deal like before. Installed Windows and got the same issue.

This is really frustrating me because my roommate built the same exact build (except he's using the equivalent Seagate 250GB HDDs). He's thinking that it may be a problem with the HDDs, but so far it seems like all three of them are working fine. Again after reformatting, getting the same error, and putting the Windows XP CD back in... it loads Windows. Though this is nice... I'd like the system to start without having the CD in there.

I could really use the help as I dropped a good 1600+ on this system

Thanks guys! Any help is always appreciated.
February 27, 2008 9:11:58 PM

I would suggest trying to install the OS with only a single HDD installed, non-raid. If this works flawlessly then at least it gives you a baseline to start troubleshooting your raid setup. Something wrong with the raid controller, perhaps? Hope this helps.
February 27, 2008 9:14:11 PM

Makes sense...

I am pretty new at this (this is my first home built system and most of my knowledge comes from the hours of research I put into each part before putting the build together) so could you tell me what I could do to check the raid controllers? Basically what my roommate did is copy the files that the ASUS drivers CD gave him and put it on a floppy. Worked flawlessly for him so this is why he thinks it's the actual HDDs.
Related resources
February 27, 2008 9:26:56 PM

I'll assume, then, that you're using an ASUS motherboard. You might try checking the ASUS website for newer versions of the drivers. Drivers on included discs are almost inherently out of date, an effect of the time it takes once the product is manufactured and its driver disc written and packaged to the point that you receive it. Maybe your WD drives are more picky about the raid drivers than your friends Seagates, though this seems unlikely (though it's worth checking). Of course, there's always a chance you have a bad motherboard.
February 27, 2008 9:40:42 PM

Did you set the RAID partition as bootable in the RAID BIOS?
Sounds more like a configuration issue than an actual HW/SW issue. Also check that in the Motherboard BIOS you have the correct SATA drives set to be members of the RAID.
February 27, 2008 9:53:29 PM

sounds like a boot order snafu
February 27, 2008 10:03:36 PM

Try booting with only the OS HD in the system. Does it boot?
February 27, 2008 10:14:30 PM

firetatoo said:
sounds like a boot order snafu


or it could be as simple a problem as this ^

:D 
February 27, 2008 11:07:42 PM

notherdude said:
Try booting with only the OS HD in the system. Does it boot?


It's definitely not a boot order snafu and I am definitely booting from the RAID drive. I will, however, try to boot the OS HD without the backup HD first and see what happens.

Thanks for your help guys.

March 2, 2008 2:45:29 AM

I had nearly the same exact problem with my Asus P5ND2-SLI a while back.

I had just installed a second SATA 300 GB hard drive. After rebooting, I got the "Disk Boot Failure" message. I also found that just the presence of the WinXP disk in the CD drive would allow the computer to boot normally. I didn't have to boot from the CD, just have it in the drive. If I disconnected the new hard drive, everything worked just fine as before. Finally after much searching, I was able to solve the problem by updating the motherboard BIOS from the Asus website. If you haven't done so already, I'd try that.

Hope this helps.

As a side note, I also experienced an intermittent problem with WinXP hanging during boot. I finally found that if I did not install the chipset drivers that came with the motherboard, the problem never resurfaced.
March 2, 2008 3:09:42 AM

I had a few problems like this before, but it was my fault cuz i didnt check my jumpers on the cd drive and the hard drives, making sure they were set to cable select... wait, your using sata drives... hmm i dunno. soz
March 2, 2008 3:51:50 AM

Make sure the cables are pushed in firmly and try again. check the floppy cables too if you're using one, or make sure it's disabled if you aren't... in bios
March 2, 2008 5:26:33 AM

swifty_morgan said:
Make sure the cables are pushed in firmly and try again. check the floppy cables too if you're using one, or make sure it's disabled if you aren't... in bios



I also had the "Disk Boot Failure" message recently and that us what worked for me....I got my message after getting the BSOD while playing Supreme Commander...lol...I thought it was maybe because of my overclock but after countless tries to get back to windows I opened up my tower and mad5e sure everything was connected and that seemed to work
August 6, 2008 4:07:46 PM

I'm having the same problem.

ASUS M2N-SLI Deluxe, Athlon 64 dual 4800, three hard drives installed, 3G of RAM.

Had Windows XP running, installed Vista 64 ultimate (from CD, as you can't install 64 bit version from the 32 bits XP) on a separate brand new hard drive (as I didn't want to run the risk of loosing everything! God I'm happy I did!)

The system reboots fine in Vista as long as the installation CD is in. As soon as I remove it and try to boot from Vista, I get the infamous "Disk Boot Failure etc...".

The system will indeed boot normally from the old XP Hard Drive.

Updated Bios, pushed every cable in, tried MS utilities in the Vista recovery console to rebuild the MBR, nothing works.

It seems that the Vista Boat Loader does not get installed on the new hard drive... Anybody knows how we can do this? In XP, fdisk /MBR would do the trick, but not anymore.....

I'm so desperate, I'm thinking of installing LILO on that drive, but would prefer avoiding path solutions...
August 7, 2008 3:36:03 AM

Tag because it's interesting :) 
August 20, 2008 1:46:26 PM

Gotta pay my dues: problem solved!

After much searching through the internet, I discovered that some people had successes by changing the actual order of the SATA cables.

My new hard disk was on SATA port 3 or 4 I think. I disconnected the Port 1 HD and connected the new target master HD on Port 1.

Did a fresh reinstall.

Everything boots normally now....

Microsoft never told me this.... They refused to help me, thinking I was trying to hack their software which I paid a good $300 for... p.o.ed!!!
September 13, 2008 12:22:05 AM

This is a late add, but other searchers may benefit:

I just went through all this today, while getting my disks setup to rebuild a RAID mirror. I had originally backed up my source drive with driveimage.xml (http://www.runtime.org/driveimage-xml.htm). Then, to test my backup, restored that image to another drive, and when booting that drive got the "DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER" message. -This was even after I set the new drive (where I restored to) to "active" in Disk Management.

What I discovered was, with all the drive switching around on my SATA ports, the BIOS was set to boot off the wrong SATA port. So you need to be sure that your boot order in BIOS matches the drive you actually want to boot from.

Then, I needed to rebuild the master boot record on that drive. Fortunately, I had a UBCD4Win disk around (http://www.ubcd4win.com/), but one could use a regular Windows Boot CD. I booted into recovery console and did a fixmbr on the drive, rebooted, and was good to go!

I've since installed the RAID card, installed the drivers, moved the drives to the RAID card, and am now in the process of rebuilding/resynching the mirror.

Weee! (This took me all of about a day)

Hope it helps someone...

Jay
January 6, 2009 4:35:00 PM

Another late post hope it can help.

System: Asus a8n-sli Premium MB
3gb Ram : xfx 8600gt
opteron 185 dual 2.6ghz

Disk: 2xseagate 250gb raid 0 "OS and Sysfiles only:
1xwd raptor 150gb "Games Only"
1xwd 750 gb "Media Content Only"

Ok I had the same problem as eveyone else tried every possible configuration.
This is what worked for me

Step 1: disconnect all other disk except the raid array do a fresh install on that. "note build your raid array as a boot device through your nvraid bios utility." after the install is complete I recomend intalling all updates as well.
Step 2: reconnect all other disk drives. worked for me.

I thinkg what happens is the sata controller lables the boot device wrong with the other disk drives connected and therefore the boot disk failure. Good luck


Anonymous
July 31, 2009 4:16:12 AM

Hey mate,

I just had the exact same problem. I have 1 150gb raptor with my os on it and a 500gb caviar(WD).

I was adding some new ram to my comp which didnt really work for some reason, so I changed back to my old ram, then I started getting the msg you described.

I realised that in the bios, the order of my hdd's had changed, so that my comp was trying to boot from the 500gb caviar which did not have an os on it, hence the error. So my advice is check your bios and make sure that it is booting from the raid hdds and not the other which doesn't have the os on it. Hope that solves the problem:) 
September 27, 2009 9:27:09 PM

I just got the dreaded 'disk boot error message' in a machine I built about six months ago. The mobo is an ASUS M2N32-SLI Deluxe running in a RAID 0+1 array. There are four SATA HDD's (320gb each) that were working perfectly the last time I powered it down. The next time I tried to boot the box, I got the boot error message. Running WinXP Pro w/ sp3 & 4gb of Corsair DDR2 ram...yes I know that XP Pro won't run all 4gb of the ram since I'm running it in x32 mode, but it uses somewhere around 3.5gb of it. I've tried clearing the CMOS, changing SATA cables & just about everything I've read on the net, but nothing changes. I can't even reload WinXP cuz it either gives the blue screen of death or just freezes when trying to reload. I looked in the BIOS & it recognizes all four drives in the correct 0+1 RAID array. Tried rebuilding the MBR to no avail. I know that a bad HDD could cause this, but the RAID array should still boot unless the OS is on the possibly defective drive. Does anyone have any ideas regarding what I should try next? Thanks in advance for any help!
Anonymous
December 12, 2009 4:05:02 AM

This is a most common problem, there is a solution what u have to do is Disk Boot Manager CD is available in the market just get it and install it then your HDD problem will be solved and u can work with ur system as usually try to get the Disk Boot Manager CD. Dont do any other things which destructs ur pc bye..... try it.
March 29, 2010 9:33:53 PM

I'm new to this board but i have a similar problem. Here's my setup:
ASUS Crosshair II with a WD 300gb raptor drive with windows 7. I also have two other drives as one master the other slave (non SATA)
I updated my bios and installed windows 7 on the raptor. I too am getting this boot disk error message. If i leave the disk in, it boots fine. I've checked the bios and all drives are accounted for and the order is set to boot on the raptor first. I've reinstalled 7 and checked all the cables.....what is going on???? Please help!
April 11, 2010 9:25:22 PM

I had this problem on a new Acer X1300 SFF desktop for weeks. At first it would hard reboot ok, but then not at all, so I felt forced to use the Win7 'repair boot sector' feature which actually ruined the hard drive completely according to Future Shop technical support.

Acer then replaced the SATA hard drive but soon I started to have the same problem again. Finally I tried changing the bios hard drive setting to 'IDE' versus the default 'ACHL' setting (or whatever its called), and so far that has finally fixed the problem completely!.

IDE drivers were immediately auto-installed by Win7 after making that bios change, and that has been a total cure for several weeks. I don't know if its related, but I after making that change I got some actual hard drive information in the bios, which was not there before, and noticed the on board 'SATA 1' connection is to the DVD, with the hard drive connction to 'SATA 2', which doesn't look right, but there seems to be no need to change that anyway.
Anonymous
May 29, 2010 3:21:23 AM

I had this same problem on an old ASUS A8N Mobo used to build an HTPC and running a fresh install of XP Pro. The system included a DVDRom, 500 GB HDD, and 1 TB HDD (all SATA). The 1 TB was formatted and loaded under Windows 7 but the 500 GB was a new Western Digital used for the OS. The XP install went normally (aside from me forgetting to plug in the mouse). Once the XP CD was removed the machine would fail to restart and gave the "disk boot failure" message. I checked and rechecked my BIOS settings and couldn't find anything wrong.

The Mobo has 4 SATA ports (and 4 more unused SATA RAID ports). I had the 500 GB OS disk on SATA1, the 1 TB data drive on SATA2, and the DVD on SATA3. My problem was solved simply by unplugging the data drive from SATA2 and plugging it into SATA4. This might be worth a try for others experiencing this issue.
June 4, 2010 7:32:45 PM

Same problem for me. I have asus p5n-d. I found a workaround. It turns out I had a usb 500 gig seagate freeagent drive hanging off of it. The bios thought the usb seagate drive was the boot drive superseding the raid controller. In the bios when you define the boot sequence, you select the 'hard drive' as first, second, & third - as many as you can spare. Initially I know I was able to boot off raid-0. I must have fat fingered the bios at some point. The bios does not specify 'which' hard drive, it just says 'hard drive'. I enabled 'hard drive' for all my 4 boot options and it worked for me. I didn't try just 1st & 2nd. I got frustrated so I enabled them all. it works now!!.
Anonymous
July 3, 2010 11:53:22 PM

I've been having this problem last time... and this is how i fixed it...

Spoiler
I opened the Cover of my CPU.. then touched something, and after that,tried just disconnecting my hard disk (well... i only have one hard disk... so it isn't a problem) and after i disconnected and reconnected it, I tried just moving all the parts of my PC... JUST MOVING them and not disconnecting... and when I returned the Cover, I tried turning it on... and it still says "DISK BOOT FAILURE" ... so I went on to the BIOS... (u know, the DEL thingy to enter... ) and went to the IDE HDD DETECTION THINGY...and i always type "Y" on all the options... and try to save the changes on the BIOS and reboot... and then... it's fixed! I can't believe it! This is just an optional solution... i don't really know if this will fix your computer... and IT WILL ONLY WORK ON PC,s... well.. if it WILL work... :) 


Just trying...
Joshua Tahanlangit
Quote:
a 13-year old computer fixer... :p 
Anonymous
July 11, 2010 12:57:07 PM

Is the disk access settings set to LBA in the BIOS? If not, change that and re-install the OS.
July 16, 2010 12:20:01 PM

hello, there the problem might solve some pc i don't know but my pc is acer and i tried to reformat it and it startup normally abd works until i turn off it but while i restart it later the problem returns back
Anonymous
July 22, 2010 3:47:00 PM

I will suggest u check the data cables that goes to the harddisk, be it SATA or IDE. The cables can be bad. :) 
August 8, 2010 7:39:02 AM

Quote:
I will suggest u check the data cables that goes to the harddisk, be it SATA or IDE. The cables can be bad. :) 

Hello, I have the same problem, it only gives the Disk Boot Failure messsage when it has been off for a while. If you turn it back off and back on again, it will boot fine. What is wroing?
January 10, 2011 3:25:21 AM

Problem: When booting Windows Vista or 7 from an NVRAID controller after configuring a RAID array, the OS will not boot unless the windows installation disk is booted first.

Description & Fix:

windows finds a harddrive, enumerates the volumes on those drives (C:, D: E:, etc), then enumerates the next harddrive, and repeats. The order Windows finds harddrives in is based on the motherboard being used, on the M2n-SLI Deluxe it enumerates (assuming this from reading not experimentation) SATA1-6 then the JMICRO internal then external Sata then the EIDE port. Ports in RAID mode are counted together as a single disk.

If, during windows setup, you install windows onto a different volume than C: (meaning during the setup screens you see a bunch of partitioned and unpartitoned volumes and the volume you are installing onto isn't the first on that list), the windows boot configuration manager will point winload.exe to a non-c: drive and assumes that volume is booting first/is mounting first, thus the error and the reason why booting off an optical drive and letting windows setup timeout works because the boot manager on the dvd is being executed and not the one on the drive.

The hard, non-technical fix is to either setup your RAID array on SATA1&2 or unplug all other drives then install windows 7 onto just the drive or raid volume you want. This will keep windows from seeing more boot volumes than it should.

The easy, technical fix is to edit the Boot Configuration Data via BCDEDIT.exe or a GUI based BCD Editor.


Background:

The Asus M2n SLI Deluxe has two Raid controllers; a JMICRON SB686 controller off an X1 PCIE port to do e-sata and a connector on the motherboard, and the native NVRAID via the MCP55/Nforce5 southbridge available via the Mediashield menu's. Either controller can be used for RAID across all the drives, however, the JMICRON controller is ganged to the MCP55 southbridge; the NVRAID controller is faster as it is located directly on the southbridge and isn't bottlenecked by an x1 pci connection.

When Windows starts searching for drives it does it in the order of ports from first to last, defined by the motherboard. The motherboard enumerates drives based on boot order; SATA ports 1-6, then the JMICRON Controller, then EIDE.

For example, the setup I was attempting:

SATA PORT 1&2: Stripe off 2X64GB SSD
SATA PORT 3: Optical Drive.
SATA PORT 4: 1TB Single HDD
SATA PORT 5&6: Mirror off 2X1TB HDD
EIDE PORT: 250GB HDD.

As the SSD Mirror hadn't been formatted, It enumerated partitons on the 1TB disk first thus my boot configuration data pointed to the D: Volume; since I was booting off the Mirror it didn't have a D: to boot off of and failed.




January 11, 2011 6:46:44 AM

As suggested by my friend I changed the small round shaped battery inside the hard disk which costs Rs 20.00. System started functioning normally.
June 10, 2011 12:08:25 PM

gliderp1 said:
I had nearly the same exact problem with my Asus P5ND2-SLI a while back.

I had just installed a second SATA 300 GB hard drive. After rebooting, I got the "Disk Boot Failure" message. I also found that just the presence of the WinXP disk in the CD drive would allow the computer to boot normally. I didn't have to boot from the CD, just have it in the drive. If I disconnected the new hard drive, everything worked just fine as before. Finally after much searching, I was able to solve the problem by updating the motherboard BIOS from the Asus website. If you haven't done so already, I'd try that.

Hope this helps.

As a side note, I also experienced an intermittent problem with WinXP hanging during boot. I finally found that if I did not install the chipset drivers that came with the motherboard, the problem never resurfaced.


----------------

Hey there. I have the same motherboard as you, but I am running Windows7 and I do not know which bios update I should use, I went to the Asus p5nd2-sli webpage, but it only had drivers for vista and XP. I could use your help please.
August 24, 2011 8:45:11 PM

frangagn said:
Gotta pay my dues: problem solved!

After much searching through the internet, I discovered that some people had successes by changing the actual order of the SATA cables.

My new hard disk was on SATA port 3 or 4 I think. I disconnected the Port 1 HD and connected the new target master HD on Port 1.

Did a fresh reinstall.

Everything boots normally now....

Microsoft never told me this.... They refused to help me, thinking I was trying to hack their software which I paid a good $300 for... p.o.ed!!!


HI, good day, i m also facing the same problem DISK BOOT FAILURE, ......
but after trying each and every thing I reach on the consequence that it must be motherboad or BIOS problem...
Because I also tried by unplugging the hard-drive and attached only the CD rom to boot from it... but system Never tries to read anything from CD and suddenly say "Disk Boot Failure, insert ................."

And the CD-DRIVE that i m using with this system is 100% working on the other computer...i m using...
any one who can tell the solution.....he has...!!!
September 2, 2011 7:55:12 AM

Quote:
This is a most common problem, there is a solution what u have to do is Disk Boot Manager CD is available in the market just get it and install it then your HDD problem will be solved and u can work with ur system as usually try to get the Disk Boot Manager CD. Dont do any other things which destructs ur pc bye..... try it.

i had also the same problem when i boot a blue screen appears saying corrupt files and fix cable so what i did is i connect the hdd to slave and format the disk drive so data where deleted. then remove the primary and innstall the drive i formated. now when i restart my computer an error message saying ntldr missing. what i did is i went to bios setup instead of booting to 1st to hdd i boot to cd 1st and 2nd is hdd. now i restart my pc and boot from cd and i did it works fine. :lol: 
September 26, 2011 1:19:43 AM

i had the same problem too i got a new blank hard disk and installd windows on it
good luck
September 29, 2011 8:49:28 AM

i' am having the problem with ASUS P5N73-AM motherboard , problem is cropping up every alternate period of using the system.... i wonder what sort of problem is that. my engineers are also failing to detect any problem, either the hdd or motherboard seems to have some problem which is totally un-detectable
!