Date: Tue, 18 Apr 2017 15:09:36 +0100 From: tech-lists <tech-lists@zyxst.net> To: freebsd-questions@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Re: 10.3-stable random server reboots - finding the reason Message-ID: <7444bde9-a898-9e7d-103a-a0903422608d@zyxst.net> In-Reply-To: <20170418123424.GD74780@home.opsec.eu> References: <a7f787f8-486f-8221-ef8a-4535c4e1ae0c@zyxst.net> <20170418123424.GD74780@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 18/04/2017 13:34, Kurt Jaeger wrote: > 1) > echo '-Dh -S115200' > /boot.config > 2) > vi /boot/loader.conf > ------------ > console="comconsole" > comconsole_speed=115200 > ------------ > > Then: connect it to some kermit session from a different box, > and write a session log. This might capture some last gasp. > A bit more detail: Problem seems to be it's DRAC is broken. The server is a Dell R710 in a datacentre so I've not got physical access. I'd normally admin the hardware via the DRAC but it's non-functional now. The system won't boot without someone there plugging in a keyboard and pressing F2 to continue... arrrgh! "idrac failed press F2". It does boot, though. The DRAC normally shows fan speed and voltage amongst other things. Right now I'm looking for an in-band method of doing that on FreeBSD as obv the out-of-band method has failed. cpu temps look fine, cool. AIUI the DRAC is a chip on the motherboard and not a module that can be whipped out and replaced. For all I know, the DRAC might be causing the reboot if it's only intermittently dead. I don't know this though. It might be CPU or RAM, both of these can be swapped out, just need to capture the info... arrgh! -- J.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7444bde9-a898-9e7d-103a-a0903422608d>