General discussion

Locked

Disk boot failure

By Blackcurrant ·
Hi

One of the machines on my network has just had its motherboard replaced with an old one from another machine. I have no idea what type of motherboard it is...

After connecting the HDD - a Quantum Fireball 3.5 series, the machine boots then displays DISK BOOT FAILURE.

I have checked the BIOS (Award modular BIOS v4.51PG), and have manually entered the settings for the drive c/h/s:4092/16/63. The POST screen, however, shows no HDD listed.

I have run the powermax diagnostic utility available from Maxtor which detects the drive and declares it healthy after an intensive check.

Can anyone help me get the drive recognised?

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by gbxtr In reply to Disk boot failure

Recheck your cables to make sure they are connected correctly. I'm assuming they are because the powermax diag utility sees the disk. Also you may try switching the jumper to cable select, or master to see if this helps.

Collapse -

by Blackcurrant In reply to

Hi, thanks for answering. Yep, the cables are connected properly. I cannot change the jumper settings because the disk never had a jumper set, and also the jumper settings diagram on the drive label bear no resemblance to the jumper pins on the drive: The diagram shows 5 pins but the drive only actually has 3.

Collapse -

by carlos.nino In reply to Disk boot failure

Hi,

Maybe the HDD is not compatible with the board. Make sure your BIOS is updated, and that the cable is connected the right way. Use a boot floppy with fdisk in it, and use to see how it detects it.

Collapse -

by Blackcurrant In reply to

Hi Carlos, thanks for answering. I am sure the HDD is compatible with the board. Fdisk does not detect the drive.

Collapse -

by Mark In reply to Disk boot failure

Sounds like a 2G Hard Disk? Try booting from a boot disk and see if you see the files. Run Scandisk and if eveything looks fine, run sys c: to see if you can make it bootable. I assume this is a WIN9X system? Some BIOS's may see the drive differently and that particular BIOS had some issues. You may need to load an overlay, but I don't think so. Use the BIOS numbers at the bottom of the screen to search for a mainboard update. Also be prepared to work out the driver issues. Changing the physical board is the easy part. You still have to get windows to talk to it.

Collapse -

by Blackcurrant In reply to

Hi Mark, thanks for answering. Yes, it's a 2GB Quantum Fireball 3.5 series disk. Booting from a floppy does not help - the drive is not detected by the BIOS so C: is an 'invalid drive specification' The OS is Win98SE. I have visited motherboards.org and have tried to use their online motherboard identifier program, but the BIOS strings I enter are invalid (I have tried inputting all the BIOS numbers seen on-screen).

Maybe, as suggested above, the HDD is incompatible with this board...

Collapse -

by Mark In reply to Disk boot failure

Do you know where this board came from? It sounds like it may have a bad controller or the drive just coincidentally went belly up during the transition. The drive should have a DS jumper to set it as Master or Standalone. The SP (Slave Present) jumper should not be installed normally, but sometimes yes if you have a slave device. Be sure the IDE cable is oriented correctly. Double check by trying the drive on another system. You can also check the Maxtor Troubleshooter at http://maxtor.custhelp.com/cgi-bin/maxtor.cfg/php/enduser/olh_adp.php?p_faqid=1584&p_created=1061317309 (Maxtor bought Quantum).

Kinda sounds like a bad mainboard IDE controller to me. Make sure it's enabled in the BIOS too.

Collapse -

by Blackcurrant In reply to

Hi Mark, thanks again for answering. The problem has now been sorted. The problem was caused by the CD drive being on the same cable as the HDD. Also, the BIOS settings were wrong - I had the drive set to User and had inputted the C/H/S settings from the label which set the drive type as normal, whereas in reality the drive needed to be set to LBA (which requires completely different C/H/S).

Am now reformatting and reinstalling...

Collapse -

by Blackcurrant In reply to Disk boot failure

This question was closed by the author

Back to Desktop Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums