Date: Thu, 13 Apr 2006 23:37:09 -0400 From: Matthew Hagerty <matthew@digitalstratum.com> To: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics Message-ID: <443F18E5.5030005@digitalstratum.com> In-Reply-To: <443EE34A.2050906@bullseye.apana.org.au> References: <443E95C1.4030404@digitalstratum.com> <443E9C38.709@dial.pipex.com> <443EE34A.2050906@bullseye.apana.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew MacIntyre wrote:
> Alex Zbyslaw wrote:
>
> {...}
>
>> Several times now I have had Linux servers (and production quality
>> ones, not built by me ones :-)) die in a somewhat similar fashion.
>> In every case the cause has been either a flaky disk or a flaky disk
>> controller, or some combination.
>
> I've seen an instance of somewhat similar symptoms where a power supply
> was sagging out of spec on one supply rail some time after startup.
> When some disk activity happened, the extra power consumption caused the
> voltage to sag further triggering the disk going AWOL.
>
> At the time this started to happen, the power supply was more than 12
> months old.
>
> -------------------------------------------------------------------------
> Andrew I MacIntyre "These thoughts are mine alone..."
> E-mail: andymac@bullseye.apana.org.au (pref) | Snail: PO Box 370
> andymac@pcug.org.au (alt) | Belconnen ACT 2616
> Web: http://www.andymac.org/ | Australia
I considered power problems, however the server has dual redundant 400
Watt power supplies, and is in a server room and none of the other
machines in there are having problems like this one. I suppose it is
possible that both supplies are failing, but that seems highly unlikely?
Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?443F18E5.5030005>