Bios does not see ide hard drive. What to do if Bios does not see the hard drive. Physical causes and ways to eliminate them
Hello, we came to you with a problem. We decided to upgrade the computer, but not the whole computer, but the main components: the motherboard, RAM, video card and power supply, all of which were safely installed in our old case. And now the problem is, our BIOS is not in hard drive is running and a disk drive, both IDE interface devices remained from the previous computer and we did not change them, the technician at the service center connected both drive data to our new motherboard with one IDE cable, since there is only one IDE controller connector on the motherboard. We brought the system unit home and when we turned on the computer, only a black screen, go to the BIOS, there is the inscription: Primary IDE Master No detected and Primary IDE Slave No detected. We would go back to the service center, but we don’t live in the city. What can you think of?
BIOS does not recognize the hard drive
I come across a similar situation quite often, probably before your hard drive and disk drive were connected to the old motherboard, using separate cables, to two different IDE connectors and both worked in the Main position, that is, Master. The service simply connected your two devices to one cable, but forgot about the jumpers, now both of your devices are working in Master mode, because of this there is a conflict and as a result BIOS does not recognize the hard drive and the disk drive too.
- In our article we will work with a hard drive and an IDE interface drive, if you have little experience, about how to connect and disconnect and what errors you may encounter, read in more detail. If this article does not help you, try another one, in it described .
Where they assembled your computer, we were in a bit of a hurry and now we will try to fix everything. IDE interface devices need to be configured with a jumper; this will tell your computer how to properly access the drives (and the drive). When working with IDE devices, it is very important for a computer to know who is the master device on one loop, Master, and who is the slave, Slave, this is decided by the little one. The contacts on which the jumper is mounted are located directly on the drive. Instructions for the location of the jumper are usually located on the drive body. We turn on the computer and go to, first of all you need to make sure that the IDE controller is enabled in the Integrated Peripherals tab.
Make sure the power cables are connected.
In our article, we will first set up a Seagate hard drive with jumpers, then, to gain experience, a Western Digital and Maxtor hard drive, with a Sony NEC Optiarc as the drive. Pay attention to the screenshot. I also have a similar problem, the BIOS is not in hard drive is running and disk drive, both devices are not detected Primary IDE Master No detected and Primary IDE Slave No detected.
From the very beginning, we look at how the jumper is mounted on the Sony NEC Optiarc drive. According to the instructions located on the drive body, the extreme right position is Master, which means the drive is already connected by a jumper as the main one. It is best to connect the Master device to the end of the loop.
Now let's move on to the hard drive, the Seagate hard drive is also connected as Master, two main devices on one cable is an inevitable conflict.
![](https://i2.wp.com/remontcompa.ru/uploads/posts/2011-12/1323120728_5.jpg)
The result for both devices in the BIOS is No detected. Let's avoid device conflict and leave our drive as Master, and connect the Seagate hard drive as Slave. We look at the instructions and see that the Seagate hard drive operates in slave mode without a jumper at all, remove the jumper completely.
We check if everything is connected correctly and turn on the computer. The result is obvious, both devices were found and identified. Now we connect the Western Digital hard drive in the same way, everything is perfectly defined in the BIOS. Behind it is a Maxtor hard drive, everything is fine too.
Many may notice that if you connect the hard drive to the end of the cable and make it the Main-Master, and the disk drive in the middle and the slave-Slave, because the more important device is always connected to the connector at the end of the cable, you want to do it this way, after all, the work of the hard drive is a priority for us. Then the main thing is not to bend the train itself too much, don’t be too clever, it will look something like the screenshot.
We take our first Seagate hard drive and put the jumper in the extreme left Master position, and connect it to the connector at the end of the IDE cable.
and set the jumper on the Sony Optiarc drive to the Slave position, that is, according to the instructions, in the middle and connect it to the cable connector, also in the middle.
Below is a list of the main problems due to which BIOS does not recognize a SATA hard drive. To find out the true cause of the malfunction, you need to carry out sequential diagnostics of all interconnected components of the computer to determine if they are working properly.
- The hard drive is not set as enabled in the BIOS.
- Serial ATA drivers are installed incorrectly or not installed at all.
- The data cable is damaged or not connected.
- The disk drive does not spin.
- The jumpers on the drive housing are set incorrectly.
- The hard drive itself is faulty.
First you need to make sure that the device you are testing is enabled in the BIOS. To do this, you need to enter the settings - at the very beginning of the operating system startup, press the F2 or Del key. Depending on the modification of the system, there may be different options. What exactly do you need to click to enter the BIOS settings? A message appears briefly at the bottom of the screen when you turn on the computer. If you miss a period, you will have to turn off the computer again and wait until you enter the settings.
Find the hard drive that is not detected on one of the settings screens and look at what is written next to it. Automatic detection must be specified. If it says Off. (Off) you need to switch to automatic detection. This problem is typical in cases where a newly installed hard drive with a SATA connection is not detected.
Motherboard drivers not loaded
Problems with driver installation most often occur in cases where Windows OS is installed on a disk drive that is used as the main boot drive. Then the Bios does not see the SATA hard drive due to problems with the drivers.
To correctly download and install drivers, perform the following manipulations:
- Load the Windows distribution into the DVD drive tray. After this, disconnect the computer from the power supply.
- Insert the SATA hard drive and connect it. Turn on your computer.
- During the installation process, you will need to press the F6 key at the appropriate moment to start the driver installation process. During the normal course of the system installation, a screen will briefly appear stating that in order to install the system normally, you need to download the missing drivers: “Press F6 if you need to install a 3rd party driver.” Try not to miss the moment, otherwise you will have to start all over again.
- After a while, an interface for loading drivers for the SATA controller will appear. Press the S key to continue installation.
- To download the drivers, you will need disks with installers; this must be found and downloaded in advance on the Internet, on the website of the manufacturer of the motherboard that is installed on your computer.
Data cable fault
Open the system unit and carefully inspect the cables connected to the motherboard and hard drive. If there is visible mechanical damage, this is the problem. Data cables are easily bent and broken, which leads to a lack of contacts in the connections. It is advisable to check the cable by replacing it with a known working analogue.
Seagate technical services note that for normal operation of the devices, the length of the SATA cable does not exceed one meter. SATA cables often simply fall out of the connectors due to vibration of the computer during operation. Check the reliability of the cable connection to the SATA ports.
When connecting loops, be guided by the following conditions:
- The blue connector must connect to the motherboard controller.
- The gray connector is used to connect a Slave – an auxiliary hard drive.
- The black connector is for the Master – the main drive.
If the cable assignment order is mixed up, it confuses the BIOS and leads to device identification errors.
The disk does not rotate
The hard drive will not be found if it is not receiving power and is not spinning. It is impossible to see the rotation of the disk externally; one can only rely on indirect signs.
With the power off, open the system unit, then turn on the computer and listen. Taking precautions, try touching the side wall of the hard drive. If vibration is felt, the disk is rotating.
If nothing is clear, try turning the drive's power cable on and off and comparing the sound. To check the functionality of the power cable, connect it to a DVD drive, where you can accurately see whether the disc is spinning or not.
It is also useful to check whether the installed power supply supplies sufficient power? It is quite possible that as the system unit is upgraded, power consumption has increased significantly and now there is simply not enough current to maintain the required performance of the equipment.
To make sure that the device being tested is working properly, remove it from the system unit being tested and install it on a known-good computer. If it doesn’t work, the hard drive itself is faulty.
The BIOS tools include a function for testing connected drives for functionality. Run the test and see the results. If any disk is faulty, it will be clear after the test.
Incorrect installation of jumpers on the drive housing
First you need to check whether the jumpers on the Master-Slave attribute are correctly distributed. If both devices have the same settings, the BIOS will not be able to detect them correctly.
A diagram of the correct location of jumpers is drawn on the drive housings. Set them according to the required priority for selecting disks in the BIOS.
If you turn on your PC and its BIOS does not see the SATA hard drive, then, despite the fact that this situation, of course, cannot be called pleasant, in some cases it can still be successfully resolved. However, the methods for solving the problem and the likelihood of success largely depend on the causes of the malfunction, of which theoretically there can be several.
Hard drives have long taken leading positions in the field of long-term information storage as devices that combine high capacity, low price and acceptable reliability and speed characteristics. While hard drive technology may not have advanced at the same rate as other computer components such as the processor and memory, hard drives today are far superior to their predecessors in terms of capacity and speed. In the last decade, significant progress in improving the parameters of hard drives was largely associated with the transition to a new technology for exchanging data between the hard drive and the motherboard -. Currently, SATA hard drives have practically replaced hard drives with an IDE interface from use, largely due to their high speed and the absence of limitations typical for IDE drives. In particular, connecting SATA hard drives to a computer is much easier and faster compared to IDE drives.
However, users of drives with a SATA interface are not immune to problems. There is often a situation where the hard drive is not visible to the old operating system. But a particularly unpleasant problem is that the hard drive is not recognized at the BIOS level. In such a case, naturally, this hard drive cannot be used to store data; In addition, it is impossible to boot a personal computer from it.
There may be several reasons for the situation when the BIOS does not see the hard drive, but basically they can be divided into the following categories:
- Hard drive or motherboard failure
- Error connecting the drive
- Error when setting BIOS options
Errors when setting BIOS options and fixing them
Many BIOS have a number of options that allow you to configure the operating parameters of the SATA host controller built into the motherboard chipset. In some cases, incorrectly setting the values of such options can lead to the inoperability of all or some of the hard drives connected to the computer, or to the inoperability of certain types of them, for example, drives connected to IDE or SATA connectors.
In particular, the option found in some BIOS has the value PATA Only, which disables support for SATA hard drives, leaving only IDE interface drives for use. In addition, if the controller in the BIOS is configured in such a way that it supports the traditional mode of accessing drives in IDE mode, then in this case the system can support no more than 4 drives, and all extra drives will simply not be visible.
Sometimes it happens that the BIOS does not see the second SATA hard drive installed in the system. In this case, the problem may be either a BIOS error or the fact that the SATA drives belong to different versions of SATA, for example, the first is SATA-2, and the second is SATA-3. In this case, it is best to set the second hard drive to SATA-2 operating mode using the corresponding jumper on its case.
Some options, such as Serial-ATA Controller, allow you to disable the SATA controller altogether. In this case, all drives connected to the motherboard connectors will not work.
You should also note that in some BIOS you can disable automatic detection of hard drives. Check if you have such an option, and if so, then its value should be set to Auto.
Additionally, in some cases, especially with older motherboards and BIOS, there may be errors in the BIOS that prevent the system from recognizing the hard drive correctly. To eliminate this possibility, you need to reset the BIOS to default settings, and if the BIOS still does not see the disk, then update the computer's BIOS version.
Errors when connecting drives to the motherboard, physical malfunction of drives and other components of the system unit
SATA hard drives do not require jumper settings to select Master and Slave operating modes, which are vital for the operation of IDE drives, so their configuration in the system is not required. In addition, SATA connectors and cables are much more convenient than IDE connectors and cables, and therefore most users do not have any problems connecting SATA hard drives. However, insufficiently tight contacts between cables and sockets can also lead to a situation where the BIOS does not see the SATA hard drive installed in the system. If you have made sure that the controller configuration in the BIOS is configured correctly, but the BIOS still does not see the disk, it makes sense to check the reliability of the cable connections to the motherboard, and also check the cables themselves by replacing them with other cables of the same type.
If, after this check procedure, the BIOS still does not see the hard drive, then it makes sense to check it in another place, taking a second system unit - it is quite possible that the problem lies in the hard drive itself - in the disk controller or in the mechanical drive. In the first case, the disk can most likely be repaired; in the second case, you will have to look for a replacement.
In some cases, the problem may not be with the hard drive, but with the SATA host controller on the motherboard. If this is the case, then the motherboard will most likely need repair. There are also cases where the BIOS does not see hard drives due to a faulty power supply.
Conclusion
The situation when the BIOS of a personal computer does not see one or more hard drives operating using the SATA interface, fortunately, does not occur very often. However, a similar problem may occur, especially if the computer is using an old version of BIOS containing errors, or if two SATA drives belonging to different generations of SATA are simultaneously installed in the system (in such a case, the second the disk may not be detected). Also, in some cases, there may be incorrect settings of BIOS options, incorrect or careless connection of disks using data or power cables. The user is not immune from hardware failures in the operation of the disk controller, as well as in the operation of the SATA host adapter located on the motherboard. In the latter cases, the problem can be corrected, as a rule, only by contacting the service center specialists.
The hard drive is the main device of your computer or laptop. It contains the operating system that runs the machine. All your data is also stored there. Without it, it is impossible to imagine the operation of electronic computer technology. Therefore, it must be handled with care and precision. After all, if this part fails, you may lose all your valuable information.
However, it often happens that your BIOS does not see the hard drive. This is influenced by a number of factors. First of all, you need to check that the device is connected correctly to the motherboard. Pay attention to the voltage supply cord that comes from the power supply. If there are no problems with this, then try connecting your hard drive to another board controller. It also makes sense to replace the interface or power cable. These are rare cases, but they do happen.
It also happens that the BIOS does not see the hard drive due to insufficient power or a malfunction of your power supply. Therefore, it is worth paying attention to this nuance. If the BIOS does not see the SATA hard drive, try changing the adapter from IDE. Don't forget that for IDE devices to work, your BIOS must have support for such drives enabled.
Go to advanced settings where you select the configuration of connected devices. Here you can activate the controller for the IDE hard drive. Don't forget to exit and save your changes afterwards. If your system unit already has equipment installed that has a new SATA interface, but you still need to connect another hard drive with an IDE interface, the above procedure is also required.
Please make sure that the IDE and SATA devices you need are marked ENABLED. The maximum allowed number of IDE devices cannot be more than two per controller. If you have two connected and the BIOS does not see the hard drive, try disconnecting one.
Also in my practice there were devices that under no circumstances wanted to be displayed as slaves. The BIOS also does not see the hard drive if you incorrectly set the jumper, which is responsible for the operating mode (master, slave and device detected by a loop). First, see if you even have it. If so, then there should be a diagram on the top of the disk for the correct connection.
These are the main problems that can arise with working hard drives. I would like to draw your attention to the fact that very rarely the BIOS does not see a SATA hard drive. There are almost never any problems with these devices. If you still encounter them, try changing the cable and going to the factory BIOS settings. If this does not help, you need to check the device itself.
I hope you understand what you need to pay attention to first. As a rule, all these methods work and help. If nothing works for you and the device still refuses to work, contact special service workshops. They will be able to determine the exact cause of the problem and, if possible, bring the hard drive you need back to life. Under no circumstances should you attempt to disassemble it yourself.
Hello friends! Yesterday I was assembling a new computer for a friend and wondered why the BIOS did not see the hard drive. After I figured out this problem, it turned out that I needed to install a jumper. But there are other cases when the hard drive is not detected in the BIOS and operating system; I will tell you about solutions to these issues in this article.
Before you find out why the BIOS does not see the hard drive and what to do, I would like to say that there may be several reasons. I have described them all below, so read carefully.
- The disk drive does not rotate;
- The hard drive is set to BIOS but not turned on;
- Serial ATA drivers are not installed/incorrectly installed;
- There are problems with the hard drive;
- The data cable is not connected/damaged;
- The jumpers on the drive housing were set incorrectly.
To identify the cause of the malfunction, it will be necessary to conduct a complete and consistent diagnosis of all computer components. I will now tell you how to do this better and faster.
What to do if the hard drive does not spin
Unfortunately, you will not be able to see the rotation/non-rotation of the disk by visual inspection. We can only guess about this through some indirect signs.
- Turn off the computer from the network and open the cover of the system unit.
- Now turn on the power and listen carefully. If you touch the side wall of the hard drive and vibration is felt, everything is in order, the disk is rotating.
- If there is no characteristic noise and vibration, then you can turn on and off the drive's power cable and compare the results. If the noise changes in any way, then the disk is working.
Hard drive is not turned on/incorrectly connected to BIOS
An indication of this will appear at the bottom of the screen when you turn on the computer. However, the indication appears only for a short period of time, and if you miss this moment, you will have to turn off and turn on the PC again and wait until you enter the settings category.
Now on the settings screen you will need to find a hard drive that is not detected. What is written opposite it? In theory, automatic detection should be specified - Automatic. If you have it set to Off, then switch to automatic detection. This happens when a new hard drive with a SATA interface is installed.
Many users use a disk drive that stores files from their Windows operating system to store their data - photos, music, movies, documents, etc. However, you cannot store your data on the same disk as the operating system.. Because of this, problems often occur with installing drivers and the BIOS therefore does not see the SATA hard drive.
- Insert the Windows OS disc into the DVD tray.
- Disconnect the computer from the power supply.
- Insert the SATA hard drive and connect it.
- Turn on the computer's power supply.
- When the installation process begins, you can press F6 at any time - and then the driver installation will start. If the installation proceeds as expected, then at a certain moment a message will appear that for correct installation it is necessary to download the missing driver. You can't miss this moment, otherwise you'll have to start all over again.
- An interface for downloading drivers for the SATA controller will soon appear. Click on S to continue with the installation.
- You will need installer disks for various drivers and programs. They can be downloaded in advance from any website.
Drive jumpers
Look more closely and you will see that a diagram of the correct location of jumpers is on the housings of all drives.
So, what should you do if the data cable is not connected correctly or is faulty?
- We open the system unit and look at the cables that go to the motherboard and hard drive. If any mechanical damage catches your eye, then everything is clear - that’s the reason.
- Due to vibration during computer operation, SATA cables may simply fall out of the connectors. It is best to check that all cables are securely fastened.
Hello, we came to you with a problem. We decided to upgrade the computer, but not the whole computer, but the main components: the motherboard, RAM, video card and power supply, all of which were safely installed in our old case. And now the problem is, our BIOS is not in hard drive is running and a disk drive, both IDE interface devices remained from the previous computer and we did not change them, the technician at the service center connected both drive data to our new motherboard with one IDE cable, since there is only one IDE controller connector on the motherboard. We brought the system unit home and when we turned on the computer, only a black screen, go to the BIOS, there is the inscription: Primary IDE Master No detected and Primary IDE Slave No detected. We would go back to the service center, but we don’t live in the city. What can you think of?
BIOS does not recognize the hard drive
I come across a similar situation quite often, probably before your hard drive and disk drive were connected to the old motherboard, using separate cables, to two different IDE connectors and both worked in the Main position, that is, Master. The service simply connected your two devices to one cable, but forgot about the jumpers, now both of your devices are working in Master mode, because of this there is a conflict and as a result BIOS does not recognize the hard drive and the disk drive too.
- In our article we will work with a hard drive and an IDE interface drive, if you have little experience, about how to connect and disconnect and what errors you may encounter, read in more detail. If this article does not help you, try another one, in it described.
Where they assembled your computer, we were in a bit of a hurry and now we will try to fix everything. IDE interface devices need to be configured with a jumper; this will tell your computer how to properly access the drives (and the drive). When working with IDE devices, it is very important for a computer to know who is the master device on one loop, Master, and who is the slave, Slave, this is decided by the little one. The contacts on which the jumper is mounted are located directly on the drive. Instructions for the location of the jumper are usually located on the drive body. We turn on the computer and go to, first of all you need to make sure that the IDE controller is enabled in the Integrated Peripherals tab.
Make sure the power cables are connected.
In our article, we will first set up a Seagate hard drive with jumpers, then, to gain experience, a Western Digital and Maxtor hard drive, with a Sony NEC Optiarc as the drive. Pay attention to the screenshot. I also have a similar problem, the BIOS is not in hard drive is running and disk drive, both devices are not detected Primary IDE Master No detected and Primary IDE Slave No detected.
From the very beginning, we look at how the jumper is mounted on the Sony NEC Optiarc drive. According to the instructions located on the drive body, the extreme right position is Master, which means the drive is already connected by a jumper as the main one. It is best to connect the Master device to the end of the loop.
Now let's move on to the hard drive, the Seagate hard drive is also connected as Master, two main devices on one cable is an inevitable conflict.
The result for both devices in the BIOS is No detected. Let's avoid device conflict and leave our drive as Master, and connect the Seagate hard drive as Slave. We look at the instructions and see that the Seagate hard drive operates in slave mode without a jumper at all, remove the jumper completely.
We check if everything is connected correctly and turn on the computer. The result is obvious, both devices were found and identified. Now we connect the Western Digital hard drive in the same way, everything is perfectly defined in the BIOS. Behind it is a Maxtor hard drive, everything is fine too.
Many may notice that if you connect the hard drive to the end of the cable and make it the Main-Master, and the disk drive in the middle and the slave-Slave, because the more important device is always connected to the connector at the end of the cable, you want to do it this way, after all, the work of the hard drive is a priority for us. Then the main thing is not to bend the train itself too much, don’t be too clever, it will look something like the screenshot.
The hard drive slows down no matter how you connect them. What in our case? We look in the BIOS, the speed of our DVD-rom Sony NEC Optiarc -UDMA-4, most likely the Seagate UDMA-5 hard drive will work in UDMA-4.
Why am I saying this? But why, if you have a very old disk drive, it’s better not to connect it with one cable at all, since the speed of both devices will be very low, most likely PIO, so save up for a new one in this case.
When you turn on your computer, the BIOS checks its hardware for functionality. If the hard drive has physical damage, then the BIOS does not see it. Accordingly, a notification will appear on the monitor screen stating that the hard drive was not found.
Causes of the “hard drive not found” error
If the BIOS does not see the hard drive, the problem may lie in either a hardware or software failure. However, among the most common it is worth highlighting:
- The hard drive is disabled in the BIOS;
- The hard drive is damaged;
- The hard drive is not connected correctly;
- The hard drive jumpers are not set correctly.
Such reasons are typical for HDD drives. However, if you have an SDD, then to some extent the tips presented will also apply to hard drives of this type.
Incorrect hard drive connection
If the BIOS does not see the hard drive, the problem may lie in incorrect connection of the cables to the motherboard.
Open the side cover of the system unit and check all cables for connections.
IMPORTANT! If the SATA cable is 1 meter long, it must be replaced with a shorter one, since a longer length causes frequent failures in the OS.
Setting up jumpers
If your PC has two hard drives and you are using the IDE interface, then the jumpers on the hard drive may be set incorrectly. They indicate which disk is “Master” and which is “Slave”. Therefore, we look at the back of the hard drive and look at the connection instructions.
It is also worth paying attention to the temperature regime of the hard drive. If it overheats, you need to adjust its cooling or install an additional cooler.
Checking BIOS settings
Any PC component turns on and off. In the event of a system crash, changes to the BIOS settings can be made without the user's knowledge. Therefore, if the BIOS does not see the hard drive, you should double-check the settings of the first one. To do this, press “Del+F2” during the first seconds of rebooting the PC. Go to the “Main” section and look at the “Sata Configuration” parameter. Its value should be "Enabled". If the value is different, click the arrows and select the desired one.
If you turn on your PC and its BIOS does not see the SATA hard drive, then, despite the fact that this situation, of course, cannot be called pleasant, in some cases it can still be successfully resolved. However...
Good day everyone, dear readers! In this article I will try to explain why the BIOS does not see the hard drive - as well as ways to solve this problem, I will tell you in my article.
This problem, when the hard drive is not detected by the computer, is the most common. It occurs on both old and new computers. This also happens with new and old, external and built-in HDDs.
First, of course, you need to find out the cause of this problem. Sometimes users can solve everything on their own and get things working with Windows and the laptop’s hard drive.
Why can't my computer see my hard drive?
Let me note right away that there are several reasons why a hard drive refuses to perform its functions. These reasons include:
- For the first time, a new sata or ide drive was connected;
- There were problems with the cable or wires;
- Perhaps the BIOS is not configured correctly or is completely out of order;
- Weak power supply;
- Low cooling system;
- The hard drive itself has failed.
Yes, you need to diagnose it, and only then solve the problem. Let's say that an inexperienced user will probably have some difficulties with this. Let me help you, and together we will figure out what and how.
First connection of the hard drive
If this is your first time connecting a screw, then most likely the system simply did not see it. Yes, physically it is in working condition, but it is not displayed among local disks.
In order to fix this problem, you need to press Win and R on your keyboard, write compmgmt.msc and select “Ok”.
Find and select "Disk Management".
In the window that appears in the middle, all your connected drives will be identified, including your problematic hard drive. As a rule, it is such because the assigned letter is incorrect.
Find the required drive and right-click on it, and then select “Change drive letter or drive path...”.
A window will open in which you will have to click on the “Change” button.
Now select the desired letter and select "OK".
Invalid format
For normal functioning of the disk in Windows, the NTFS format is required.
Just as in the instructions above, go to “Disk Management”, that is, repeat the previous first two steps. After that, right-click on the disk and select “Format”.
Select the file system – NTFS, and click “OK”.
BIOS does not see the hard drive - setting
In some cases, the BIOS may set the wrong priority for boot devices. When booting the PC, press F2 (or Del). Which key needs to be pressed will be indicated when the PC starts. By pressing the desired key, you will enter the BIOS.
Please note that due to differences in BIOS versions, the names of menu items here and below may differ slightly.
Find the "Boot" tab. Use the arrows to control. In the list of boot devices, set your HDD to first place (1st Boot Priority/First Boot Device).
Press F10 to save and exit and then press Y to confirm. After this, the PC will boot from the device you set.
SATA operating mode
Often, users do not have an operating mode in their BIOS that is compatible with the IDE. To make the change, you need to go into the BIOS, select Main, Advanced or Integrated Peripherals and find the SATA Operation, Configure SATA As, or OnChip SATA Type setting.
Select IDE or Native IDE, press F10 and enter Y.
BIOS does not show hard drive
If the BIOS cannot detect your hard drive, then most likely it is due to incorrect settings or failures.
Incorrect settings appear due to user actions, and failure can occur for various reasons. So, starting from power outages and ending even with system infection. The system date may indicate this - if it is not accurate, then you have undoubtedly experienced a failure. To fix this problem, you need to reset all settings.
Find the Clear CMOS jumper on the motherboard.
Change the jumper from contacts 1-2 to 2-3, hold them for 20-30 seconds and then return them to their original position. Besides, there is another way. Find the motherboard in the system unit and remove the battery from it.
You will need to return it back in 25-30 minutes.
Conclusion
Now you know what to do if the BIOS does not see the hard drive. I hope you were able to solve your problem, thank you all for your attention, and don’t forget to ask any questions in the comments!
07.10.2010, 13:22
Recently the following problem appeared:
While working with the computer, a blue screen appeared (this has happened before, I rebooted and that’s it). I rebooted and it gives me "disk boot failure. insert system disk and press enter"
I thought the hardisk was gone, I wanted to launch from a CD-rom, but it seemed like it didn’t exist. Also in the BIOS you can’t see anything except the SATA hard drive.
After spending a couple of hours in the guts of the computer, replacing the tire and blowing all the dust off, rechecking the connectors, I returned everything back. the result was the same
"disk boot failure. insert system disk and press enter"
I walked away for 5 minutes, restarted, to my surprise I saw that everything that was hanging on the IDE was returned. As if he needed a break ;)
I suspect that the port itself or something in the motherboard has something to do with this, is there a way to check this? What other versions could there be?
PS: now I’m working from a problematic computer, until a blue screen pops up and again I have to wait, dig, hope that it will turn on after the restart
General information about your computer
07.10.2010, 14:24
nothing is visible except the SATA railway.
to my surprise I saw that everything that was hanging on the IDE was returned
So which interface is your drive on - IDE or SATA? And in general, a complete description of your hardware and what OS you need...
07.10.2010, 15:33
Disconnect the CD-ROM from the IDE for a while, try to work without it
08.10.2010, 16:21
SlavikK, tried it, doesn’t help
Leon534, interface hangs on IDE
At the moment I connected the “old organ”, I’m waiting for advice
08.10.2010, 16:41
What are some tips here? If it starts when cold, but after working it “breaks,” then it’s most likely overheating. Dust, problems with the fan, a foreign body interfering with cooling (maybe the cable is poorly positioned) - most likely this is the problem. Just in case, look at the capacitors, try installing an additional fan, at least check the temperature with Everest.
By the way, you say that you cleaned everything, and the power supply? Maybe it overheats and the voltage starts to jump.
08.10.2010, 16:47
2 DJLOVE
Full description of the hardware in the studio: contract:. Check a few things offhand and post here:
1) Bus voltage 12V
08.10.2010, 17:00
leon534, Full description of hardware for the studio (http://www.djlove.com.ru/bpmclub.htm)
1) Bus voltage 12V
2) Have you tried changing the IDE cable?
3) Have you tried Victoria or Mhdd to check your disk?
1. I don’t know where to watch this
2. no possibility, there is only one on the board
3. I haven’t tried it yet, I’m unfamiliar with this software
Does it start when cold?
sometimes yes, sometimes no
08.10.2010, 18:12
2. no possibility, there is only one question on the board. The question was not about the connector, but about the cable (flat cable connecting the drive to the motherboard).
You can first look at the voltage programmatically (with the same Everest), and then with a regular voltmeter on any free power connector from the power supply (12 volts is yellow, ground is black).
Most likely it will not reach the third point.
08.10.2010, 18:41
I changed the cable, same as the tire, it didn’t help.
went to check the temperature and voltage
09.10.2010, 00:24
I took a quick look at your zoo.
Briefly, motherboard ASRock ALiveNF7G-HDready, CPU AMD Athlon 64 X2 4200+
HDD WDC WD5000AAKS-00A7B0 SATA2
HDD Maxtor 6Y200M0 SATA
Regarding the latest hard drive, even ASTRA32 (a pensioner) says:
HDD Temperature 55 C (131 F), Remapped Sectors 273, HDD Reliability Status Poor
What you do with this zoo is up to you, of course. My personal opinion is to buy another SATA II drive, remove the ExcelStor Technology J680, and throw out the Maxtor 6Y200M0.
09.10.2010, 00:49
Maxtor 6Y200M0 has nothing to do with it, I installed it just to replace the HDD ExcelStor Technology J680 which hangs on one (only) IDE cable with DVD-RW, and I noticed that it was acting up
ExcelStor doesn’t bother me so much, what bothers me is the fact that the IDE is completely “turned off”, that is, the CD-DVD cannot start in any way even if you switch completely to SATA. When this IDE glitch appears, even if the ExcelStor hard drive is disconnected from the bus and power, even the drive is invisible
After cleaning the dust, starting the case fan and various fiddling around, at first glance the computer started working. I checked: turn it off, turn it on, restart, it seems to start normally.
There is only one explanation for this - dust and overheating. But in the morning I turned it on and again 25, only this time one restart was enough for all IDE devices to appear again.
11.10.2010, 01:58
Most likely there is a problem with the motherboard. It is over 3 years old and there is no longer any guarantee. If there are no blown capacitors on it, shouldn’t it be replaced with a similar one (http://www.nix.ru/autocatalog/motherboards_asustek/ASUS_M2A74AM_SI_SocketAM2_AMD_740G_PCIE_DVI_SATA_RAID_MicroATX_2DDRII_ 93192.html)? The issue price is $60.
29.10.2010, 14:17
Most likely there is a problem with the motherboard. It is more than 3 years old and there is no longer any guarantee. If there are no blown capacitors on it, shouldn't it be replaced with a similar one? The issue price is $60.
There were 4 identical computers at work. And the motherboards in them died the same way - the integrated network card failed, I installed a PCI network card, the computer worked for a week, then in the morning it didn’t turn on at all.
Your version, it seems to me, is closer to the truth, but I have doubts, since everything works in a fixed way and sometimes seizures like this just appear. I would have changed the motherboard a long time ago, but I don’t have 60 bucks at the moment.
Today, for example, after three weeks of trouble-free operation,
I turned on the computer and again it does not see both devices hanging on the IDE. The hard drive is working, the DVD is working, from here I have only one conclusion: everything that controls them is faulty.
Is there any software that checks for IDE or IDE controller failures?
PS: neither the tires are flat, nor dust nor overheating were the cause
02.11.2010, 23:43
And so the anomaly repeated itself, 3 weeks later
for reasons unknown to me, everything that hangs on the IDE (maybe the IDE controller itself?) again refused to start, as if the IDE did not exist.
I've been having exactly the same problem for two or three weeks now. If you don’t really believe in coincidences, maybe because of a Windows update, something might start to work incorrectly (I have a seven, it updates automatically). I also noticed that if Windows takes longer to load than usual, then everything that hangs on the IDE will not even be visible.
Besides, it happens that everything that hangs on the IDE can turn off during operation. In short, if you have any thoughts, let me know, I’ll try to clean the system unit tomorrow, it seemed to help you for three weeks.
P.S. On one of the forums I read an assumption that maybe Starforce could somehow interfere.
03.11.2010, 00:35
I also noticed that if Windows takes longer to load than usual, then everything that hangs on the IDE will not even be visible.
Actually, even before loading Windows, I still don’t see the IDE in the BIOS
05.11.2010, 12:03
Actually, even before loading Windows, I still don’t see the IDE in the BIOS
I have the same thing. nothing helps me. I also remember that I was fiddling with memory allocation, after I threw out one stick and only 3 gigs remained. you haven't done anything like that?
05.11.2010, 12:32
no, I didn’t touch the memory
3GB SD DDR hangs as it was
25.11.2010, 00:49
not even a year has passed
again the same glitch!!
It doesn’t matter to me anymore whether it can be repaired or not (I’ll buy a new motherboard)
But I would still like to understand why the computer works fine for a month and suddenly the IDE goes offline again, without any symptoms or reasons????
25.11.2010, 02:42
but I would still like to understand why the computer works fine for a month and suddenly the IDE goes offline again
Based on the topic, I don’t understand what motherboard the whole thing is on (ASRock ALiveNF7G-HDready?), but such glitches could be. associated with a dying tablet (battery on the motherboard) or power supply
Of course, many reasons can be listed. But it’s better to start with a tablet and see what kind of power supply you’re working with. If it is Chinese, with paper wool, then the capacitors may dry out and not provide the necessary power.
25.11.2010, 19:20
exactly she, ASRock ALiveNF7G-HDready
Such glitches may be associated with a dying tablet (battery on the motherboard) or power supply
you are the first to bring up this reason,
changed the tablet, changed the power supply - no change
Overheating of the south bridge, if it has not been vacuumed for a long time or poor cooling.
With cooling everything seems to be ok, dust is blown out periodically
Internal break in IDE cable
Tried different cables, same result
25.11.2010, 21:38
that is, you need to try replacing the tablet or BP
replace the tablet, and give more information here
- BP - company, model, power
- computer config (Proc, video, hard)
For now, I'm assuming that you don't have enough power when polling devices during loading.
My preferences do not include Asrock as a motherboard developer and Nvidev chipsets as the basis of a computer. I collect with other brands.
25.11.2010, 22:04
I repeat,
The tablet was replaced by zero use (BP is the same)
system data in brief
Motherboard ASRock ALiveNF7G-HDready, CPU AMD Athlon 64 X2 4200+
HDD ExcelStor Technology J680 hangs on the same IDE cable with DVD-RW
HDD WDC WD5000AAKS-00A7B0 on SATA
video VAPOR-X HD4850 (Sapphire)
BP-1: 500Watts PSU L&C-B500E
BP-2: MI-ATX400
Completely complete system data
http://www.djlove.com.ru/bpmclub.htm
26.11.2010, 00:12
DJLOVE
The 1st power supply is quite decent, the 2nd is so-so, but it should be enough to determine the hard drive.
There remains the option of overheating the south bridge. This is confirmed by SMART ExcelStor Technology J680 Parameter 199 Errors in UDMA transmission mode = 88, Difference from ZERO is already bad. But you need to understand how the parameter changed over time, which affects the appearance of the error. Formally, this is an interface error, which means the cause is the cable or the controller (i.e., the MCP hot south bridge)
Regarding the train. This was a long time ago and I can forget the details, but in theory, if the hard drive supports UDMA mode - UltraDMA/100, and Active: 2 (UltraDMA/33), then this means that you have a 40-wire LOAD (UltraDMA/33) , and d.b. 80(UltraDMA/100)
Added after 14 minutes
In continuation of your analysis http://www.djlove.com.ru/bpmclub.htm
The Maxtor 6Y200M0 drive will die soon. His SMART is disgusting. Copy the data immediately.
Change the cooling in the case, because it seems that there is no blower fan, because... Maxtor's current temperature is 55 degrees, which means that the computer's cooling is not built correctly
Added after 30 minutes
As Alice said: “more and more wonderful and more wonderful..”
In the description of your ASRock ALiveNF7G-HDready motherboard (http://www.asrock.com/mb/overview.asp?Model=ALIVENF7G-HDREADY) there is NO VT6421 controller
Your link http://www.djlove.com.ru/bpmclub.htm clearly states that the ExcelStor Technology J680 drive sits on a VT6421 IDE RAID Controller
If the manufacturer (ASRock) deceived you and the IDE is supported not by MCP 67, but by VT6421, then it’s clear why you don’t see your IDE hard in the BIOS.
Because drivers for VIA are not installed, then during operation the controller does not provide normal UltraDMA/100 speed
In general, I didn’t like Asrock and now I’ll never like it again :)))
Added after 9 minutes
PS. By the way, if the disk sits on a VT6421, then it’s clear where so many problems come from - http://forum.ixbt.com/topic.cgi?id=4:89954
26.11.2010, 01:43
Prod. ATA controller VIA Technologies Inc
ATA controller name VT6421 IDE RAID Controller
Looks like you're onto something
And really, why is the MASTER HDD hanging on this non-existent controller, that is, not connected at all?
I tried to install VT6421 a long time ago, but it didn’t work. There are probably still “scars” of this attempt in the windows. But no device physically hangs on it, and the VT6421 controller itself has long been lying around somewhere to the side.
BUT IT WORKED FOR THE SAME MONTH, which means it was defined as this:idontnow:
There remains the option of overheating the south bridge
That is, a fatal outcome due to overheating? or what do you mean? Well, what about the process itself, interruption-work-interruption, if it would burn out, it would burn out, but now I’m working, and then I’m not. Yes, and when starting from the “cold” I didn’t find it either.
The Maxtor 6Y200M0 disk died during the first analysis a month ago. Thank you: beer: I wasn’t worried about him
I saw that the memory sticks are different. Are the timings consistent in Bios? Have there been any attempts to boot computers by pulling out the straps?
there were no such attempts,
no one looked at the timings, it works according to the “stick it in, plow, everything is ok” system
26.11.2010, 02:19
That is, a fatal outcome due to overheating?
there is overheating, because Maxtor died for a reason. If there has been overheating for a long time, then, as with any temperature increase, you have worn out the resource and now, as soon as a load appears on the controller, glitches appear. These are precisely glitches, which are always difficult to diagnose, and not a complete hardware failure
And how, most importantly, to redirect specifically to the mother IDE controller?
Now we need to build normal access via the IDE.
The simplest (and most correct) thing is to demolish the system and install it from scratch. If you want to fix it, then make an image (Acronis, Ghost) and start experimenting.
Prepare nVidia drivers, call Device Manager, see who is hanging on the IDE ATA/ATAPI controllers. You should see which driver is hanging on the IDE and go from there.
PS. This is a preliminary summary - out of purely sporting interest :) - it can be fixed. when preparing the correct drivers, work for 20 minutes. But it's better to go another way
-change the motherboard (to Gigabyte, Asus)
- fix the cooling (intake fan, case, if it doesn’t have a seat for a fan on the front panel, and maybe something else),
- change the IDE hard drive to SATA,
- coordinate memory strips in frequency and volume (dual channel is lost)
- etc. etc.
26.11.2010, 12:55
Now we need to build normal access via the IDE.
The simplest (and most correct) is to demolish the system and install from scratch
I can’t install anything in any way, since I don’t have the installation Flash, and this, in theory, is the only way to install something without an IDE.
Change IDE hard drive to SATA,
Even when everything was working, the fix always got the same failure during installation, it was reported that it was impossible to install WINXP on this HDD
Whatever one may say, I return to the same conclusion
- change motherboard
26.11.2010, 13:07
I can’t install anything because I don’t have...
there are 101 ways to install all this, starting from rolling a pre-prepared system with pre-installed drivers onto a hard drive, to forcing a driver update via Device Manager or changing the ATA controller to PCI IDE manually (and then to the correct one), using Paragon HDM, Acronis UR, etc......
But if you decide to change your motherboard, then change it and forget about these problems, because... New mother will have new problems...
"But that's a completely different story..."
PS. It's interesting that your AMD Athlon 64 X2 4200+ Brisbane is supported starting with Bios ver. 1.70, and yours is 1.20
At a minimum, you need to update the BIOS to the latest version - http://www.asrock.com/mb/download.ru.asp?Model=ALiveNF7G-HDready&o=BIOS, and this, if the motherboard is alive and just buggy, can revive the system
28.01.2011, 23:51
Guys, I have the following problem: the motherboard stopped working, I changed it to http://www.nix.ru/autocatalog/motherboards_elitegroup/EliteGroup_P965TA_rev1.0_LGA775_P965_2xPCIE_SATA_RAID_4DDRII_PC26400_5 5268.html, now I wanted to install a new Windows, but nothing is defined in the BIOS, no IDE 80GB hard drive, no DVD-RW. From hardware, Rentium 4,630 percent, memory stick 512MB, pc2-5300. When you start installing Windows, information is displayed on the screen on a black background, and there is also no word about hard drive and Sidi ROM, then the light on the Sidi ROM starts blinking (as if the installation had started) and immediately goes out (although in the BIOS I set first boot devaice costs CD-ROM, second hard drive). All. The system offers to choose how to boot (safe mode, normal boot, etc.) from the old Windows. then a blue screen.
Can you tell me what’s wrong with this mother? Or maybe something needs to be set in the BIOS settings? I bought the mother used, not new.
Thanks in advance for your help!