Date: Tue, 16 Feb 2010 18:49:32 -0800 From: Garrett Cooper <yanefbsd@gmail.com> To: Charles Sprickman <spork@bway.net>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: netboot issues, 8.0, mfsroot mount failure Message-ID: <7d6fde3d1002161849gacd620cpe8a56c25bffa32bd@mail.gmail.com> In-Reply-To: <alpine.OSX.2.00.1002162009030.840@hotlap.local> References: <alpine.OSX.2.00.1002162009030.840@hotlap.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 16, 2010 at 5:28 PM, Charles Sprickman <spork@bway.net> wrote:
> Howdy,
>
> I'm having some problems getting 8.0 to install over the network. =A0I'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. =A0The kernel bo=
ots,
> and parses the options in loader.conf that exist in my nfs-exported 8.0 D=
VD
> fileset:
>
> [root@archive /home/spork/tmp]# cat
> /usr/local/netboot/freebsd8/boot/loader.conf
> mfsroot_load=3D"YES"
> mfsroot_type=3D"mfs_root"
> mfsroot_name=3D"/boot/mfsroot"
> boot_multicons=3D"YES"
> boot_serial=3D"YES"
> console=3D"comconsole,vidconsole"
> vfs.root.mountfrom=3D"ufs:/dev/md0c"
>
> I see the kernel does find mfsroot and attaches it:
>
> md0: Preloaded image </boot/mfsroot> 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 fr=
om
> the loader prompt:
>
> =A0 =A0 set vfs.root.mountfrom.options=3Drw
>
> and then remove invalid mount options from /etc/fstab.
>
> It doesn't really state what the error is. =A0It's hinting that it's
> read-only, but that seems odd. =A0Even 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. =A0Remotely I can't do anything. =A0If I'm local, I ca=
n
> 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 nf=
s
> traffic between the two hosts, which appears to be the client stat-ing a
> file or directory. =A0tcpdump also shows some checksum errors, but I reca=
ll 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/freebsd=
8
> /mntroot@h10[/home/spork]# ls /mnt/
> .cshrc =A0 =A0 =A0 =A0 =A0HARDWARE.TXT =A0 =A0boot.catalog =A0 =A0media =
=A0 =A0 =A0 =A0 =A0 sbin
> .profile =A0 =A0 =A0 =A0README.HTM =A0 =A0 =A0cdrom.inf =A0 =A0 =A0 mnt =
=A0 =A0 =A0 =A0 =A0 =A0 stand
> 8.0-RELEASE =A0 =A0 README.TXT =A0 =A0 =A0dev =A0 =A0 =A0 =A0 =A0 =A0 pac=
kages =A0 =A0 =A0 =A0sys
> COPYRIGHT =A0 =A0 =A0 RELNOTES.HTM =A0 =A0docbook.css =A0 =A0 proc =A0 =
=A0 =A0 =A0 =A0 =A0tmp
> ERRATA.HTM =A0 =A0 =A0RELNOTES.TXT =A0 =A0etc =A0 =A0 =A0 =A0 =A0 =A0 res=
cue =A0 =A0 =A0 =A0 =A0usr
> ERRATA.TXT =A0 =A0 =A0bin =A0 =A0 =A0 =A0 =A0 =A0 lib =A0 =A0 =A0 =A0 =A0=
=A0 root =A0 =A0 =A0 =A0 =A0 =A0var
> HARDWARE.HTM =A0 =A0boot =A0 =A0 =A0 =A0 =A0 =A0libexec =A0 =A0 =A0 =A0 r=
r_moved
> root@h10[/home/spork]# touch /mnt/foo
> root@h10[/home/spork]# rm /mnt/foo
> root@h10[/home/spork]# umount /mnt
>
> Any ideas? =A0I've got about a dozen remote boxes to upgrade, so I want t=
o
> totally nail down this procedure. =A0I've been putting off learning this =
for a
> few years, and now I've got an actual need for it.
I'll be in your shoes in a little bit... I ran into some issues
when I last tried with NFSv3 on a Solaris server so we'll see how
things go in the second go-around [with a FreeBSD nfs rootfs server],
but 7.x netbooted and 8.x didn't when I tried last; the 7.x images
have some secret sauce fixes for PXE booting -- the ones I know of are
as follows (apply to loader.conf as you feel fit):
vfs.root.mountfrom=3D"nfs"
boot.nfsroot.path=3D"/absolute/path/to/netboot/dir"
boot.nfsroot.server=3D"nfs-server-ip-addr"
There were also some code changes made to `fix' netbooting with
pxeloader, but I'm not sure if they're applicable or needed in 8.x,
and I'm not sure what the actual changes are TBH...
Cheers,
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d1002161849gacd620cpe8a56c25bffa32bd>