From owner-freebsd-current@FreeBSD.ORG Wed Jan 30 11:18:21 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EE506CAB for ; Wed, 30 Jan 2013 11:18:21 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by mx1.freebsd.org (Postfix) with ESMTP id C9A4D94 for ; Wed, 30 Jan 2013 11:18:21 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,567,1355126400"; d="scan'208";a="7395983" Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 30 Jan 2013 03:18:15 -0800 Received: from vmwexceht05-prd.hq.netapp.com (vmwexceht05-prd.hq.netapp.com [10.106.77.35]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r0UBIF0n011523; Wed, 30 Jan 2013 03:18:15 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0328.009; Wed, 30 Jan 2013 03:18:15 -0800 From: "Eggert, Lars" To: Craig Rodrigues Subject: Re: mounting root from NFS via ROOTDEVNAME Thread-Topic: mounting root from NFS via ROOTDEVNAME Thread-Index: AQHN/WoQ3bLz4fhIpUOOqbDPPwYM3JhhN1MAgADtYYCAAB2QgA== Date: Wed, 30 Jan 2013 11:18:14 +0000 Message-ID: References: <19F92E0C-F004-4F16-A5FC-A10DF84BDCCF@netapp.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.106.53.51] Content-Type: text/plain; charset="us-ascii" Content-ID: <1D18576AD0CF1B45B1A8358AA4F6CE08@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 11:18:22 -0000 Hi, On Jan 30, 2013, at 10:32, "Eggert, Lars" wrote: > On Jan 29, 2013, at 20:22, Craig Rodrigues wrote= : >> In src/sys/boot/common/boot.c which is part of the loader (not the kerne= l), >> if you look in the getrootmount() function, >> you will see that the loader will try to figure out where the root file >> system >> is by parsing /etc/fstab, and looking for the "/" mount. >>=20 >> So, if your kernel is located in: >>=20 >> /usr/home/elars/dst/boot/kernel/kernel >>=20 >> Then create a file /usr/home/elars/dst/etc/fstab file with something lik= e: >>=20 >> # Device Mountpoint FSType >> Options Dump Pass >> 10.11.12.13:/usr/home/elars/dst/ / nfs ro 0 = 0 >=20 > Thanks, will try that! doesn't work. The kernel never leaves the "DHCP/BOOTP timeout for server"-loop unless I h= and out a root-path option via DHCP. I tried your tip above, I tried setting ROOTDEVNAME in the kernel, I create= d a /boot.config with "-r" in it on the NFS root - all to no avail.=20 >> Alternatively, if you don't want to create an /etc/fstab file, then >> you could put something like this in your loader.conf file: >>=20 >> vfs.root.mountfrom=3Dnfs:10.11.12.13:/usr/home/elars/dst >=20 > Will try that too, but not sure if this works with our custom loader. Doesn't seem to work either. Lars=