From owner-freebsd-questions@freebsd.org Thu Dec 7 03:18:20 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 DC12CE99EE8 for ; Thu, 7 Dec 2017 03:18:20 +0000 (UTC) (envelope-from srs0=ahgx=dd=mail.sermon-archive.info=doug@sermon-archive.info) Received: from mail.sermon-archive.info (sermon-archive.info [71.177.216.148]) by mx1.freebsd.org (Postfix) with ESMTP id C8E6572AC8 for ; Thu, 7 Dec 2017 03:18:19 +0000 (UTC) (envelope-from srs0=ahgx=dd=mail.sermon-archive.info=doug@sermon-archive.info) Received: from [10.0.1.251] (mini [10.0.1.251]) by mail.sermon-archive.info (Postfix) with ESMTPSA id 3ysgT50jyQz2fjVG for ; Wed, 6 Dec 2017 19:10:01 -0800 (PST) From: Doug Hardie Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Error Message at end of boot Message-Id: <1F79D9DB-E67E-4446-A81B-C9A3ADE4C46B@mail.sermon-archive.info> Date: Wed, 6 Dec 2017 19:10:00 -0800 To: "freebsd-questions@freebsd.org Questions" X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at mail X-Virus-Status: Clean 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: Thu, 07 Dec 2017 03:18:21 -0000 I have one system (11.1 generic installed via freebsd-update) that = gives the message: Dec 6 18:31:24 Backup kernel: FAILED as the last message at the end of the boot process. Messages from ports = starting all precede it. Digging through the kernel source, the only = places I find such a message are: ./geom/raid/g_raid.c: return ("FAILED"); ./geom/raid/g_raid.c: return ("FAILED"); ./geom/raid/g_raid.c: return ("FAILED"); This seems a bit odd as there is no raid hardware or software being used = on this system. The system completes the boot process, although it = seems quite slow to do so, and then runs just fine. I don't see any = issues with the system. Everything seems to work. Any ideas how to = figure out what is causing that error message? -- Doug