Question HDD spins, BIOS reads HDD, but windows/disk manager doesn't?

Aug 31, 2024
42
4
35
4tb seagate baracuda.

After my pc stopped working, maybe due to a bad PSU, bad motherboard, I don't know, I got my hard drives all removed and my two SSDs seem fine, but my 4tb Seagate baracuda HDD, no windows installed on it just a secondary internal hard drive, the one with lots of important files on it, spins up when plugged into another PC directly, it shows correct storage in bios, but not windows/file explorer, like, AT ALL. Not "unknown", not "not initialized" ... nothing. Doesn't show in device manager either, its like it literally does not exist.

The drive showed NO signs of slowing down or death before this. It still spins just fine, no clicking, seems completely and utterly fine

I have no earthly idea what went wrong with my PC which makes this so frustrating. Its definitely not the data cable because another HDD works just fine when plugged into another PC, but this hard drive is a ghost!

It spins, BIOS reads it, but in windows it might as well not exist.

What could possibly cause a drive to spin, be read in bios, but basically not exist as far as windows is concerned? Ive used this Hard drive for 2.5 years with zero issues.
 
Not "unknown", not "not initialized" ... nothing. Doesn't show in device manager either, its like it literally does not exist.
Chances are the PCB/controller/a fuse on the HDD went out. I wouldn't mess with it and try and look for a professional data recovery specialist in your locality.

What could possibly cause a drive to spin, be read in bios, but basically not exist as far as windows is concerned?
Part of the drive is receiving power, is my guess.
 
Not "unknown", not "not initialized" ... nothing. Doesn't show in device manager either, its like it literally does not exist.
Chances are the PCB/controller/a fuse on the HDD went out. I wouldn't mess with it and try and look for a professional data recovery specialist in your locality.

What could possibly cause a drive to spin, be read in bios, but basically not exist as far as windows is concerned?
Part of the drive is receiving power, is my guess.
Wouldnt a PCB issue manifest in the drive not even spinning at all?

It spins, bios even reads it, but windows doesn't detect it whatsoever

Edit: nevermind, missed your second part
 
Last edited:
Please show BIOS screenshots.
Also screenshots from
Disk Management,​
Device Manager - disk drives and storage controllers sections expanded and​
Windows Storage Spaces (Control Panel/Storage Spaces)​
(upload to imgur.com and post link)
Unfortunately, I dont have any at this moment but want to provide them soon.

But basically, it shows up in bios completely normally (4 tb, model name)

But in windows, nothing, absolutely nothing, as if it were not even plugged in
 
have you clicked on "this pc" , then "more options", then click manage" when "computer management" page pops up click on ""disk management" (understorage option)..
if it shows there but as "offline" click it and select "online" if its not there click "ACTION" (at top of screen) then "rescan"

this should make it show up and working ( you might have to allocate it a "drive designation"..
 
have you clicked on "this pc" , then "more options", then click manage" when "computer management" page pops up click on ""disk management" (understorage option)..
if it shows there but as "offline" click it and select "online" if its not there click "ACTION" (at top of screen) then "rescan"

this should make it show up and working ( you might have to allocate it a "drive designation"..
The disk did not appear in disk management whatsoever

my main theory is some sort of firmware issue atm, so I sent it to data recovery, I will keep this thread posted on if its successful
 
  • Like
Reactions: steveb1976
The identity information for Seagate HDDs is usually stored in the reserved System Area on the platters.
Also hopefully if it is a firmware issue the firmware that's damaged is not the unique unfixable firmware, but rather something that can be fixed by specialized equipment, if it is a firmware issue