From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 13 22:22:39 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5038E16A402 for ; Thu, 13 Apr 2006 22:22:39 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd4mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 788FC43D55 for ; Thu, 13 Apr 2006 22:22:37 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from pd4mr2so.prod.shaw.ca (pd4mr2so-qfe3.prod.shaw.ca [10.0.141.213]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXO00H9DM4KT500@l-daemon> for freebsd-hackers@freebsd.org; Thu, 13 Apr 2006 16:21:56 -0600 (MDT) Received: from pn2ml6so.prod.shaw.ca ([10.0.121.150]) by pd4mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXO00DBYM4KUX40@pd4mr2so.prod.shaw.ca> for freebsd-hackers@freebsd.org; Thu, 13 Apr 2006 16:21:56 -0600 (MDT) Received: from soralx.cydem.org ([24.87.27.3]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IXO003SBM4KE210@l-daemon> for freebsd-hackers@freebsd.org; Thu, 13 Apr 2006 16:21:56 -0600 (MDT) Date: Thu, 13 Apr 2006 15:21:54 -0700 From: soralx@cydem.org In-reply-to: <443EAFC0.6040308@dial.pipex.com> To: freebsd-hackers@freebsd.org Message-id: <200604131521.55405.soralx@cydem.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline References: <443E95C1.4030404@digitalstratum.com> <443EA32B.408@digitalstratum.com> <443EAFC0.6040308@dial.pipex.com> User-Agent: KMail/1.9.1 Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 22:22:39 -0000 > > Hmm, that just seems odd that a disk controller just vanishing would > > not cause some sort of console message? Even if the disk device is > > gone, /dev/console should still be intact to display an error, no? > > Also, a disk device that is all of a sudden missing seems pretty > > serious to me, since a disk is one of the main devices that modern > > OSes cannot run without (generally speaking.) I would think *some* > > console message should be warranted. > > Not if syslogd tries to access the disk :-( All can say is that I have > seen three Linux boxes go this way; I've never had this kind of failure > on a BSD box (touch wood) so all I can do is speculate about the I have. I've got a Seagate X15k SCSI HDD with SCA2->68pin adapter, and sometimes it used to lose power and shut off (bad contact in the adapter perhaps). FreeBSD would spit SCSI diagnostic messages onto the console about failed field-replacable unit (which I couldn't see in X Windows), restart the HDD a few times (at this point the machine would hang until HDD is restarted), and then reboot (panic?). Timestamp: 0x443EC707 [SorAlx] http://cydem.org.ua/ ridin' VN1500-B2