Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Apr 2006 15:21:54 -0700
From:      soralx@cydem.org
To:        freebsd-hackers@freebsd.org
Subject:   Re: FreeBSD Crash without Errors, Warnings, or Panics
Message-ID:  <200604131521.55405.soralx@cydem.org>
In-Reply-To: <443EAFC0.6040308@dial.pipex.com>
References:  <443E95C1.4030404@digitalstratum.com> <443EA32B.408@digitalstratum.com> <443EAFC0.6040308@dial.pipex.com>

next in thread | previous in thread | raw e-mail | index | archive | help


> > 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200604131521.55405.soralx>