From owner-freebsd-net@FreeBSD.ORG Sat Jun 28 14:12:27 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B2242865 for ; Sat, 28 Jun 2014 14:12:27 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7EDE02A75 for ; Sat, 28 Jun 2014 14:12:27 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1X0tMZ-0008Ug-HN for freebsd-net@freebsd.org; Sat, 28 Jun 2014 07:12:19 -0700 Date: Sat, 28 Jun 2014 07:12:19 -0700 (PDT) From: Beeblebrox To: freebsd-net@freebsd.org Message-ID: <1403964739522-5924518.post@n5.nabble.com> Subject: PXE boot using Grub bootloader fails at mountroot; no PXE devs. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jun 2014 14:12:27 -0000 I'm using grub2 as the pxe bootloader rather than BTX's pxeboot. I get Grub to load kernel and all necessary modules and boot. It goes as far as mountroot> and stops. "?" fails to show any pxe devices. If I recall correctly, when booting from BTX and upon hitting a mountroot problem, "?" is able to show pxe device. The kernel modules {nfscl.ko, nfsclient.ko, nfscommon.ko} are loaded through grub.cfg kfreebsd_module entries. Using the BTX pxeboot system boots and mounts everything normally. At this point, I could only think of two possibilities: A) the grub.cfg entry is wrong (which I don't think so since as stated above mountroot> "?" shows no available pxe devices). Or B) the more plausible reason is that I need to load some other module which will make the pxe devices become visible to the mountroot process. Grub's normal solution to this problem (pxechainloader $path/pxeboot) has been broken for some time unfortunately. I'd like to make sure that I am loading all the necessary modules through grub.cfg (for diskless clients) before heading over to the grub mail list with this problem. Server-side loaded modules: {nfsd.ko, nfslockd.ko, nfsserver.ko, nfs_common.ko, acl_nfs4.ko} within kernel: {nfscommon, nfssvc, nfs, nfscl, nfslock}. As a side comment, under BTX as long as one has "option root-path" in dhcpd.conf and a correct fsatb entry for "/", none of the below are needed in loader.conf - system is able to boot without these and mount ro (from fstab): boot.nfsroot.server="192.168.2.1" boot.nfsroot.path="/data/amd6" vfs.root.mountfrom="nfs:192.168.2.1:/data/amd64" vfs.root.mountfrom="nfs" Regards. ----- FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context: http://freebsd.1045724.n5.nabble.com/PXE-boot-using-Grub-bootloader-fails-at-mountroot-no-PXE-devs-tp5924518.html Sent from the freebsd-net mailing list archive at Nabble.com.