Well, I just got my desktop computer back from the Local Computer Place[sup]TM[/sup] who installed a new hard drive to replace the one that went dead at the end of last month.
Now my computer had two hard drives prior to the crash, “C” and “D”. I was running WinME so the drives were both formatted and contained data.
So now, after the Local Computer Place[sup]TM[/sup] has installed a new C drive running Windows XP Pro. I fired up the desktop, went to access the D drive (which is now the “F” Drive, grr.)…
ERROR:
The disk in Drive F is not formatted.
:mad:
Yes it damn well is, or at least it damn well should be! Why won’t it read the fucking thing? Did the Local Computer Place[sup]TM[/sup] unformat the drive? Is there some inherent incompatibility between the formats used by the two versions of Windows? (Probably.)
Hmmm…I don’t know about the formatting on ME, but do you have the disc for Windows XP Pro? Just stick it in the CD-ROM drive, let it boot off of the CD, and reinstall it yourself. That’ll take care of that little sucker.
I have done several installs of XP Pro, and I have found that it’s never the same, each time I do it. Weird.
You dare question the wisdom of the mighty Windows XP? PEON! HERETIC! Windows XP is infalliable! Windows XP does not make mistakes! If Windows XP says your hard drive is unformatted, you had better damn well believe it is unformatted! WINDOWS XP IS NEVER WRONG!
Windows XP is capable of reading FAT32. In order to verify that the data is still there before converting the file system, I’d boot from some sort of disk (don’t install anything or format anything) and just check and see if there are files there.
After that it should definitely be possible to convert the FAT32 drive to NTFS (but beware, because you can’t without extreme difficulty go in the other direction) and Windows XP should like it just fine.
In theory, XP reads FAT32. In theory there is no difference between theory and practice. In practice, there always is. I doubt LCP did anything to the formatting of the second drive, but you may also want to look inside the computer at the backs of the drives themselves and make sure LCP didn’t change any jumpers around. (New C drive should be Master, old D drive should be Slave.)
Converting from FAT32 to NTFS doesn’t require formatting the drive or changing the data on it. It can be done under Windows through the disk management service.
Not sitting on my XP box right now, but I’m pretty sure it’s in the Administrative Tools.
One more thing I should mention. Old hard drive (“F”, formerly “D”) was IDE and new hard drive is ATA. I had to install an ATA controller to run the new drive.
So old hard drive is now on an IDE cable all by itself?
If it is configured to be slave, this could be why Windows is having difficulty recognizing the drive properly… although normally that means it’s not recognized at all.
A RAID is a Redundant Array of Independent Disks. It’s a system of making sure that a redundant copy of data always exists so that if one drive fails, others supply the data from that drive, and nothing is lost.
The RAID controller has the job of determining which disk in the array gets which chunks of data at which time and sends that data to the correct drive.
RAID isn’t all that common in home computer systems because there’s really no reason to provide that level of redundancy for personal data, but I’m figuring that the card in your computer is capable of supporting a RAID array whether you have one or not, so that’s why you’re seeing RAID controller.
How old is the motherboard in the computer that you just had a new drive added to? With some of the older boards that supported ATA 66 it’s necessary to add another card to support the Ultra ATA/100 drives, so that could be the reason you’ve got another controller card in there. Not a big deal, I had one for a while, and it would also allow for RAID.
To go from NTFS to FAT32, absolutely. From FAT32 to NTFS under Windows XP, I have yet to encounter a single problem in the couple hundred drives I’ve done, and I did all of them right through the disk management service built into the OS.
Find out from LCP what type of controller card they installed and whether they actually did anything to the drive that used to be D and is currently F.
No matter what, I’d recommend converting to NTFS. It’s less likely to have a major crash on you, and it’s got security whereas FAT32 does not.
This may just be a case of one setting being thrown off by changing the way the drives are plugged in, or XP having an issue with FAT32.