• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

HDD not booting up

G

Goi

Diamond Member
Hi,

I have a WD 2TB Caviar Black HDD that is only a couple months old, running Windows 7 Ultimate x64 24/7, and just yesterday it rebooted while I was away, and I came back to a non-booting PC.

I have been unable to get it to boot up ever since, even though the AHCI menu seems to recognize that the HDD is there. I've tried different ports, and certain ports have a slight delay before the HDD is detected. I suspect that the ports may be faulty, but how do I make sure that the data in the HDD is still there? Perhaps the boot sector has been corrupted or something...

Edit: Just tried a port that detects it immediately rather than a delay, and left it to boot for a few minutes while I googled around for solutions on another PC. When I went back, the HDD booted up to Startup Repair, which informs me that it could take hours and several reboots to complete fixing the drive. How long do I wait before I give up and try something else?
 
Last edited:
I was thinking of both suggestions...

For #1, Startup Recovery is still running so I'm wondering whether to give it more time or cancel and try it on this PC.

For #2, I tried an old Knoppix 5.0.1 CD I had...maybe it's too old or not compatible or corrupted, but I could only manage to boot up to a very limited prompt as it failed to find the Knoppix system files. Could not even do an ls, much less fdisk and other commands.
 
"fdisk"... What are you thinking? 😱
If you value your data, don't even think about fdisk.

Try some known good memory.
 
Blain said:
"fdisk"... What are you thinking? 😱
If you value your data, don't even think about fdisk.

Try some known good memory.
Click to expand...

I meant, I was doing an "fdisk -l" just to detect any drives/volumes, but it wouldn't even work.

Anyway, fixed the problem...just a faulty SATA port.
 
You must log in or register to reply here.
Back
Top