SEO

Dear Guys,
My Slackware hdd is blinking non-stop & is very slow. Is it possible for me
to see what process is causing it?

Your help is much appreciated.

--
Thank & Regards,
CL

CL wrote:

> My Slackware hdd is blinking non-stop & is very slow. Is it possible for
> me to see what process is causing it?

top ?
--
Two Ravens
"...hit the squirrel..."

Two Ravens wrote:

> CL wrote:
>
>> My Slackware hdd is blinking non-stop & is very slow. Is it possible for
>> me to see what process is causing it?
>
> top ?

See also: http://www.ss64.com/bash/
--
Two Ravens
"...hit the squirrel..."

CL wrote:

> My Slackware hdd is blinking non-stop & is very slow. Is it possible
> for me to see what process is causing it?

It may not be a single process, but rather the system itself, for
example, if it's low on memory and using the disk for swap. What does
"cat /proc/meminfo" report?

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems and Network analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

"Two Ravens" <two-ravens@operamail.com> escreveu na mensagem
news:fZadnSTy4JU-8kjYRVnyugA@pipex.net...
> CL wrote:
>
>> My Slackware hdd is blinking non-stop & is very slow. Is it possible for
>> me to see what process is causing it?
>
> top ?
> --
> Two Ravens
> "...hit the squirrel..."


Deffective areas on the HDD surface can also slow the computer down. If you
can't pinpoint the software component that might be causing the frequent
disk access you could try running a disk analisys utility such as MHDD32
just to make sure.

Cheers
Paulo Costa

CL wrote:
> Dear Guys,
> My Slackware hdd is blinking non-stop & is very slow. Is it possible for me
> to see what process is causing it?
>

Sounds like your disk platters could be losing their magnetic media.

Have a look in your log files for entries like:

hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
hda: set_multmode: error=0x04 { DriveStatusError }

On Feb 16, 10:16 pm, Chris Sorenson <cso...@isd.net> wrote:
> CL wrote:
> > Dear Guys,
> > My Slackware hdd is blinking non-stop & is very slow. Is it possible for me
> > to see what process is causing it?
>
> Sounds like your disk platters could be losing their magnetic media.
>
> Have a look in your log files for entries like:
>
> hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> hda: set_multmode: error=0x04 { DriveStatusError }

Are you sure that those errors are due to "disk platters could be
losing their magnetic media".
Where did you get that information?

When I was running a 2.4.? kernel I did notice those exact lines on
bootup. I did fsck on disk but it looked OK. So I kept using it. I did
some reading about it and remember concluding (I can't remember why)
that it may have been caused by the fact that *THAT* hardrive had
originally been partitioned with a Maxtor utility to allow it to be
used under Win95 (plus the jumper had to be set to CS I think)

When I switched to a 2.6.? kernel (which was when Slackware 11.0 was
released) I noticed that those lines do not appear anymore. I have
been using that 80GB disk now for a few years and touch wood (hand on
head) it has been just fine.

regards - mm

On Feb 13, 12:22 am, "CL" <c...@screamx.com> wrote:
> Dear Guys,
> My Slackware hdd is blinking non-stop & is very slow. Is it possible for me
> to see what process is causing it?
> ...
CL:
Have you figured out the cause yet?

If not, I assume you've tried using "top", etc to figure what process
is causing it, but nothng came up. Then try the following approach:
Bring machine into telinit 1 state.
If you have any partitions on HD that you can unmount (like /home)
umount them - you won't be able to unmount / and /usr.
See if problem persists. If it does, then run "lsof" on the device
example: lsof /dev/hda. This will tell you what files are being used
at the moment.
there should *not* be many at all. Then try to make sense of the
results or post them here.

If there is no problem in telinit 1, then go into multiuser mode as
usual but "go slow" :-)
Don't log in as yourself (i.e. don't go into X/KDE/Gnome whatever),
but login as root and see what files are being used. Again try to make
sense of it or post here. Try to remove services and add them back
again to try to isolate the cause.

In other words is the HD doing that all the time even from the moment
pc is booting up in BIOS, or is there a later time at which it begins?
I would try to figure out at which point the HD light starts doing
what you describe.

Of course all this may be academic because maybe your HD is about to
go ballistic. In which case....have you backed up?

good luck

Dear All,
Thanks for your all additional info. Find out it is really the harddisk
being overloaded. Not sure what cause it. But I already split out the files
to different harddisk. Right now, Home Drive, Mail, Shared Folder all in
different harddisk. Doing manual raid.

--
CL
"Manimoto" <manimotomushi@hotmail.com> wrote in message
news:1171937650.981463.172610@a75g2000cwd.googlegr oups.com...
> On Feb 13, 12:22 am, "CL" <c...@screamx.com> wrote:
> > Dear Guys,
> > My Slackware hdd is blinking non-stop & is very slow. Is it possible for
me
> > to see what process is causing it?
> > ...
> CL:
> Have you figured out the cause yet?
>
> If not, I assume you've tried using "top", etc to figure what process
> is causing it, but nothng came up. Then try the following approach:
> Bring machine into telinit 1 state.
> If you have any partitions on HD that you can unmount (like /home)
> umount them - you won't be able to unmount / and /usr.
> See if problem persists. If it does, then run "lsof" on the device
> example: lsof /dev/hda. This will tell you what files are being used
> at the moment.
> there should *not* be many at all. Then try to make sense of the
> results or post them here.
>
> If there is no problem in telinit 1, then go into multiuser mode as
> usual but "go slow" :-)
> Don't log in as yourself (i.e. don't go into X/KDE/Gnome whatever),
> but login as root and see what files are being used. Again try to make
> sense of it or post here. Try to remove services and add them back
> again to try to isolate the cause.
>
> In other words is the HD doing that all the time even from the moment
> pc is booting up in BIOS, or is there a later time at which it begins?
> I would try to figure out at which point the HD light starts doing
> what you describe.
>
> Of course all this may be academic because maybe your HD is about to
> go ballistic. In which case....have you backed up?
>
> good luck
>