Server 2003 slow to a crawl

[d.barrow@virgin.net]

The server was running fine until a week ago, but it's slowed to a
disc-bound crawl. CPU time is 1-2%, Network activity is negligible,
but the HDD is constantly in action. There have been no significant
changes to the setup. Task manager shows no unusual activity. At the
moment, no-one can even log in. Windows on the server take around 5
minutes to open up, so detective work is horribly slow.

Is there a way to determine which process is driving the HDD activity?

Ideas for where to look next...most welcome.

Thanks

 

[Scare?row]

Re: Server 2003 slow to a crawl

perfomance counters?

 

[Dragos CAMARA]

RE: Server 2003 slow to a crawl

hi,
try filemon
http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx
--
Dragos CAMARA
MCSA Windows 2003 server


"d.barrow@virgin.net" wrote:

> The server was running fine until a week ago, but it's slowed to a
> disc-bound crawl. CPU time is 1-2%, Network activity is negligible,
> but the HDD is constantly in action. There have been no significant
> changes to the setup. Task manager shows no unusual activity. At the
> moment, no-one can even log in. Windows on the server take around 5
> minutes to open up, so detective work is horribly slow.
>
> Is there a way to determine which process is driving the HDD activity?
>
> Ideas for where to look next...most welcome.
>
> Thanks
>
>

 

[Worrab]

Re: Server 2003 slow to a crawl

On 12 Jul, 12:02, Dragos CAMARA <drago...@remove-this.hotmail.com>
wrote:
> hi,
> try filemonhttp://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx
> --
> Dragos CAMARA
> MCSA Windows 2003 server
>
> "d.bar...@virgin.net" wrote:
> > The server was running fine until a week ago, but it's slowed to a
> > disc-boundcrawl. CPU time is 1-2%, Network activity is negligible,
> > but the HDD is constantly in action. There have been no significant
> > changes to the setup. Task manager shows no unusual activity. At the
> > moment, no-one can even log in. Windows on the server take around 5
> > minutes to open up, so detective work is horribly slow.
>
> > Is there a way to determine which process is driving the HDD activity?
>
> > Ideas for where to look next...most welcome.
>
> > Thanks

Thanks everyone. It turned out to be a Hard Disc error right in the
middle of the event log. I guess that every time the event log was
written to, it generated an error. Ran chkdsk on the affected drive
and it pinpointed the problem.

Regards