Discussion Locked

Hard Drive Disappeared

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a 40GB WD drive that has become unreadable after a windows XP installation on another (Newly added) drive in the same system. The 40GB drive was ?theoretically? not touched (was originally the 2nd drive (D) in a two drive system), however XP now sees it as a ?Raw? disk, vs the actual FAT32 single partition. In the XP Drive Administration page, the type of partition is blank. The new boot drive (C) is a 100GB clean XP installation NTFS and is fine, as is the old boot (formerly C) drive, which is a 6 GB FAT32 drive.

The 40 GB drive is on the Primary IDE cable as a slave to the 100GB new drive C.

Other notes-- the drive appeared to be functioning fine (folders visible, drive "D" name, etc.) after the 100 GB Drive additioin and XP install, but "disappeared" on a subsequent reboot.

It has about 35GBs of useful info on the drive. We have run Western Digital?s diags on the disk and the disk is mechanically OK, but it is not showing up on the boot-up and XP wants (asks) to ?initialize? it.

My question is whether any of the "recovery" products might be able to restore the readability of the disk, or is there something else I can try . Please comment. Partition Magic has not worked in this case.

My local PC shop has tried a number of utilities - about half see it as a FAT32 and the other see it as Raw. Nothing they have tried as yet has worked, though they were successful in creating an identically "Bad" drive out of a brand new 40GB drive they had on theshelf. I am picking the PC up today - they have given up on it, I think.

Any comments would be much appreciated!!!

14 replies

by opatzg9

Just a thought, have you tried a PCI IDE controller card instead of onboard IDE? All the diagnosis may have caused more problems and attaching to different controllers may cause more harm than good. If you take the 100gig drive out and reassemble it as your initial layout is the data still accessible? If it is get a cd burner and back it up then do whatever you need to get them to work. Could it be a power issue with three hard disks?

by wa4tvy

I don?t know if the shop tried the PCI IDE trick, but it is a good idea. They told me they did try reverting to the original config, with no results. The PS is 300W so it should be able to handle it.. any other ideas??? Ever seen anything like this? My shop is stumped.

by opatzg9

F.Y.I. I know "The Chas" on a number of occasions has stated that a 300w supply may not be enough, depends on the 300w supply. I have an emachine 466, 120w supply with 2 drives, dvd, cd burner and usb devices, network card and modem and the rest integrated sound/video, 192 mb ram 2 fans and that works, go figure. Anyway laying out the rest of what you're using may help someone more knowledgable diagnose it as well. I do think the pci ide card is worth a try but I'v also heard that changing the ide chip sets changes the way drives are written and read so its' possible you'll be reloading everything if you do. Good Luck!

by wa4tvy

Have just returned from the shop and am working on the drive myself. The shop did not try the PCI-IDE route, but did try the drive in several other machines with the same result. Current status is that the drive is recognized but claims it is not formatted. Shows 37+ GB as free space. The XP Disk management window does not show anything in the column where "NTFS or FAT32" should be - just a blank. The drive is or was a FAT32. I am running it as the only drive on the secondary IDE. I am trying a demo product by LC-Technologies "File Recovery Pro". We'll see what it thinks. BTW... the power supply is actually a 350 Watt version, not a 300 like I thought.

More thoughts or ideas anyone??? I am up-ing the points since this seem to be a real puzzle.

by wa4tvy

Update - the File Recovery software was not successful, though it "found four Logical volumes on this single physical drive. One tech beleives that the problem is related to having a FAT32 drive over 32 MB on a XP system, where possibly a file was crosslinked. Suggestion was to fDISK the HD on a W98SE system to restore the proper partitioin geometry (without losing the data, hopefully)

Another Disk recovery program (Winternals Disk Commander) reports the drive as being "0 MB RAW" and is unable to Mount the drive, thus cannot proceed. Hope these clues are helpful to some of you super-techs out there :-)

by djent

you may have a corrupt boot sector. You could use Diskprobe (win2K resource kit) to examine the boot sector and repair it.

by wa4tvy

Sounds dangerous for someone (like me) not real familiar with the drive set-up. Will have a look though to see ...

by robb.banner

Try the obvious, put the smaller size drive first then the larger drive as slave IE: 40 GB = C: & 100 GB = D: then it should see both of them (but unfortunately, you will have to re-install an OS on it to get things back to the way they were. So, ifyou are running XP, Win2K, Or any othe M.S. OS, Then you'll either have to "GHOST" it or manually re-build the CPU. (Sorry for the bad news)

by wa4tvy

We tried this before, using the smallest drive (6GB) as C, which still had the w98 OS on it. no luck. WD rep told me that when upgrading to XP with a drive in the system that was >32 GB,which was originally formatted under W98, the result could be "unstable" (his words) and that probably XP rendered the drive unreadable. net result was that we had to reformat the 40GB drive, losing all data. Would have been good to have understad that little WD tidbit earlier - oh well...

by opatzg9

Any luck with the software diagnostics utility?
Have you tried new ide cables?

by wa4tvy

tried a half dozen of them - nothing worked. New IDE cables was the first thing we tried.

by dsimms

I had my secondary drive disappear with Win2000, I reset the mother board and rebooted and the drive came back. Note: there was a reset button located on my motherboard that enabled me to do this. if there is no reset button maybe removing the CMOS battery might do the same thing.
Hope this helps.

This discussion is closed to new replies.