Date: Mon, 28 Jan 2013 15:13:44 +0000 From: "Eggert, Lars" <lars@netapp.com> To: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: mounting root from NFS via ROOTDEVNAME Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F671642@SACEXCMBX01-PRD.hq.netapp.com>
next in thread | raw e-mail | index | archive | help
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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D4D47BCFFE5A004F95D707546AC0D7E91F671642>