//flex table opened by JP
PDA

Click to See Complete Forum and Search --> : scandisk caused hard drive to not be recognized????

shocksyde
10-22-2000, 09:26 AM
ok i was trying to format a 1.2 gig WD hard drive so i could reinstall everything (the comp was over-run with 5 years worth of virii http://sysopt.earthweb.com/forum/smile.gif). so i try to sinply format...wouldnt work for some reason so i decide maybe i need to run scan disk and clean it up first. so i run scan disk, then i try running it again in thorough mode. it locked up so i restarted the computer. now when i start the computer the drive wont be recognized. how can i get it recognized again so that i can format and reinstall windows and everything??

thanks ahead of time,
shock
Vampiel
10-22-2000, 10:46 AM
How far does your boot procedure progress? Does it get past the bios? If not try going into your bios and re-detecting it. If that does not work then you should try putting in all of the specs on it manually. If it does go past the bios, then simply use a bootup disk. If it goes to a prompt then go to your main drive and type fdisk. In fdisk you can re-partition the hard drive and hope for the best. Make sure you still format it. If youve never used fdisk just lemme know and ill walk you though it.
shocksyde
10-22-2000, 01:20 PM
nah it wont get past the ide detections in bios...only thing it detects is the cpu and memory then detects on my cd rom drive.

shock
Vampiel
10-22-2000, 03:35 PM
Then try using a boot up disk and fdisking it.
Nathan
10-22-2000, 03:44 PM
Can you try and put that hard drive in another PC? If I understand this right, something is causing it not to see the drive. If you have another hard drive, you can also put it in the same PC and see if it sees it.

Let us know.
TechJumper
10-22-2000, 04:31 PM
Perhaps we are going too far into things.

When you ran scandisk, were you running any executables at the same time? The executable is using the drive that you are trying to scan, thus creating a conflict in Windows. This has happened to me before, ended up being a CMOS error, keep me posted...

Michael Morelli (TechJumper)
shocksyde
10-22-2000, 07:51 PM
i'll probably fool with it some more tomorrow morning. i'll let you guys know.

shock