removed the secondary HDD and things started fine. Looks like the Intel Visual BIOS tries to access the drives before loading anything, since it displays all the folders of all drives in the BIOS update tab. And the drive seems to be corrupted and hence the BIOS doesn't load. Is there any way I can detect the secondary drive and repair it? Or should I need to go back to some legacy board with legacy boot?
I’m sorry you are having problems with the motherboard but let me help you.
Based on all the information you have provided, I would like you to try the following steps:
- Power off your system and unplug the power source from the power outlet.
- Open the system up so you can see the motherboard and disconnect the power supply.
- Locate the CMOS battery. (Refer to the Technical Product Specification for the board to details.)
- Remove the CMOS battery carefully and leave it out for 15-20 minutes.
- Reseat the CMOS battery and power on the system.
After this access the BIOS by pressing the F2 and reset the BIOS settings to default with the F9 key.
Thanks for helping out. But however, clearing CMOS cache doesn't help me. I tried the steps you mentioned. But the same is the result. Stalls at splash screen if I use the secondary hard drive which seems quite corrupted. I think the Visual Bios tries to read the boot code and also some contents of the hard disk (I guess it looks for the bios update file in the folders, but I am not sure if it does only inside the boot partition of the bootable disk drive and also if it does this only when we click on the BIOS update tab). Also, disconnecting the secondary HDD helps the machine work normally. I then tried to hot-plug the SATA ports and tested with Windows and linux. Linux hangs up immediately whereas Windows helps just to *see* the drive, not *use* it. Any other way I can use this HDD in DH87RL without reading the boot code or the controller chip information?
And have you tried another HDD? Can you also try the BIOS update for the board? Here is it:
I am afraid to say that as soon as you turn the board on the BIOS will start detecting the components connected to the board so it will read the chip and the controller information.
Trying it on any other legacy boards like D945CGNL will help? Where there is no UEFI boot and legacy BIOS is in place. Will it still try to read the controller chip information from there if I set the corrupted disk to slave in such a motherboard?
If you connect an HDD it will always be read by the BIOS but if the driver is set as slave it should not be booting from that drive.