Xcopy from XP client trashes volume on Windows 2000 server

[Guest Ben Bazian]

Here is one for the group. Wonder if anyone has heard of this. I have a

Windows 2000 server as part of a Windows domain. The particular server has

a large hard drive so I have my laptop users execute a batch command that

xcopies modified files to a share on the server. I have one laptop that

crashed the server while the xcopy was running. I believe it was copying a

..pst file. The server would not boot. Just got a blinking cursor on

startup. I booted from the Windows 2000 CD and ran chkdsk. That appeared

to fix the issue. Other users in the interim executed their backup without

issue. On Friday I decided to try to have the user run the backup again.

This time it totally trashed the volume. When I tried to run checkdisk I

got an error that there were multiple errors on the volume and that it could

not be repaired. I tried to do a repair install but the windows

installation was not recognized.

 

I have since reformatted and reinstalled the server. I am fairly certain

that the server drive is not the problem.

 

I am at a loss as to how an xcopy could actually trash a volume.

 

Anyone have any ideas?

[Guest Pegasus \(MVP\)]

Re: Xcopy from XP client trashes volume on Windows 2000 server

 

 

"Ben Bazian" <bbazian@mybizoffice.com> wrote in message

news:uiuaXHcNIHA.5224@TK2MSFTNGP02.phx.gbl...

> Here is one for the group. Wonder if anyone has heard of this. I have a

> Windows 2000 server as part of a Windows domain. The particular server

> has a large hard drive so I have my laptop users execute a batch command

> that xcopies modified files to a share on the server. I have one laptop

> that crashed the server while the xcopy was running. I believe it was

> copying a .pst file. The server would not boot. Just got a blinking

> cursor on startup. I booted from the Windows 2000 CD and ran chkdsk.

> That appeared to fix the issue. Other users in the interim executed their

> backup without issue. On Friday I decided to try to have the user run the

> backup again. This time it totally trashed the volume. When I tried to

> run checkdisk I got an error that there were multiple errors on the volume

> and that it could not be repaired. I tried to do a repair install but the

> windows installation was not recognized.

>

> I have since reformatted and reinstalled the server. I am fairly certain

> that the server drive is not the problem.

>

> I am at a loss as to how an xcopy could actually trash a volume.

>

> Anyone have any ideas?

 

It might be a little premature to say that xcopy.exe is the culprit.

I would do some further tests, e.g.

- Use copy and robocopy

- Use xcopy to copy the files to a test machine instead of the server

- Use a different network adapter (it might send out garbage!)

- Use a different port on the network hub/switch that this PC is

connected to (the port might be defective)

[Guest Ben Bazian]

Re: Xcopy from XP client trashes volume on Windows 2000 server

 

 

"Pegasus (MVP)" <I.can@fly.com> wrote in message

news:edZEMkcNIHA.5360@TK2MSFTNGP03.phx.gbl...

>

> "Ben Bazian" <bbazian@mybizoffice.com> wrote in message

> news:uiuaXHcNIHA.5224@TK2MSFTNGP02.phx.gbl...

>> Here is one for the group. Wonder if anyone has heard of this. I have a

>> Windows 2000 server as part of a Windows domain. The particular server

>> has a large hard drive so I have my laptop users execute a batch command

>> that xcopies modified files to a share on the server. I have one laptop

>> that crashed the server while the xcopy was running. I believe it was

>> copying a .pst file. The server would not boot. Just got a blinking

>> cursor on startup. I booted from the Windows 2000 CD and ran chkdsk.

>> That appeared to fix the issue. Other users in the interim executed

>> their backup without issue. On Friday I decided to try to have the user

>> run the backup again. This time it totally trashed the volume. When I

>> tried to run checkdisk I got an error that there were multiple errors on

>> the volume and that it could not be repaired. I tried to do a repair

>> install but the windows installation was not recognized.

>>

>> I have since reformatted and reinstalled the server. I am fairly certain

>> that the server drive is not the problem.

>>

>> I am at a loss as to how an xcopy could actually trash a volume.

>>

>> Anyone have any ideas?

>

> It might be a little premature to say that xcopy.exe is the culprit.

> I would do some further tests, e.g.

> - Use copy and robocopy

> - Use xcopy to copy the files to a test machine instead of the server

> - Use a different network adapter (it might send out garbage!)

> - Use a different port on the network hub/switch that this PC is

> connected to (the port might be defective)

>

Thanks for the idea but I cannot take a chance on corrupting the server

again. I do not assume that xcopy is the culprit. It was the fact of

writing the files to the server. I am still wondering how it could trash

the whole volume? Assuming it is a network issue, which I do not believe it

to be, how would that totally corrupt to volume? At worst I would thing

that I would get corrupt files on the drive but it should not have rendered

the OS totally trashed.

 

I am setting up a NAS drive and will try to backup the computer to it and

see what happens.

[Guest Pegasus \(MVP\)]

Re: Xcopy from XP client trashes volume on Windows 2000 server

 

 

"Ben Bazian" <bbazian@mybizoffice.com> wrote in message

news:uRoDMCeNIHA.5264@TK2MSFTNGP02.phx.gbl...

>

> "Pegasus (MVP)" <I.can@fly.com> wrote in message

> news:edZEMkcNIHA.5360@TK2MSFTNGP03.phx.gbl...

>>

>> "Ben Bazian" <bbazian@mybizoffice.com> wrote in message

>> news:uiuaXHcNIHA.5224@TK2MSFTNGP02.phx.gbl...

>>> Here is one for the group. Wonder if anyone has heard of this. I have

>>> a Windows 2000 server as part of a Windows domain. The particular

>>> server has a large hard drive so I have my laptop users execute a batch

>>> command that xcopies modified files to a share on the server. I have

>>> one laptop that crashed the server while the xcopy was running. I

>>> believe it was copying a .pst file. The server would not boot. Just

>>> got a blinking cursor on startup. I booted from the Windows 2000 CD and

>>> ran chkdsk. That appeared to fix the issue. Other users in the interim

>>> executed their backup without issue. On Friday I decided to try to have

>>> the user run the backup again. This time it totally trashed the volume.

>>> When I tried to run checkdisk I got an error that there were multiple

>>> errors on the volume and that it could not be repaired. I tried to do a

>>> repair install but the windows installation was not recognized.

>>>

>>> I have since reformatted and reinstalled the server. I am fairly

>>> certain that the server drive is not the problem.

>>>

>>> I am at a loss as to how an xcopy could actually trash a volume.

>>>

>>> Anyone have any ideas?

>>

>> It might be a little premature to say that xcopy.exe is the culprit.

>> I would do some further tests, e.g.

>> - Use copy and robocopy

>> - Use xcopy to copy the files to a test machine instead of the server

>> - Use a different network adapter (it might send out garbage!)

>> - Use a different port on the network hub/switch that this PC is

>> connected to (the port might be defective)

>>

> Thanks for the idea but I cannot take a chance on corrupting the server

> again. I do not assume that xcopy is the culprit. It was the fact of

> writing the files to the server. I am still wondering how it could trash

> the whole volume? Assuming it is a network issue, which I do not believe

> it

> to be, how would that totally corrupt to volume? At worst I would thing

> that I would get corrupt files on the drive but it should not have

> rendered

> the OS totally trashed.

>

> I am setting up a NAS drive and will try to backup the computer to it and

> see what happens.

>

 

Did you note my suggestion?

"Use xcopy to copy the files to a test machine instead of the server".