From owner-freebsd-stable@freebsd.org Mon Jun 4 23:22:43 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 805B3FE4610 for ; Mon, 4 Jun 2018 23:22:43 +0000 (UTC) (envelope-from dsamms@nw-ds.com) Received: from web.nwds.us (web2.nwds.us [135.84.180.41]) (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 109B56D687; Mon, 4 Jun 2018 23:22:42 +0000 (UTC) (envelope-from dsamms@nw-ds.com) Received: from localhost (localhost [127.0.0.1]) by web.nwds.us (Postfix) with ESMTP id 58144213AF; Mon, 4 Jun 2018 17:22:42 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nw-ds.com; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:reply-to:from:from:references:subject:subject; s= default; t=1528154562; x=1529968963; bh=oERJ7RPFROK4j1rj6bseXJxe NT7JvtB5qnGwhVEYtdE=; b=PNZZ6s3U15tQdQSNjRVz3mGut6CvnqSFurRjOWtE rObDPVQ6anNZB8FF5ZkXLmDo0iX9sXF3mlPQunrKslvRij4Iyrero8BKfH5Eqtx0 h/mC+0xgmNj3IfRjw1Xsb68a1h1jQWC0d8XRQaMnIkwpZlppAG1VfpIyA+TZNLs3 7V9N11A4d+UKRi3F5A897yDN9IelKBUteq5BVTh2GxD+06tlqDLQLDuYOvc1EO3Y PA6BdT8w8Wgsn8uvtgpNPeLZxLUj80sq1ClU3K8jGiiefy5AVbR0SLy4yQxfDd0I 67yVY6ZhuxuSnJxqdrQSrubf9Om7UZg0q3rGahxmbs2HoQ== X-Virus-Scanned: Debian amavisd-new at web.nwds.us Received: from web.nwds.us ([127.0.0.1]) by localhost (smtp-1.nwds.us [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id hFBOzdjsOLQF; Mon, 4 Jun 2018 17:22:42 -0600 (MDT) Received: from xeon.localdomain (host-98-127-45-240.grf-mt.client.bresnan.net [98.127.45.240]) (Authenticated sender: dsamms@nw-ds.com) by web.nwds.us (Postfix) with ESMTPSA id C368521378; Mon, 4 Jun 2018 17:22:41 -0600 (MDT) Subject: Re: Fwd: 11.2-Beta3 fails to boot: legacy mode ZFS To: freebsd-stable@freebsd.org References: <8c5d0d8b-e6ca-5694-5ef8-6e75f30e7756@freebsd.org> Cc: Allan Jude , jrm@FreeBSD.org, eugen@grosbein.net From: David Samms Reply-To: 2yt@gmx.com Message-ID: <520ede06-1f48-a67f-6ee5-5ed3c8ee682a@nw-ds.com> Date: Mon, 4 Jun 2018 17:22:40 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <8c5d0d8b-e6ca-5694-5ef8-6e75f30e7756@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 23:22:43 -0000 All, My first response appears not to have made the list, so am reposting. The problem is SOLVED however. The system in question is an Intel s1200kb with Xeon processor but no COM port, only USB so console access is not available. Make debugging more difficult. On 06/04/18 13:59, Allan Jude wrote: > When you say it "failed at ZFS", what do you mean? Sorry for the poor description. I get all the normal boot prompts and the system starts to boot then suddenly without any error message or output to the console, reboots. The last text I can see is... ZFS... This occurs very early in the boot cycle and way before mounting / or going into single user mode > There will be multiple 'boot prompts' as well. > > The system starts up, and boot1/boot2 happen. This is where you'll get > the first GELI password prompt. > > This will start the loader, which draws the beastie menu. After the > menu, the kernel modules indicated in /boot/loader.conf are loaded, then > the text 'booting' is displayed, and the screen is cleared, and the > kernel starts loading. Reboots HERE. Before mount-root prompt. > Later on you get the mount-root prompt if something goes wrong. > > Query: Do you happen to have VirtualBox or the nVidia driver kernel > modules loaded? This was causing problems for some other people, where > the system would boot up, but instantly panic once the VirtualBox > networking driver was loaded, since the vbox driver module needs to be > compiled against the 11.2 source code to work with an 11.2 kernel. > > If this doesn't seem to be the problem: > Can you send the contents of /boot/loader.conf, /etc/rc.conf, 'zpool > list' and 'zfs list' Allan, thank you so much for this suggestion. Commenting out all ports based kernel modules resolved the problem. In the past upgrades I have had ports based kernel modules fail to load or crash when used, but I have never seen the loading of a ports based kernel modules crash the boot process. Would suggest "we" make it clear in the upgrade instructions to disable ALL optional kernel modules. I expect Nvidia to fail and require a recompile before working with a new version of FreeBSD, but in the past I have always been able to boot to single user mode. Thank you guys for terrific support! > On 2018-06-03 11:28 PM, Warner Losh wrote: >> I think this is on your side of the wall... >> >> Warner >> >> ---------- Forwarded message --------- >> From: David Samms > >> Date: Sun, Jun 3, 2018, 7:08 PM >> Subject: 11.2-Beta3 fails to boot: legacy mode ZFS >> To: > >> >> >> Hello, >> >> Background: >> ------------- >> System was originally installed with an 11.0 CD. At the time I tried to >> get UEFI to work, but ended up booting in legacy/BIOS mode. Upgrading to >> 11.1 was uneventful. The system has a single SSD with full disk >> encryption and ZFS. Again, nothing special, just the user selectable >> install options from the 11.0 CD. >> >> Current Failure: >> ------------------ >> After running "freebsd-update upgrade -r 11.2-BETA3" the system failed >> on reboot. Disk encryption keys can be entered, boot prompt appears, >> boot starts but fails at ZFS. Reboots with no info sent to the console. >> >> Luckily, selecting kernel.old at the boot prompt works fine. >> >> Any ideas? Need more info? What can I do to help track down the bug? >> >> Thank you >> >> -- >> David Samms >> _______________________________________________ >> freebsd-stable@freebsd.org mailing >> list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "freebsd-stable-unsubscribe@freebsd.org >> " > > -- David Samms