BIOS not detecting working SATA hard drive
Some time ago my power supply died. It's a long story from then till now, but the important bit is that I ended up with a new hard drive and a new power supply. I tested to see if my original hard drive was still alive, and it booted and worked perfectly until I turned it off. When I started it again it would not boot. I bought new SATA cables, assuming that the one I had was not seating properly (it was cheap and wobbly), but no dice.
Upon start-up I am presented with a message telling me to insert boot media into the selected drive or add a drive and restart. Neither the new or the old drive is detected by BIOS, my Vista install disk, or from my bootable Linux USB drive. When I remove all of the RAM the computer ceases outputting visual information, and upon reinstalling the ram and starting up again gives me a "failed overclock" error.
So, does anyone have an idea as to what might be going on? I'm completely lost at this point.
hard-drive boot bios hardware-failure sata
edited Feb 4 '15 at 8:46
pulsarjune
1,2121921
add a comment |
Some time ago my power supply died. It's a long story from then till now, but the important bit is that I ended up with a new hard drive and a new power supply. I tested to see if my original hard drive was still alive, and it booted and worked perfectly until I turned it off. When I started it again it would not boot. I bought new SATA cables, assuming that the one I had was not seating properly (it was cheap and wobbly), but no dice.
Upon start-up I am presented with a message telling me to insert boot media into the selected drive or add a drive and restart. Neither the new or the old drive is detected by BIOS, my Vista install disk, or from my bootable Linux USB drive. When I remove all of the RAM the computer ceases outputting visual information, and upon reinstalling the ram and starting up again gives me a "failed overclock" error.
So, does anyone have an idea as to what might be going on? I'm completely lost at this point.
hard-drive boot bios hardware-failure sata
edited Feb 4 '15 at 8:46
pulsarjune
1,2121921
Are you using 1.5, 3 or 6 Gb/s SATA connection? I had a problem where my drive wasn't detected until I changed from 6 to 3 - dunno how relevant this is to you.
– Pubby
Oct 12 '11 at 0:37
Your hard drive is toast. RMA if you can, chuck it if you can't.
– Sammitch
May 14 '13 at 21:54
add a comment |
Some time ago my power supply died. It's a long story from then till now, but the important bit is that I ended up with a new hard drive and a new power supply. I tested to see if my original hard drive was still alive, and it booted and worked perfectly until I turned it off. When I started it again it would not boot. I bought new SATA cables, assuming that the one I had was not seating properly (it was cheap and wobbly), but no dice.
Upon start-up I am presented with a message telling me to insert boot media into the selected drive or add a drive and restart. Neither the new or the old drive is detected by BIOS, my Vista install disk, or from my bootable Linux USB drive. When I remove all of the RAM the computer ceases outputting visual information, and upon reinstalling the ram and starting up again gives me a "failed overclock" error.
So, does anyone have an idea as to what might be going on? I'm completely lost at this point.
hard-drive boot bios hardware-failure sata
edited Feb 4 '15 at 8:46
pulsarjune
1,2121921
Some time ago my power supply died. It's a long story from then till now, but the important bit is that I ended up with a new hard drive and a new power supply. I tested to see if my original hard drive was still alive, and it booted and worked perfectly until I turned it off. When I started it again it would not boot. I bought new SATA cables, assuming that the one I had was not seating properly (it was cheap and wobbly), but no dice.
Upon start-up I am presented with a message telling me to insert boot media into the selected drive or add a drive and restart. Neither the new or the old drive is detected by BIOS, my Vista install disk, or from my bootable Linux USB drive. When I remove all of the RAM the computer ceases outputting visual information, and upon reinstalling the ram and starting up again gives me a "failed overclock" error.
So, does anyone have an idea as to what might be going on? I'm completely lost at this point.
hard-drive boot bios hardware-failure sata
hard-drive boot bios hardware-failure sata
edited Feb 4 '15 at 8:46
pulsarjune
1,2121921
edited Feb 4 '15 at 8:46
pulsarjune
1,2121921
edited Feb 4 '15 at 8:46
pulsarjune
1,2121921
edited Feb 4 '15 at 8:46
pulsarjune
1,2121921
edited Feb 4 '15 at 8:46
pulsarjune
1,2121921
1,2121921
asked Feb 21 '10 at 7:24
user28927
Are you using 1.5, 3 or 6 Gb/s SATA connection? I had a problem where my drive wasn't detected until I changed from 6 to 3 - dunno how relevant this is to you.
– Pubby
Oct 12 '11 at 0:37
Your hard drive is toast. RMA if you can, chuck it if you can't.
– Sammitch
May 14 '13 at 21:54
add a comment |
Are you using 1.5, 3 or 6 Gb/s SATA connection? I had a problem where my drive wasn't detected until I changed from 6 to 3 - dunno how relevant this is to you.
– Pubby
Oct 12 '11 at 0:37
Your hard drive is toast. RMA if you can, chuck it if you can't.
– Sammitch
May 14 '13 at 21:54
Are you using 1.5, 3 or 6 Gb/s SATA connection? I had a problem where my drive wasn't detected until I changed from 6 to 3 - dunno how relevant this is to you.
– Pubby
Oct 12 '11 at 0:37
Are you using 1.5, 3 or 6 Gb/s SATA connection? I had a problem where my drive wasn't detected until I changed from 6 to 3 - dunno how relevant this is to you.
– Pubby
Oct 12 '11 at 0:37
Your hard drive is toast. RMA if you can, chuck it if you can't.
– Sammitch
May 14 '13 at 21:54
Your hard drive is toast. RMA if you can, chuck it if you can't.
– Sammitch
May 14 '13 at 21:54
add a comment |
5 Answers
5
active
oldest
votes
Is your hard drive one of the ready to fail Seagate drives? I had a problem very similar. Was working until I turned the machine off and the bamb the drive was gone. I later got it replaced as Seagate had a firmware problem that killed hard drives. There is information on their site so you can check out weather your drive is effected or not.
A computer is never going to boot with no memory and the error about failed overclock is likely because the system knows it started but couldn't successfully POST.
Cheers
answered Feb 21 '10 at 13:33
Hadyn
393
1
I don't think so, both of my drives are manufactured by Western Digital. Any other ideas?
– user28927
Feb 22 '10 at 0:56
The initial spin-up cycle of hard drive stresses them, and they draw more power during that time. It's possible a teetering hard drive could kick the bucket at that point. If it doesn't work in another system you are looking at things like trying to replace the PCB on the drive or professional, expensive data recovery.
– LawrenceC
Jun 24 '14 at 12:10
add a comment |
Are you sure that the drive is good? Have you tested it on another system? It could be that the drive has also failed... Unlikely, but a bad power suppy can damage anything plugged into it...
Also check your motherboard's bios for drive settings, see if there is a legacy mode for the sata drive. Try that setting....
answered Feb 23 '10 at 13:20
Benjamin Schollnick
4,2131215
Well, I suppose it is possible that the drive failed after using it for an hour on the new power supply, and that my new drive is defective, but I haven't got the resources to test that at the moment. As for the SATA legacy mode, I'm not seeing such a setting in my BIOS. Is it likely that I'm missing this, and if so where is it hiding?
– user28927
Feb 26 '10 at 7:16
What Bios do you have?
– Benjamin Schollnick
Feb 27 '10 at 22:37
American Megatrends AMIBIOs v2.6.
– user28927
Mar 2 '10 at 20:58
A cheap way to test the drive is a SATA to USB adapter or dock, which you can usually find for less than $20. If it's a 3.5" drive, you'll need a powered adapter.
– rob
Jan 20 '14 at 23:35
add a comment |
SATA legacy mode can be under many forms. It can be called IDE mode, legacy mode, NON-SATA mode
Is your ODD (CD/DVD unit) detected correctly ?
If yes, try to disconnect it and put a hard drive on that SATA port, assuming the ODD is also SATA.
answered Feb 4 '15 at 9:25
Overmind
7,83331531
regardless of legacy mode or regular AHCI mode, the BIOS should still detect the drive. If it does not that either drive, cable, power or controller are dead.
– Hennes
Dec 22 '15 at 8:45
add a comment |
Some BIOSes show UEFI hard drives in separate places from legacy hard drives, so it may not show up in the place you expect.
answered Aug 10 '17 at 19:25
Christopher Hostage
3,291928
add a comment |
When a disk is not detected in the BIOS it usually means that:
- Either it does not get proper power.
- Or the data cable is not connected.
- Or the data cable is broken.
- Or the disk is broken.
- or the controller/port on the motherboard is broken.
Testing 1) is easy. If its gets power it will spin up*1. No new data cables are needed, and you can swap power cables around to test with.
Or the data cable is not connected/broken.... Obviously not the case here, but listed for completeness.
Or the disk is broken... Possible. If it was just one drive then it was even likely. Some time ago my power supply died. this however add the option that the disk was damaged and died a bit later, doing damage whilest dying.
Neither the new or the old drive is detected by BIOS
That shounds like a SATA controller failure. Either damaged, or disabled in the BIOS. You could try restoring the BIOS to default, if it was disabled it should detect the drives*2.
*1: Not always true. But since we are dealing with a regular setup and not with servers this is true enough.
*2: Ignore anything about normal SATA mode (AHCI), legacy mode or RAID modes. The drives should be detected. Those settings are only important once you try booting from the disk, but right not we first want the firmware (BIOS) to actually detect the disk.
answered Dec 22 '15 at 8:58
Hennes
58.8k792141
OP may also try it on another disk or using a SATA adapter to plug it on a USB port...
– Alfabravo
Oct 13 '17 at 21:14
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f111477%2fbios-not-detecting-working-sata-hard-drive%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
Is your hard drive one of the ready to fail Seagate drives? I had a problem very similar. Was working until I turned the machine off and the bamb the drive was gone. I later got it replaced as Seagate had a firmware problem that killed hard drives. There is information on their site so you can check out weather your drive is effected or not.
A computer is never going to boot with no memory and the error about failed overclock is likely because the system knows it started but couldn't successfully POST.
Cheers
answered Feb 21 '10 at 13:33
Hadyn
393
1
I don't think so, both of my drives are manufactured by Western Digital. Any other ideas?
– user28927
Feb 22 '10 at 0:56
The initial spin-up cycle of hard drive stresses them, and they draw more power during that time. It's possible a teetering hard drive could kick the bucket at that point. If it doesn't work in another system you are looking at things like trying to replace the PCB on the drive or professional, expensive data recovery.
– LawrenceC
Jun 24 '14 at 12:10
add a comment |
Is your hard drive one of the ready to fail Seagate drives? I had a problem very similar. Was working until I turned the machine off and the bamb the drive was gone. I later got it replaced as Seagate had a firmware problem that killed hard drives. There is information on their site so you can check out weather your drive is effected or not.
A computer is never going to boot with no memory and the error about failed overclock is likely because the system knows it started but couldn't successfully POST.
Cheers
answered Feb 21 '10 at 13:33
Hadyn
393
1
I don't think so, both of my drives are manufactured by Western Digital. Any other ideas?
– user28927
Feb 22 '10 at 0:56
The initial spin-up cycle of hard drive stresses them, and they draw more power during that time. It's possible a teetering hard drive could kick the bucket at that point. If it doesn't work in another system you are looking at things like trying to replace the PCB on the drive or professional, expensive data recovery.
– LawrenceC
Jun 24 '14 at 12:10
add a comment |
Is your hard drive one of the ready to fail Seagate drives? I had a problem very similar. Was working until I turned the machine off and the bamb the drive was gone. I later got it replaced as Seagate had a firmware problem that killed hard drives. There is information on their site so you can check out weather your drive is effected or not.
A computer is never going to boot with no memory and the error about failed overclock is likely because the system knows it started but couldn't successfully POST.
Cheers
answered Feb 21 '10 at 13:33
Hadyn
393
Is your hard drive one of the ready to fail Seagate drives? I had a problem very similar. Was working until I turned the machine off and the bamb the drive was gone. I later got it replaced as Seagate had a firmware problem that killed hard drives. There is information on their site so you can check out weather your drive is effected or not.
A computer is never going to boot with no memory and the error about failed overclock is likely because the system knows it started but couldn't successfully POST.
Cheers
answered Feb 21 '10 at 13:33
Hadyn
393
answered Feb 21 '10 at 13:33
Hadyn
393
answered Feb 21 '10 at 13:33
Hadyn
393
answered Feb 21 '10 at 13:33
Hadyn
393
393
1
I don't think so, both of my drives are manufactured by Western Digital. Any other ideas?
– user28927
Feb 22 '10 at 0:56
The initial spin-up cycle of hard drive stresses them, and they draw more power during that time. It's possible a teetering hard drive could kick the bucket at that point. If it doesn't work in another system you are looking at things like trying to replace the PCB on the drive or professional, expensive data recovery.
– LawrenceC
Jun 24 '14 at 12:10
add a comment |
1
I don't think so, both of my drives are manufactured by Western Digital. Any other ideas?
– user28927
Feb 22 '10 at 0:56
The initial spin-up cycle of hard drive stresses them, and they draw more power during that time. It's possible a teetering hard drive could kick the bucket at that point. If it doesn't work in another system you are looking at things like trying to replace the PCB on the drive or professional, expensive data recovery.
– LawrenceC
Jun 24 '14 at 12:10
1
1
I don't think so, both of my drives are manufactured by Western Digital. Any other ideas?
– user28927
Feb 22 '10 at 0:56
I don't think so, both of my drives are manufactured by Western Digital. Any other ideas?
– user28927
Feb 22 '10 at 0:56
The initial spin-up cycle of hard drive stresses them, and they draw more power during that time. It's possible a teetering hard drive could kick the bucket at that point. If it doesn't work in another system you are looking at things like trying to replace the PCB on the drive or professional, expensive data recovery.
– LawrenceC
Jun 24 '14 at 12:10
The initial spin-up cycle of hard drive stresses them, and they draw more power during that time. It's possible a teetering hard drive could kick the bucket at that point. If it doesn't work in another system you are looking at things like trying to replace the PCB on the drive or professional, expensive data recovery.
– LawrenceC
Jun 24 '14 at 12:10
add a comment |
Are you sure that the drive is good? Have you tested it on another system? It could be that the drive has also failed... Unlikely, but a bad power suppy can damage anything plugged into it...
Also check your motherboard's bios for drive settings, see if there is a legacy mode for the sata drive. Try that setting....
answered Feb 23 '10 at 13:20
Benjamin Schollnick
4,2131215
Well, I suppose it is possible that the drive failed after using it for an hour on the new power supply, and that my new drive is defective, but I haven't got the resources to test that at the moment. As for the SATA legacy mode, I'm not seeing such a setting in my BIOS. Is it likely that I'm missing this, and if so where is it hiding?
– user28927
Feb 26 '10 at 7:16
What Bios do you have?
– Benjamin Schollnick
Feb 27 '10 at 22:37
American Megatrends AMIBIOs v2.6.
– user28927
Mar 2 '10 at 20:58
A cheap way to test the drive is a SATA to USB adapter or dock, which you can usually find for less than $20. If it's a 3.5" drive, you'll need a powered adapter.
– rob
Jan 20 '14 at 23:35
add a comment |
Are you sure that the drive is good? Have you tested it on another system? It could be that the drive has also failed... Unlikely, but a bad power suppy can damage anything plugged into it...
Also check your motherboard's bios for drive settings, see if there is a legacy mode for the sata drive. Try that setting....
answered Feb 23 '10 at 13:20
Benjamin Schollnick
4,2131215
Well, I suppose it is possible that the drive failed after using it for an hour on the new power supply, and that my new drive is defective, but I haven't got the resources to test that at the moment. As for the SATA legacy mode, I'm not seeing such a setting in my BIOS. Is it likely that I'm missing this, and if so where is it hiding?
– user28927
Feb 26 '10 at 7:16
What Bios do you have?
– Benjamin Schollnick
Feb 27 '10 at 22:37
American Megatrends AMIBIOs v2.6.
– user28927
Mar 2 '10 at 20:58
A cheap way to test the drive is a SATA to USB adapter or dock, which you can usually find for less than $20. If it's a 3.5" drive, you'll need a powered adapter.
– rob
Jan 20 '14 at 23:35
add a comment |
Are you sure that the drive is good? Have you tested it on another system? It could be that the drive has also failed... Unlikely, but a bad power suppy can damage anything plugged into it...
Also check your motherboard's bios for drive settings, see if there is a legacy mode for the sata drive. Try that setting....
answered Feb 23 '10 at 13:20
Benjamin Schollnick
4,2131215
Are you sure that the drive is good? Have you tested it on another system? It could be that the drive has also failed... Unlikely, but a bad power suppy can damage anything plugged into it...
Also check your motherboard's bios for drive settings, see if there is a legacy mode for the sata drive. Try that setting....
answered Feb 23 '10 at 13:20
Benjamin Schollnick
4,2131215
answered Feb 23 '10 at 13:20
Benjamin Schollnick
4,2131215
answered Feb 23 '10 at 13:20
Benjamin Schollnick
4,2131215
answered Feb 23 '10 at 13:20
Benjamin Schollnick
4,2131215
4,2131215
Well, I suppose it is possible that the drive failed after using it for an hour on the new power supply, and that my new drive is defective, but I haven't got the resources to test that at the moment. As for the SATA legacy mode, I'm not seeing such a setting in my BIOS. Is it likely that I'm missing this, and if so where is it hiding?
– user28927
Feb 26 '10 at 7:16
What Bios do you have?
– Benjamin Schollnick
Feb 27 '10 at 22:37
American Megatrends AMIBIOs v2.6.
– user28927
Mar 2 '10 at 20:58
A cheap way to test the drive is a SATA to USB adapter or dock, which you can usually find for less than $20. If it's a 3.5" drive, you'll need a powered adapter.
– rob
Jan 20 '14 at 23:35
add a comment |
Well, I suppose it is possible that the drive failed after using it for an hour on the new power supply, and that my new drive is defective, but I haven't got the resources to test that at the moment. As for the SATA legacy mode, I'm not seeing such a setting in my BIOS. Is it likely that I'm missing this, and if so where is it hiding?
– user28927
Feb 26 '10 at 7:16
What Bios do you have?
– Benjamin Schollnick
Feb 27 '10 at 22:37
American Megatrends AMIBIOs v2.6.
– user28927
Mar 2 '10 at 20:58
A cheap way to test the drive is a SATA to USB adapter or dock, which you can usually find for less than $20. If it's a 3.5" drive, you'll need a powered adapter.
– rob
Jan 20 '14 at 23:35
Well, I suppose it is possible that the drive failed after using it for an hour on the new power supply, and that my new drive is defective, but I haven't got the resources to test that at the moment. As for the SATA legacy mode, I'm not seeing such a setting in my BIOS. Is it likely that I'm missing this, and if so where is it hiding?
– user28927
Feb 26 '10 at 7:16
Well, I suppose it is possible that the drive failed after using it for an hour on the new power supply, and that my new drive is defective, but I haven't got the resources to test that at the moment. As for the SATA legacy mode, I'm not seeing such a setting in my BIOS. Is it likely that I'm missing this, and if so where is it hiding?
– user28927
Feb 26 '10 at 7:16
What Bios do you have?
– Benjamin Schollnick
Feb 27 '10 at 22:37
What Bios do you have?
– Benjamin Schollnick
Feb 27 '10 at 22:37
American Megatrends AMIBIOs v2.6.
– user28927
Mar 2 '10 at 20:58
American Megatrends AMIBIOs v2.6.
– user28927
Mar 2 '10 at 20:58
A cheap way to test the drive is a SATA to USB adapter or dock, which you can usually find for less than $20. If it's a 3.5" drive, you'll need a powered adapter.
– rob
Jan 20 '14 at 23:35
A cheap way to test the drive is a SATA to USB adapter or dock, which you can usually find for less than $20. If it's a 3.5" drive, you'll need a powered adapter.
– rob
Jan 20 '14 at 23:35
add a comment |
SATA legacy mode can be under many forms. It can be called IDE mode, legacy mode, NON-SATA mode
Is your ODD (CD/DVD unit) detected correctly ?
If yes, try to disconnect it and put a hard drive on that SATA port, assuming the ODD is also SATA.
answered Feb 4 '15 at 9:25
Overmind
7,83331531
regardless of legacy mode or regular AHCI mode, the BIOS should still detect the drive. If it does not that either drive, cable, power or controller are dead.
– Hennes
Dec 22 '15 at 8:45
add a comment |
SATA legacy mode can be under many forms. It can be called IDE mode, legacy mode, NON-SATA mode
Is your ODD (CD/DVD unit) detected correctly ?
If yes, try to disconnect it and put a hard drive on that SATA port, assuming the ODD is also SATA.
answered Feb 4 '15 at 9:25
Overmind
7,83331531
regardless of legacy mode or regular AHCI mode, the BIOS should still detect the drive. If it does not that either drive, cable, power or controller are dead.
– Hennes
Dec 22 '15 at 8:45
add a comment |
SATA legacy mode can be under many forms. It can be called IDE mode, legacy mode, NON-SATA mode
Is your ODD (CD/DVD unit) detected correctly ?
If yes, try to disconnect it and put a hard drive on that SATA port, assuming the ODD is also SATA.
answered Feb 4 '15 at 9:25
Overmind
7,83331531
SATA legacy mode can be under many forms. It can be called IDE mode, legacy mode, NON-SATA mode
Is your ODD (CD/DVD unit) detected correctly ?
If yes, try to disconnect it and put a hard drive on that SATA port, assuming the ODD is also SATA.
answered Feb 4 '15 at 9:25
Overmind
7,83331531
answered Feb 4 '15 at 9:25
Overmind
7,83331531
answered Feb 4 '15 at 9:25
Overmind
7,83331531
answered Feb 4 '15 at 9:25
Overmind
7,83331531
7,83331531
regardless of legacy mode or regular AHCI mode, the BIOS should still detect the drive. If it does not that either drive, cable, power or controller are dead.
– Hennes
Dec 22 '15 at 8:45
add a comment |
regardless of legacy mode or regular AHCI mode, the BIOS should still detect the drive. If it does not that either drive, cable, power or controller are dead.
– Hennes
Dec 22 '15 at 8:45
regardless of legacy mode or regular AHCI mode, the BIOS should still detect the drive. If it does not that either drive, cable, power or controller are dead.
– Hennes
Dec 22 '15 at 8:45
regardless of legacy mode or regular AHCI mode, the BIOS should still detect the drive. If it does not that either drive, cable, power or controller are dead.
– Hennes
Dec 22 '15 at 8:45
add a comment |
Some BIOSes show UEFI hard drives in separate places from legacy hard drives, so it may not show up in the place you expect.
answered Aug 10 '17 at 19:25
Christopher Hostage
3,291928
add a comment |
Some BIOSes show UEFI hard drives in separate places from legacy hard drives, so it may not show up in the place you expect.
answered Aug 10 '17 at 19:25
Christopher Hostage
3,291928
add a comment |
Some BIOSes show UEFI hard drives in separate places from legacy hard drives, so it may not show up in the place you expect.
answered Aug 10 '17 at 19:25
Christopher Hostage
3,291928
Some BIOSes show UEFI hard drives in separate places from legacy hard drives, so it may not show up in the place you expect.
answered Aug 10 '17 at 19:25
Christopher Hostage
3,291928
answered Aug 10 '17 at 19:25
Christopher Hostage
3,291928
answered Aug 10 '17 at 19:25
Christopher Hostage
3,291928
answered Aug 10 '17 at 19:25
Christopher Hostage
3,291928
3,291928
add a comment |
add a comment |
When a disk is not detected in the BIOS it usually means that:
- Either it does not get proper power.
- Or the data cable is not connected.
- Or the data cable is broken.
- Or the disk is broken.
- or the controller/port on the motherboard is broken.
Testing 1) is easy. If its gets power it will spin up*1. No new data cables are needed, and you can swap power cables around to test with.
Or the data cable is not connected/broken.... Obviously not the case here, but listed for completeness.
Or the disk is broken... Possible. If it was just one drive then it was even likely. Some time ago my power supply died. this however add the option that the disk was damaged and died a bit later, doing damage whilest dying.
Neither the new or the old drive is detected by BIOS
That shounds like a SATA controller failure. Either damaged, or disabled in the BIOS. You could try restoring the BIOS to default, if it was disabled it should detect the drives*2.
*1: Not always true. But since we are dealing with a regular setup and not with servers this is true enough.
*2: Ignore anything about normal SATA mode (AHCI), legacy mode or RAID modes. The drives should be detected. Those settings are only important once you try booting from the disk, but right not we first want the firmware (BIOS) to actually detect the disk.
answered Dec 22 '15 at 8:58
Hennes
58.8k792141
OP may also try it on another disk or using a SATA adapter to plug it on a USB port...
– Alfabravo
Oct 13 '17 at 21:14
add a comment |
When a disk is not detected in the BIOS it usually means that:
- Either it does not get proper power.
- Or the data cable is not connected.
- Or the data cable is broken.
- Or the disk is broken.
- or the controller/port on the motherboard is broken.
Testing 1) is easy. If its gets power it will spin up*1. No new data cables are needed, and you can swap power cables around to test with.
Or the data cable is not connected/broken.... Obviously not the case here, but listed for completeness.
Or the disk is broken... Possible. If it was just one drive then it was even likely. Some time ago my power supply died. this however add the option that the disk was damaged and died a bit later, doing damage whilest dying.
Neither the new or the old drive is detected by BIOS
That shounds like a SATA controller failure. Either damaged, or disabled in the BIOS. You could try restoring the BIOS to default, if it was disabled it should detect the drives*2.
*1: Not always true. But since we are dealing with a regular setup and not with servers this is true enough.
*2: Ignore anything about normal SATA mode (AHCI), legacy mode or RAID modes. The drives should be detected. Those settings are only important once you try booting from the disk, but right not we first want the firmware (BIOS) to actually detect the disk.
answered Dec 22 '15 at 8:58
Hennes
58.8k792141
OP may also try it on another disk or using a SATA adapter to plug it on a USB port...
– Alfabravo
Oct 13 '17 at 21:14
add a comment |
When a disk is not detected in the BIOS it usually means that:
- Either it does not get proper power.
- Or the data cable is not connected.
- Or the data cable is broken.
- Or the disk is broken.
- or the controller/port on the motherboard is broken.
Testing 1) is easy. If its gets power it will spin up*1. No new data cables are needed, and you can swap power cables around to test with.
Or the data cable is not connected/broken.... Obviously not the case here, but listed for completeness.
Or the disk is broken... Possible. If it was just one drive then it was even likely. Some time ago my power supply died. this however add the option that the disk was damaged and died a bit later, doing damage whilest dying.
Neither the new or the old drive is detected by BIOS
That shounds like a SATA controller failure. Either damaged, or disabled in the BIOS. You could try restoring the BIOS to default, if it was disabled it should detect the drives*2.
*1: Not always true. But since we are dealing with a regular setup and not with servers this is true enough.
*2: Ignore anything about normal SATA mode (AHCI), legacy mode or RAID modes. The drives should be detected. Those settings are only important once you try booting from the disk, but right not we first want the firmware (BIOS) to actually detect the disk.
answered Dec 22 '15 at 8:58
Hennes
58.8k792141
When a disk is not detected in the BIOS it usually means that:
- Either it does not get proper power.
- Or the data cable is not connected.
- Or the data cable is broken.
- Or the disk is broken.
- or the controller/port on the motherboard is broken.
Testing 1) is easy. If its gets power it will spin up*1. No new data cables are needed, and you can swap power cables around to test with.
Or the data cable is not connected/broken.... Obviously not the case here, but listed for completeness.
Or the disk is broken... Possible. If it was just one drive then it was even likely. Some time ago my power supply died. this however add the option that the disk was damaged and died a bit later, doing damage whilest dying.
Neither the new or the old drive is detected by BIOS
That shounds like a SATA controller failure. Either damaged, or disabled in the BIOS. You could try restoring the BIOS to default, if it was disabled it should detect the drives*2.
*1: Not always true. But since we are dealing with a regular setup and not with servers this is true enough.
*2: Ignore anything about normal SATA mode (AHCI), legacy mode or RAID modes. The drives should be detected. Those settings are only important once you try booting from the disk, but right not we first want the firmware (BIOS) to actually detect the disk.
answered Dec 22 '15 at 8:58
Hennes
58.8k792141
edited Oct 14 '17 at 19:08
answered Dec 22 '15 at 8:58
Hennes
58.8k792141
answered Dec 22 '15 at 8:58
Hennes
58.8k792141
answered Dec 22 '15 at 8:58
Hennes
58.8k792141
58.8k792141
OP may also try it on another disk or using a SATA adapter to plug it on a USB port...
– Alfabravo
Oct 13 '17 at 21:14
add a comment |
OP may also try it on another disk or using a SATA adapter to plug it on a USB port...
– Alfabravo
Oct 13 '17 at 21:14
OP may also try it on another disk or using a SATA adapter to plug it on a USB port...
– Alfabravo
Oct 13 '17 at 21:14
OP may also try it on another disk or using a SATA adapter to plug it on a USB port...
– Alfabravo
Oct 13 '17 at 21:14
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f111477%2fbios-not-detecting-working-sata-hard-drive%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Are you using 1.5, 3 or 6 Gb/s SATA connection? I had a problem where my drive wasn't detected until I changed from 6 to 3 - dunno how relevant this is to you.
– Pubby
Oct 12 '11 at 0:37
Your hard drive is toast. RMA if you can, chuck it if you can't.
– Sammitch
May 14 '13 at 21:54