Re: 7.1 System Crashing



On Tue, Apr 14, 2009 at 8:49 PM, Fbsd1 <fbsd1@xxxxxxxxxxxxxxx> wrote:
APseudoUtopia wrote:

My FreeBSD 7.1-RELEASE-p3 system has gone down a few times in the last
two days. I'm trying to figure out why, but there is nothing in
/var/log/messages or dmesg about the incident.

Here's the output from the `last` command:
User      ttyp0    1.2.3.4    Tue Apr 14 19:02   still logged in
User      ttyp0    1.2.3.4    Tue Apr 14 18:52 - 19:02  (00:09)
reboot           ~                         Tue Apr 14 18:52
User      ttyp0    1.2.3.4    Tue Apr 14 18:42 - crash  (00:09)
User      ttyp0    1.2.3.4    Tue Apr 14 16:06 - 18:42  (02:36)
User      ttyp0    1.2.3.4    Tue Apr 14 11:23 - 12:53  (01:29)
reboot           ~                         Tue Apr 14 07:44
User      ttyp0    1.2.3.4    Mon Apr 13 20:01 - 22:58  (02:57)
User      ttyp0    1.2.3.4    Mon Apr 13 19:56 - 20:01  (00:04)
User      ttyp0    1.2.3.4    Mon Apr 13 19:31 - 19:56  (00:25)
User      ttyp0    1.2.3.4    Sun Apr 12 15:02 - 16:15  (01:12)
User      ttyp0    1.2.3.4    Sun Apr 12 14:48 - 15:02  (00:14)
reboot           ~                         Sun Apr 12 14:48
shutdown         ~                         Sun Apr 12 14:45
User      ttyp0    1.2.3.4    Sun Apr 12 14:24 - shutdown  (00:21)
User      ttyp0    1.2.3.4    Sat Apr 11 13:03 - 17:00  (03:56)
wtmp begins Wed Apr  1 21:21:28 UTC 2009



As you can see, the system reboot several times, and crashed the most
recent time. Only one of the shutdown/reboots listed is valid - the
furthest one.
I have no idea why it is rebooting/crashing. It has been completely
stable until about 1-2 days ago. If anyone can direct me to post the
output to any commands or any log messages, I'd be more than willing
to do so in order to help anyone diagnose my problem.

Thank you for your time.



What you are experiencing are the early warning signs of disk drive failure
or over heating problems.

Before doing any thing else make backup of your user data if you have not
done so already.

Then open your box and use a small brush and a can of compressed air to blow
the dust off the motherboard and the fans. Give special attention to the fan
in the power supply. If PC is older than 3 years or has over 1 year of
continues use then replace the power supply.

IF problem still happens replace hard drive.




The system is in a colocation center which I don't have access to. The
HDD crashed several months ago and was replaced by a brand new drive
(or so I was told....). So I'm leaning towards a heat or PSU problem.
I installed Healthd on the system to monitor such things, however it
didn't detect the hardware properly. Apparently the voltage in my CPU
core was 0.00, as was the temperature. Is there any other way to
monitor these things?

Everyone: Thanks for all the help. I'll open up a ticket with my host
to get them to look at it.
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: 7.1 System Crashing
    ... Here's the output from the `last` command: ... As you can see, the system reboot several times, and crashed the most ... What you are experiencing are the early warning signs of disk drive failure or over heating problems. ... Then open your box and use a small brush and a can of compressed air to blow the dust off the motherboard and the fans. ...
    (freebsd-questions)
  • Re: Command or setting to force monitor on?
    ... Invoke the Task Scheduler ... I set up a .cmd file to run the ping command you suggested and then tested ... Both tasks work fine, but upon wakeup, the monitor doesn't turn on. ...
    (microsoft.public.windowsxp.general)
  • Re: computer wont boot
    ... of, concerning the fans. ... The monitor screen starts up with a black background and a "monitor self ... (but since I can't power down normally, I'm unplugging the CPU). ... The obvious problem seems to be the video card and it really does not ...
    (microsoft.public.windowsxp.hardware)
  • Re: Command or setting to force monitor on?
    ... I set up a batch file containing the commands to first start IE, ... the keystrokes script. ... could move to the keystrokes command. ... But the monitor still stayed off past the time I set the ping cmd file to ...
    (microsoft.public.windowsxp.general)
  • Re: problem after installing fedora core 6
    ... the monitor's refresh-rate should be detected by most distro's... ... your monitor is necessary to get these specs). ... get you to a command prompt... ... I said you should issue 'nano /etc/X11/xorg.conf', nano is a text edit so ...
    (comp.os.linux.setup)