From owner-freebsd-current@FreeBSD.ORG Mon Jan 28 15:13:54 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9A771CE6 for ; Mon, 28 Jan 2013 15:13:54 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 3F68E230 for ; Mon, 28 Jan 2013 15:13:53 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,551,1355126400"; d="scan'208";a="13011365" Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 28 Jan 2013 07:13:47 -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 r0SFDkda018562 for ; Mon, 28 Jan 2013 07:13:47 -0800 (PST) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.51]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0328.009; Mon, 28 Jan 2013 07:13:45 -0800 From: "Eggert, Lars" To: "freebsd-current@freebsd.org" Subject: mounting root from NFS via ROOTDEVNAME Thread-Topic: mounting root from NFS via ROOTDEVNAME Thread-Index: AQHN/WoQ3bLz4fhIpUOOqbDPPwYM3A== Date: Mon, 28 Jan 2013 15:13:44 +0000 Message-ID: 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: <1BD0C6361EBA6146BDD9332C516FA563@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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: Mon, 28 Jan 2013 15:13:54 -0000 Hi, I'm trying to netboot a system where the root device is specified in the ke= rnel via ROOTDEVNAME: options BOOTP options BOOTP_NFSROOT options BOOTP_NFSV3 options BOOTP_COMPAT options BOOTP_WIRED_TO=3Dem4 options ROOTDEVNAME=3D\"nfs:10.11.12.13:/usr/home/elars/dst\" I was under the assumption that specifying a ROOTDEVNAME in the kernel conf= ig would override the "root-path" option in DHCP, or at least take effect w= hen "root-path" wasn't provided via DHCP, but that doesn't seem to be the c= ase. The system configures it's address correctly over em4, but then enters= a loop: em4: link state changed to UP Received DHCP Offer packet on em4 from 0.0.0.0 (accepted) (no root path) Sending DHCP Request packet from interface em4 (XX:XX:XX:XX:XX:XX) Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) DHCP/BOOTP timeout for server 255.255.255.255 Received DHCP Ack packet on em4 from 0.0.0.0 (accepted) (no root path) DHCP/BOOTP timeout for server 255.255.255.255 ... If I hand out a root path via DHCP the system boots fine, but the idea here= is to be able to boot different root devices without needing to diddle dhc= pd.conf. Can this be done? Thanks, Lars=