From owner-freebsd-questions@freebsd.org Tue Dec 12 18:31:12 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F413EA21C9 for ; Tue, 12 Dec 2017 18:31:12 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (ns.dreamchaser.org [66.109.141.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 52AAA6A430 for ; Tue, 12 Dec 2017 18:31:11 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from breakaway.dreamchaser.org (breakaway [192.168.151.122]) by nightmare.dreamchaser.org (8.15.2/8.15.2) with ESMTP id vBCIUxWX044594; Tue, 12 Dec 2017 11:30:59 -0700 (MST) (envelope-from freebsd@dreamchaser.org) From: Gary Aitken Subject: Re: Subject: Thunderbird causing system crash, need guidance Reply-To: freebsd@dreamchaser.org To: Polytropon Cc: Adam Vande More , FreeBSD Questions References: <201712110045.vBB0jCTQ078476@nightmare.dreamchaser.org> <38e2ef70-fa1b-25bf-4447-752006418d0a@dreamchaser.org> <20171211135803.d1aff6c8.freebsd@edvax.de> Message-ID: <5fbcd05c-ce12-b1a4-a9e9-79276dad7183@dreamchaser.org> Date: Tue, 12 Dec 2017 11:30:26 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171211135803.d1aff6c8.freebsd@edvax.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (nightmare.dreamchaser.org [192.168.151.101]); Tue, 12 Dec 2017 11:31:00 -0700 (MST) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Dec 2017 18:31:12 -0000 On 12/11/17 05:58, Polytropon wrote: > On Sun, 10 Dec 2017 21:56:16 -0700, Gary Aitken wrote: >> On 12/10/17 19:02, Adam Vande More wrote: >>> On Sun, Dec 10, 2017 at 6:45 PM, Gary Aitken wrote: >> However, I'm confused. >> Upon reboot, the system checks to see if file systems were properly >> dismounted and is supposed to do an fsck. Since those don't show up >> in messages, I can't verify this, but I'm pretty certain it must have >> thought it was clean, which it wasn't. (One reason I'm pretty certain >> is the time involved when run manually as you suggested). > > This is the primary reason for setting > > background_fsck="NO" Already had that set for just that reason. > in /etc/rc.conf - if you can afford a little downtime. > The background fsck doesn't have all the repair capabilities > a forced foreground check has, to it _might_ leave the file > system in an inconsistent state, and the system runs with > that unclean partition. > >> The file system in question was mounted below "/". >> Does the system only auto-check file systems mounted at "/"? > > Yes, / is the first file system it checks. The two last > fields in /etc/fstab control what fsck will check, and > /etc/rc.conf allows additional flags for those automatic > checks. The ordering part I understand; what I don't understand is why it (as I recall) rebooted successfully with no warnings in spite of the background_fsck="NO" being set and when one of the disks apparently didn't fsck properly. I thought it should have halted in single-user mode and waited for me to do a full fsck manually. Unfortunately, the fsck output is not printed to the log, and I logged in as root on the vt0 device, so it had scrolled off by the time I went to look for it. A good reason never to log into the vt0 device. Is there any way to get the "transient" boot-time fsck and other messages recorded in the log? Gary