A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Hardware and Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Drive not readable in XP after crash, fine in DOS



 
 
Thread Tools Display Modes
  #1  
Old December 6th 03, 08:37 PM
Steak
external usenet poster
 
Posts: n/a
Default Drive not readable in XP after crash, fine in DOS

Here's my deal, which is so laden with unlucky coincidences it's kind
of amusing.

My basic setup:
KT7A-RAID (not using RAID though)
Primary: 40 GB Western Digital drive (FAT32, 6 partitions)
Slave: 20 GB Maxtor drive (FAT32, 1 partition)

After a crash today, the D: (Maxtor) isn't recognized under Win XP. I
receive "The disk in Drive D is not formatted. Do you want to format
now?" when I try to access it.

I initially thought it might be an issue with the BIOS (which is
up-to-date) or the VIA chipset (I already have a wacky problem due to
an incompatibility with my generation of Western Digital drives).
However, I was able to boot to DOS (the D: used to be a Win98 system
drive, and I can still get to the command prompt). I found that all of
the folders are still accessible.

Unfortunately, I can't run any utilities to check the disk -- Windows
XP's scandisk doesn't recognize the drive as having a valid file
system. And my floppy drive bit the dust, so I can't use Maxblast,
Norton, etc.

I assume it's a Windows problem at this point. But, due to a low disk
space warning on a partition on my primary drive, I cleared some
"obsolete" files on XP's recommendations. Turns out those obsolete
files were probably my system restore points, because when I looked,
there weren't any! I manually create them on a pretty regular basis,
so there should have been something there.

Any ideas on how to fix this problem, short of reinstalling XP? The
worst part is, I planned on building a new PC in 2-3 weeks anyway,
because I've got to replace half the hardware anyway (plus I'm sick of
the VIA issues and want to switch chipsets).

Thanks in advance for your advice.
Ads
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off






All times are GMT +1. The time now is 02:22 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.