From owner-freebsd-stable@FreeBSD.ORG Wed Feb 17 01:28:05 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15A62106566C for ; Wed, 17 Feb 2010 01:28:05 +0000 (UTC) (envelope-from spork@bway.net) Received: from xena.bway.net (xena.bway.net [216.220.96.26]) by mx1.freebsd.org (Postfix) with ESMTP id C832D8FC0C for ; Wed, 17 Feb 2010 01:28:04 +0000 (UTC) Received: (qmail 22090 invoked by uid 0); 17 Feb 2010 01:28:03 -0000 Received: from unknown (HELO ?10.3.2.41?) (spork@96.57.144.66) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 17 Feb 2010 01:28:03 -0000 Date: Tue, 16 Feb 2010 20:28:03 -0500 (EST) From: Charles Sprickman X-X-Sender: spork@hotlap.local To: stable@freebsd.org Message-ID: User-Agent: Alpine 2.00 (OSX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Subject: netboot issues, 8.0, mfsroot mount failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Feb 2010 01:28:05 -0000 Howdy, I'm having some problems getting 8.0 to install over the network. I've got my dhcp, tftp and nfs server working well, and I've tested all three services from this host before attempting to boot over the network. pxeboot seems to work, and I see it get loaded via tftp. The kernel boots, and parses the options in loader.conf that exist in my nfs-exported 8.0 DVD fileset: [root@archive /home/spork/tmp]# cat /usr/local/netboot/freebsd8/boot/loader.conf mfsroot_load="YES" mfsroot_type="mfs_root" mfsroot_name="/boot/mfsroot" boot_multicons="YES" boot_serial="YES" console="comconsole,vidconsole" vfs.root.mountfrom="ufs:/dev/md0c" I see the kernel does find mfsroot and attaches it: md0: Preloaded image 4423680 bytes at 0xc0f6dfe0 But then when it's ready to mount the root filesystem, I get this: SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/md0c ROOT MOUNT ERROR: If you have invalid mount options, reboot, and first try the following from the loader prompt: set vfs.root.mountfrom.options=rw and then remove invalid mount options from /etc/fstab. It doesn't really state what the error is. It's hinting that it's read-only, but that seems odd. Even if it couldn't mount r/w, shouldn't it just drop to single-user at this point? Next it tries nfs: Trying to mount root from nfs: NFS ROOT: 192.168.1.111:/usr/local/netboot/freebsd8 em0: link state changed to UP And there it sits. Remotely I can't do anything. If I'm local, I can ctrl-alt-del a few times and then about a minute later it does an orderly restart. I'm not aware of a good way to snoop on nfs traffic, but tcpdump shows nfs traffic between the two hosts, which appears to be the client stat-ing a file or directory. tcpdump also shows some checksum errors, but I recall a few threads here mentioning that on Intel cards that generally is not a cause for concern. >From another host, I have no issues mounting that nfs filesystem r/w: root@h10[/home/spork]# mount_nfs 192.168.1.111:/usr/local/netboot/freebsd8 /mntroot@h10[/home/spork]# ls /mnt/ .cshrc HARDWARE.TXT boot.catalog media sbin .profile README.HTM cdrom.inf mnt stand 8.0-RELEASE README.TXT dev packages sys COPYRIGHT RELNOTES.HTM docbook.css proc tmp ERRATA.HTM RELNOTES.TXT etc rescue usr ERRATA.TXT bin lib root var HARDWARE.HTM boot libexec rr_moved root@h10[/home/spork]# touch /mnt/foo root@h10[/home/spork]# rm /mnt/foo root@h10[/home/spork]# umount /mnt Any ideas? I've got about a dozen remote boxes to upgrade, so I want to totally nail down this procedure. I've been putting off learning this for a few years, and now I've got an actual need for it. Thanks, Charles