OK, Now I'm Livid - Windows 2000 SP4 Trashed Another Large Drive

C

cope242

I just built this AMD box...

MSI K8N Neo4-F Motherboard
AMD Athlon 64 3200+
1GB Crucial Ram
200GB Western Digital HD
EVGA Geforce 256 Video Card

I installed the Windows 2000 SP4, then after about 2 hours of installs
and copying data from my old drive **POW** file copy error! I was
forced to reboot and just like last time Chkdsk went to work trashing
the drive. This time it was an AMD system with a 200GB Western
Digital drive, last time it was an Intel system and a 200GB Maxtor.

I'm desperately trying to figure out what's going on. Are there any
known issues with W2K and large drives?

I did find this link, so I know I'm not the only one that's
experiencing this kind of data loss...

http://groups.google.com/group/micr...OPYING"+CORRUPT&rnum=9&hl=en#c005e8ddc83b879b

Any information about how I can prevent this in the future would be
great appreciated.

Thank you,

Cope242
 
D

Dave Patrick

As John mentioned you'll need the EnableBigLba fix then let chkdsk run once
before copying your data, then probably again after the copy. After the new
install the dirty bit is set on any additional disks prior to the OS
mounting them.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
R

Roedy Green

I'm desperately trying to figure out what's going on. Are there any
known issues with W2K and large drives?
Click to expand...

the other thing to check is that your RAM is functioning 100%. You
might run a burn in test.
 
S

Stan Shankman

But I thought SP4 eliminated the need to set big LBA.
Could it be that this guy is running on a machine that has and older IDE
host adapter?
Some old drive controllers simply do not support big LBA.
If you cross the line, you are in trouble - data loss!
- Stan
 
J

John John

Oh no, not that I know of. I think that only came about with Windows XP
SP1.

John
 
Top