hard disk problem?

Hello,

I have a machine running W2K Server. It has a 2 hard drives set up in
a RAID array providing mirroring.

Today, I noticed an interesting problem. There's a large folder on the
hard drive containing around 8000 files (including subfolders) that
takes up about 4GB of space. When I copy that large folder anywhere --
either to another place on the same drive or to an external USB drive
I have -- as many as 50 of the copied files aren't identical to their
respective originals (according to fc.exe as well as a third-party
file-comparison utility).

This never used to happen, and it has me a little puzzled. Any
thoughts as to why this might be happening? Impending hardware
failure? Virus?

Thanks,
Martin

On 22 May 2004 12:00:09 -0700, me@mgoldman.com (Martin Goldman) wrote:

>Hello,
>
>I have a machine running W2K Server. It has a 2 hard drives set up in
>a RAID array providing mirroring.
>
>Today, I noticed an interesting problem. There's a large folder on the
>hard drive containing around 8000 files (including subfolders) that
>takes up about 4GB of space. When I copy that large folder anywhere --
>either to another place on the same drive or to an external USB drive
>I have -- as many as 50 of the copied files aren't identical to their
>respective originals (according to fc.exe as well as a third-party
>file-comparison utility).
>
>This never used to happen, and it has me a little puzzled. Any
>thoughts as to why this might be happening? Impending hardware
>failure? Virus?
>
>Thanks,
>Martin

You provided no detail of systems involved?
I mean, the hardware, since this is a hardware-oriented newsgroup.

Some chipsets had potential problems (like Via KT series boards with 686
southbridge) but since you provide no further detail the first
recommendation would be to extensively check your memory for errors,
several hours to more than a day running http://www.memtest86.com

kony <spam@spam.com> wrote in message news:<8vdva0lbi727hphffaqo9nj6pk3ir1mg12@4ax.com>...

> You provided no detail of systems involved?
> I mean, the hardware, since this is a hardware-oriented newsgroup.
>
> Some chipsets had potential problems (like Via KT series boards with 686
> southbridge) but since you provide no further detail the first
> recommendation would be to extensively check your memory for errors,
> several hours to more than a day running http://www.memtest86.com

I have posted a report from the System Information snap-in in MMC on
this machine at:

http://www.mgoldman.com/comp.txt

Please let me know what, if any, other information would be helpful
and how I might find it.

As per your suggestion, I tried to create a memtest86 boot disk on
this machine, and then booted from it, and it seems that the disk
wasn't created right -- when I tried to boot from it, it just started
printing "1000" on the screen, over and over again, until I shut it
off. When I made the disk on another machine, it worked fine. Wonder
if it could be a related issue.

I started memtest86 at 2 p.m. today and will let it continue running
until around 7 a.m. tomorrow morning; will post again if I get any
interesting results.

Thanks again,
Martin

"Martin Goldman" <me@mgoldman.com> skrev i melding
news:6cb3f9a8.0405231055.7296b047@posting.google.com...

> I have posted a report from the System Information snap-in in MMC on
> this machine at:
> http://www.mgoldman.com/comp.txt

Oh, to much text for me to read.

Is the harddisks in your raid array equals each other?
Microsoft says that all of the disks in a raid array should be produced by
the same manufacturer, and being the same type and size. If not, the raid
array may not work properly.
I have tested a raid array with two disks having the same size, but
different brand. And i got the same problems as you.