BIOS and Windows 10 cannot use/detect/initialize Hard drive while Linux can (tried NTFS/FAT file systems and...
OS: Windows 10 Enterprise
Motherboard: MSI Z87-G45
HDD: Western Digital 1TB Black WD1003FZEX
Hello, first post on here but this site, among many other StackExchange sites have been an infinite wealth of knowledge to me for years so thanks for that. I apologize if I don't have formatting down too well.
I'm having a problem with my hard drive that I really feel like I'm at a dead end with.
I recently got an SSD and installed it into my PC. At this point I had 3 drives. 1 SSD and 2 HDDs. After plugging all 3 drives in, I started getting signs of my power supply getting finicky. This had also happened previously when I had 3 HDDs installed at the same time. The PC would randomly shut off/restart, my motherboard would go into its protective mode which made it where the PC would not power on until I unplugged and re-plugged the power supply cable to the motherboard. So I took it as a sign, while everything was still intact, to unplug my least used HDD and leave it be until I upgraded PSUs. So I unplugged the HDD and just left it in my case. About a week later I go ahead and get a new PSU, it's a EVGA 850w G3 and I hooked it up with seemingly perfect success. I power it on, and everything seems fine, except one thing, which is Windows isn't showing my 3rd drive at all. I reboot a couple of times and check my bios (it wasn't showing up there either) and eventually it does show up, but it's unreadable. Explorer completely hangs whenever I try to access the drive in any way imaginable.
So I figured the drive was corrupted and I thought I'd do my best to recover anything I could so I threw SystemRescueCd onto a USB stick and booted into it expecting to use ddRescue and Testdisk to try and get at least something off of the drive. Out of curiosity, I attempted to mount the drive, and to my surprise it worked. It popped up a message claiming something about windows metadata, hibernation, and that it could only be accessed in read-only mode, but it mounted nonetheless. So I backed up the entire drive to an external HDD without any issue. All files fully functional and intact.
At this point, I figured I would just attempt to delete the two partitions on the drive and create a new one. So I used gparted to delete and then create an NTFS partition, and once again, everything worked. I mounted this new partition without issue, and this time I could read and write to it without any problem. I reboot, check BIOS (still not there). I boot into windows, still not there. So I boot back into SystemRescueCd and I try to rewrite the partition table. First I tried GPT, then I tried MBR. I tried doing this with Gparted, and then with testdisk. Nothing changed. However now, when I go into Disk Management on Windows, it will sometimes show a Disk 0, and it'll claim it's
not initialized
If I try to initialize it with MBR, it'll say "incorrect function" and if I do GPT it'll have a message claiming
The specified disk is not convertible because the size is less than the minimum size required for GPT disks
If I look at drive 0 in Diskpart it shows it having 0GB. As a last ditch effort, I tried completely clearing the drive with DD, filling it with /dev/zero, then creating a new partition table using gparted. Still nothing, with the exact same Not Initialized issue and errors.
So now I'm just confused. Why can I use this drive completely normally on linux, but not even my BIOS can read it? I could understand a corrupted partition table hampering things but I've done my best to reset that. Could this happen with a hardware issue? It just doesn't make sense to me that it's completely fine when I use a Linux distro. Prior to all of this, the drive appeared completely healthy. I check S.M.A.R.T. status quite often and although I know failure can happen suddenly, especially electrical, that doesn't make sense to me since it's still fully functional.
I've looked all over online and most people with this issue seem to have a broken drive but mine still works, just not where it needs to.
tl;dr: No matter what I've tried, my HDD cannot be used by BIOS or Windows, but works totally fine on Linux (While trying NTFS and FAT partitions)
linux windows-10 hard-drive dd gparted
asked Dec 30 '18 at 6:46
Mojave3Mojave3
1
add a comment |
OS: Windows 10 Enterprise
Motherboard: MSI Z87-G45
HDD: Western Digital 1TB Black WD1003FZEX
Hello, first post on here but this site, among many other StackExchange sites have been an infinite wealth of knowledge to me for years so thanks for that. I apologize if I don't have formatting down too well.
I'm having a problem with my hard drive that I really feel like I'm at a dead end with.
I recently got an SSD and installed it into my PC. At this point I had 3 drives. 1 SSD and 2 HDDs. After plugging all 3 drives in, I started getting signs of my power supply getting finicky. This had also happened previously when I had 3 HDDs installed at the same time. The PC would randomly shut off/restart, my motherboard would go into its protective mode which made it where the PC would not power on until I unplugged and re-plugged the power supply cable to the motherboard. So I took it as a sign, while everything was still intact, to unplug my least used HDD and leave it be until I upgraded PSUs. So I unplugged the HDD and just left it in my case. About a week later I go ahead and get a new PSU, it's a EVGA 850w G3 and I hooked it up with seemingly perfect success. I power it on, and everything seems fine, except one thing, which is Windows isn't showing my 3rd drive at all. I reboot a couple of times and check my bios (it wasn't showing up there either) and eventually it does show up, but it's unreadable. Explorer completely hangs whenever I try to access the drive in any way imaginable.
So I figured the drive was corrupted and I thought I'd do my best to recover anything I could so I threw SystemRescueCd onto a USB stick and booted into it expecting to use ddRescue and Testdisk to try and get at least something off of the drive. Out of curiosity, I attempted to mount the drive, and to my surprise it worked. It popped up a message claiming something about windows metadata, hibernation, and that it could only be accessed in read-only mode, but it mounted nonetheless. So I backed up the entire drive to an external HDD without any issue. All files fully functional and intact.
At this point, I figured I would just attempt to delete the two partitions on the drive and create a new one. So I used gparted to delete and then create an NTFS partition, and once again, everything worked. I mounted this new partition without issue, and this time I could read and write to it without any problem. I reboot, check BIOS (still not there). I boot into windows, still not there. So I boot back into SystemRescueCd and I try to rewrite the partition table. First I tried GPT, then I tried MBR. I tried doing this with Gparted, and then with testdisk. Nothing changed. However now, when I go into Disk Management on Windows, it will sometimes show a Disk 0, and it'll claim it's
not initialized
If I try to initialize it with MBR, it'll say "incorrect function" and if I do GPT it'll have a message claiming
The specified disk is not convertible because the size is less than the minimum size required for GPT disks
If I look at drive 0 in Diskpart it shows it having 0GB. As a last ditch effort, I tried completely clearing the drive with DD, filling it with /dev/zero, then creating a new partition table using gparted. Still nothing, with the exact same Not Initialized issue and errors.
So now I'm just confused. Why can I use this drive completely normally on linux, but not even my BIOS can read it? I could understand a corrupted partition table hampering things but I've done my best to reset that. Could this happen with a hardware issue? It just doesn't make sense to me that it's completely fine when I use a Linux distro. Prior to all of this, the drive appeared completely healthy. I check S.M.A.R.T. status quite often and although I know failure can happen suddenly, especially electrical, that doesn't make sense to me since it's still fully functional.
I've looked all over online and most people with this issue seem to have a broken drive but mine still works, just not where it needs to.
tl;dr: No matter what I've tried, my HDD cannot be used by BIOS or Windows, but works totally fine on Linux (While trying NTFS and FAT partitions)
linux windows-10 hard-drive dd gparted
asked Dec 30 '18 at 6:46
Mojave3Mojave3
1
You should focus on getting all three drives showing up in the BIOS properly. This problem tells me you have a hardware, or at least a BIOS setting, issue. It’s probably a motherboard issue, not a hard drive issue. Try unplugging all the drives and try plugging in the problematic drive to other SATA ports. Try resetting the BIOS, changing SATA modes, etc. the drive should show up. Your description of shutting down or restarting makes me think your motherboard may be the problem, not your power supply.
– Appleoddity
Dec 30 '18 at 6:54
add a comment |
OS: Windows 10 Enterprise
Motherboard: MSI Z87-G45
HDD: Western Digital 1TB Black WD1003FZEX
Hello, first post on here but this site, among many other StackExchange sites have been an infinite wealth of knowledge to me for years so thanks for that. I apologize if I don't have formatting down too well.
I'm having a problem with my hard drive that I really feel like I'm at a dead end with.
I recently got an SSD and installed it into my PC. At this point I had 3 drives. 1 SSD and 2 HDDs. After plugging all 3 drives in, I started getting signs of my power supply getting finicky. This had also happened previously when I had 3 HDDs installed at the same time. The PC would randomly shut off/restart, my motherboard would go into its protective mode which made it where the PC would not power on until I unplugged and re-plugged the power supply cable to the motherboard. So I took it as a sign, while everything was still intact, to unplug my least used HDD and leave it be until I upgraded PSUs. So I unplugged the HDD and just left it in my case. About a week later I go ahead and get a new PSU, it's a EVGA 850w G3 and I hooked it up with seemingly perfect success. I power it on, and everything seems fine, except one thing, which is Windows isn't showing my 3rd drive at all. I reboot a couple of times and check my bios (it wasn't showing up there either) and eventually it does show up, but it's unreadable. Explorer completely hangs whenever I try to access the drive in any way imaginable.
So I figured the drive was corrupted and I thought I'd do my best to recover anything I could so I threw SystemRescueCd onto a USB stick and booted into it expecting to use ddRescue and Testdisk to try and get at least something off of the drive. Out of curiosity, I attempted to mount the drive, and to my surprise it worked. It popped up a message claiming something about windows metadata, hibernation, and that it could only be accessed in read-only mode, but it mounted nonetheless. So I backed up the entire drive to an external HDD without any issue. All files fully functional and intact.
At this point, I figured I would just attempt to delete the two partitions on the drive and create a new one. So I used gparted to delete and then create an NTFS partition, and once again, everything worked. I mounted this new partition without issue, and this time I could read and write to it without any problem. I reboot, check BIOS (still not there). I boot into windows, still not there. So I boot back into SystemRescueCd and I try to rewrite the partition table. First I tried GPT, then I tried MBR. I tried doing this with Gparted, and then with testdisk. Nothing changed. However now, when I go into Disk Management on Windows, it will sometimes show a Disk 0, and it'll claim it's
not initialized
If I try to initialize it with MBR, it'll say "incorrect function" and if I do GPT it'll have a message claiming
The specified disk is not convertible because the size is less than the minimum size required for GPT disks
If I look at drive 0 in Diskpart it shows it having 0GB. As a last ditch effort, I tried completely clearing the drive with DD, filling it with /dev/zero, then creating a new partition table using gparted. Still nothing, with the exact same Not Initialized issue and errors.
So now I'm just confused. Why can I use this drive completely normally on linux, but not even my BIOS can read it? I could understand a corrupted partition table hampering things but I've done my best to reset that. Could this happen with a hardware issue? It just doesn't make sense to me that it's completely fine when I use a Linux distro. Prior to all of this, the drive appeared completely healthy. I check S.M.A.R.T. status quite often and although I know failure can happen suddenly, especially electrical, that doesn't make sense to me since it's still fully functional.
I've looked all over online and most people with this issue seem to have a broken drive but mine still works, just not where it needs to.
tl;dr: No matter what I've tried, my HDD cannot be used by BIOS or Windows, but works totally fine on Linux (While trying NTFS and FAT partitions)
linux windows-10 hard-drive dd gparted
asked Dec 30 '18 at 6:46
Mojave3Mojave3
1
OS: Windows 10 Enterprise
Motherboard: MSI Z87-G45
HDD: Western Digital 1TB Black WD1003FZEX
Hello, first post on here but this site, among many other StackExchange sites have been an infinite wealth of knowledge to me for years so thanks for that. I apologize if I don't have formatting down too well.
I'm having a problem with my hard drive that I really feel like I'm at a dead end with.
I recently got an SSD and installed it into my PC. At this point I had 3 drives. 1 SSD and 2 HDDs. After plugging all 3 drives in, I started getting signs of my power supply getting finicky. This had also happened previously when I had 3 HDDs installed at the same time. The PC would randomly shut off/restart, my motherboard would go into its protective mode which made it where the PC would not power on until I unplugged and re-plugged the power supply cable to the motherboard. So I took it as a sign, while everything was still intact, to unplug my least used HDD and leave it be until I upgraded PSUs. So I unplugged the HDD and just left it in my case. About a week later I go ahead and get a new PSU, it's a EVGA 850w G3 and I hooked it up with seemingly perfect success. I power it on, and everything seems fine, except one thing, which is Windows isn't showing my 3rd drive at all. I reboot a couple of times and check my bios (it wasn't showing up there either) and eventually it does show up, but it's unreadable. Explorer completely hangs whenever I try to access the drive in any way imaginable.
So I figured the drive was corrupted and I thought I'd do my best to recover anything I could so I threw SystemRescueCd onto a USB stick and booted into it expecting to use ddRescue and Testdisk to try and get at least something off of the drive. Out of curiosity, I attempted to mount the drive, and to my surprise it worked. It popped up a message claiming something about windows metadata, hibernation, and that it could only be accessed in read-only mode, but it mounted nonetheless. So I backed up the entire drive to an external HDD without any issue. All files fully functional and intact.
At this point, I figured I would just attempt to delete the two partitions on the drive and create a new one. So I used gparted to delete and then create an NTFS partition, and once again, everything worked. I mounted this new partition without issue, and this time I could read and write to it without any problem. I reboot, check BIOS (still not there). I boot into windows, still not there. So I boot back into SystemRescueCd and I try to rewrite the partition table. First I tried GPT, then I tried MBR. I tried doing this with Gparted, and then with testdisk. Nothing changed. However now, when I go into Disk Management on Windows, it will sometimes show a Disk 0, and it'll claim it's
not initialized
If I try to initialize it with MBR, it'll say "incorrect function" and if I do GPT it'll have a message claiming
The specified disk is not convertible because the size is less than the minimum size required for GPT disks
If I look at drive 0 in Diskpart it shows it having 0GB. As a last ditch effort, I tried completely clearing the drive with DD, filling it with /dev/zero, then creating a new partition table using gparted. Still nothing, with the exact same Not Initialized issue and errors.
So now I'm just confused. Why can I use this drive completely normally on linux, but not even my BIOS can read it? I could understand a corrupted partition table hampering things but I've done my best to reset that. Could this happen with a hardware issue? It just doesn't make sense to me that it's completely fine when I use a Linux distro. Prior to all of this, the drive appeared completely healthy. I check S.M.A.R.T. status quite often and although I know failure can happen suddenly, especially electrical, that doesn't make sense to me since it's still fully functional.
I've looked all over online and most people with this issue seem to have a broken drive but mine still works, just not where it needs to.
tl;dr: No matter what I've tried, my HDD cannot be used by BIOS or Windows, but works totally fine on Linux (While trying NTFS and FAT partitions)
linux windows-10 hard-drive dd gparted
linux windows-10 hard-drive dd gparted
asked Dec 30 '18 at 6:46
Mojave3Mojave3
1
asked Dec 30 '18 at 6:46
Mojave3Mojave3
1
asked Dec 30 '18 at 6:46
Mojave3Mojave3
1
asked Dec 30 '18 at 6:46
Mojave3Mojave3
1
asked Dec 30 '18 at 6:46
Mojave3Mojave3
1
1
You should focus on getting all three drives showing up in the BIOS properly. This problem tells me you have a hardware, or at least a BIOS setting, issue. It’s probably a motherboard issue, not a hard drive issue. Try unplugging all the drives and try plugging in the problematic drive to other SATA ports. Try resetting the BIOS, changing SATA modes, etc. the drive should show up. Your description of shutting down or restarting makes me think your motherboard may be the problem, not your power supply.
– Appleoddity
Dec 30 '18 at 6:54
add a comment |
You should focus on getting all three drives showing up in the BIOS properly. This problem tells me you have a hardware, or at least a BIOS setting, issue. It’s probably a motherboard issue, not a hard drive issue. Try unplugging all the drives and try plugging in the problematic drive to other SATA ports. Try resetting the BIOS, changing SATA modes, etc. the drive should show up. Your description of shutting down or restarting makes me think your motherboard may be the problem, not your power supply.
– Appleoddity
Dec 30 '18 at 6:54
You should focus on getting all three drives showing up in the BIOS properly. This problem tells me you have a hardware, or at least a BIOS setting, issue. It’s probably a motherboard issue, not a hard drive issue. Try unplugging all the drives and try plugging in the problematic drive to other SATA ports. Try resetting the BIOS, changing SATA modes, etc. the drive should show up. Your description of shutting down or restarting makes me think your motherboard may be the problem, not your power supply.
– Appleoddity
Dec 30 '18 at 6:54
You should focus on getting all three drives showing up in the BIOS properly. This problem tells me you have a hardware, or at least a BIOS setting, issue. It’s probably a motherboard issue, not a hard drive issue. Try unplugging all the drives and try plugging in the problematic drive to other SATA ports. Try resetting the BIOS, changing SATA modes, etc. the drive should show up. Your description of shutting down or restarting makes me think your motherboard may be the problem, not your power supply.
– Appleoddity
Dec 30 '18 at 6:54
add a comment |
0
active
oldest
votes
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%2f1388904%2fbios-and-windows-10-cannot-use-detect-initialize-hard-drive-while-linux-can-tri%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f1388904%2fbios-and-windows-10-cannot-use-detect-initialize-hard-drive-while-linux-can-tri%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
You should focus on getting all three drives showing up in the BIOS properly. This problem tells me you have a hardware, or at least a BIOS setting, issue. It’s probably a motherboard issue, not a hard drive issue. Try unplugging all the drives and try plugging in the problematic drive to other SATA ports. Try resetting the BIOS, changing SATA modes, etc. the drive should show up. Your description of shutting down or restarting makes me think your motherboard may be the problem, not your power supply.
– Appleoddity
Dec 30 '18 at 6:54