"Bad" HardDrive

Heres a first;

6hcnd5c.jpg

(Click to view details)

About; C: (disk1) Containing Windows, I had resently though ubuntu resized it to half its size.. Windows detected the error upon startup but couldnt fix it.. because I cancelled the 'check'. Norton couldnt fix it eaither, and this was about a week and a half ago. "opps"

Now I'm no Genious, but when a computer describes your harddrive as "Bad" somthing up. Can anyone fill me in? My gusse to fix it just run the windows disk and see if it can repair it, I just dont want to overly f*ck this one up I finally got my pc exactly the way i want it.

#462474

What i would do is run the files and settings transfer wizard, just in case. and do the "old PC" option. save it to a folder on your media drive.

then try the repair. you could also try booting into a DOS floppy and running chkdsk

#462477

In time I got a similar problem, I resolved him, like introducing the windows XP disk, and try to format with it... probably it will give you an error, but when you run again Partition Magic, the drive is no more labeled as BAD. And you could format like you want..

I hope it solves your problem...

Sorry my english...

#462489

You did do a check disk & defrag before partitioning I hope?

Just had to fix mine last week. Before jumping into the recovery console or into formating. Verify the disk is bad by using the fsutil at the command prompt.

Type this and replace "C:" for each respective drive:

fsutil dirty query C:

Link to MS Documention

If it is bad then back things up and either run chkdsk from the command line or right click on the drive properties, select tools tab, Error-Checking Section select check now. You will have to do this for each drive and most likely it will require a reboot each time to fix the issues.

Microsoft Documention on Chkdsk

After all that I would do a defrag of each drive. IMO formatting won't necessarily fix anything or everything and should be used as a last resort.

Last but, not least a link to Windows XP Resource Kit Troubleshooting Guide.

#462529