Re: Previously working PXE setup now fails

Hi and thanks for your input. If I may, I have several more Q's regarding
this issue:

> As I think I've mentioned before, a NFSv4 root fs won't work, so don't
> bother trying...
Q1: I did not realise that. I took out the "V4: " in exports. However, is it
possible to have a mixed-mode, something like /data/amd64 as V3 but /home as
V4?

Q2: I now get to the BTX loader, wireshark shows correct mount call
"192.168.2.3, 192.168.2.1, MOUNT, V3 MNT Call (Reply In 14072) /data/amd64".
Unfortunately, I get a complete black screen when I hit <enter> from BTX (it
looks like a lock-up) and wireshark shows no traffic for the problem.

To get to this point, I re-anabled some of what I had taken out before, and
I now forget which config options are necessary at this point. What I have:
(always had this) fstab: 192.168.2.1:/data/amd64  /  nfs  ro 0 0

boot/loader.conf:
boot.nfsroot.server="192.168.2.1"
boot.nfsroot.path="/data/amd64"
##_re-enabled_##
vfs.root.mountfrom="nfs:192.168.2.1:/data/amd64"
vfs.root.mountfrom="nfs"
boot.nfsroot.options="nolockd"
vfs.root.mountfrom.options="ro"

re-enabled in dhcpd.conf
option root-path "192.168.2.1:/data/amd64"; 

I can't figure out what needs to be modified and what options can be
removed?

Thanks for your help.



-----
FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS
--
View this message in context: http://freebsd.1045724.n5.nabble.com/Previously-working-PXE-setup-now-fails-tp5919662p5923355.html
Sent from the freebsd-current mailing list archive at Nabble.com.