Re: unresponsive system
- From: Amit Uttamchandani <atu13439@xxxxxxxx>
- Date: Thu, 24 Jan 2008 06:09:40 -0800
On Wed, 23 Jan 2008 16:01:31 -0500
Brian McKee <map@xxxxxxxxxxx> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All,
A little while back I was trying to fix a system that was producing
a continuous tone after being unused for a while, then logging in.
Now it's running a wee mite slow....
time top -n 1 > output.txt
real 67m42.116s
user 0m0.008s
sys 0m0.000s
Yep - it took it over an hour to run top once and put the output in a
file. Then it started beeping again.
I had to hard reboot it (the noise was driving me batty) and guess
what - output.txt is nowhere to be found!
I did see the file before I rebooted - cpu was 0%us 0%ni 89%id,
swap was 0k used and the first process listed was using less than 2%
cpu.
After the reboot it seems to run fine - the software RAID rebuilds
etc etc.
I can't seem to nail down what makes it start - I'm not actually
using the system at present.
I just set it up to do some testing and it's just sitting there idle.
Any suggestions what's going on here or how to troubleshoot further?
Brian
What kind of noise is it?
Coming from the hard drive?
Based on the above...if it takes forever to write to output.txt, it looks like hard drive is messed up.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Follow-Ups:
- Re: unresponsive system
- From: Brian McKee
- Re: unresponsive system
- References:
- unresponsive system
- From: Brian McKee
- unresponsive system
- Prev by Date: Re: OT: How to detect a keypress, and in which language?
- Next by Date: sid/xinerama: how to start app on specific screen
- Previous by thread: unresponsive system
- Next by thread: Re: unresponsive system
- Index(es):
Relevant Pages
|
|
