Hard drive wont boot

bigmatt0211

New Member
Reaction score
0
This is weird. Im fixing my friends computer. When I first got it, the ntfs file system had failed, and after a 2 day chkdsk, i got it where it is now accessible. It was attached to my computer, but when I reinstall the hd back inside his computer, the harddrive doesnt seem to boot. I see the motherboard loading screen, but after that it just stops. Now when I run UBCD, i can read and access all the files, windows repair detects the harddrive, but it wont boot. Any one have any ideas? Im currently scanning it with ubcd for viruses and spyware...
 
Another option in case your friend is cheap and doesn't want to buy a new HD...
  1. Copy the data off.
  2. Format drive.
  3. Reinstall Wondows.
  4. Replace data.
Remind him that the drive will likely fail again soon. The second time you'll have to do all of it again AND he'll have to buy a new HD.
 
Last edited:
This is weird. Im fixing my friends computer. When I first got it, the ntfs file system had failed, and after a 2 day chkdsk, i got it where it is now accessible. It was attached to my computer, but when I reinstall the hd back inside his computer, the harddrive doesnt seem to boot. I see the motherboard loading screen, but after that it just stops. Now when I run UBCD, i can read and access all the files, windows repair detects the harddrive, but it wont boot. Any one have any ideas? Im currently scanning it with ubcd for viruses and spyware...

I'm hoping that HD isn't one of those Seagate drives that had the bad firmware/failure issue. If it is, I'd backup, wipe the drive and send it back with an RMA and get a replacement drive.
 
sounds like you need a new boot record
did you try the repair console
the commands i think are fixboot and fixmbr
 
I just recently had an issue with adding an old harddrive to my computer to use while I wait for my memory RMA for my new computer. Added it to the primary channel as slave and started getting delay write failed messages. Tried mixing up the drives on different channels, master/slave, new cables, etc. A chkdsk resulted in god knows how many corrupted and recovered files of just about every file on my harddrive. And while I never did figure it out as I reinstalled windows, I susspect it may have been a shotty power plug in the drive causing problems as it seemed too easy to pull out when I swapped the cable one more time. It eventually got to a STOP 7b error when booting, but I believe Ubuntu could still read it. Check your drive with some diagnostic boot cd in both computers to narrow it down, as when they fail they have failed in the software for me. If your drive in getting corrupt in your friends machine run a memtest on it, as I've had flaky problems with memory lately on a few machines that cause allllllll kinds of issues that you wouldn't even think would be related. Worst case if the drive is good save the data and nuke it.
 
Back
Top