Date: Wed, 23 Apr 2003 18:26:23 +0300 (EEST) From: "BigBrother (BigB3)" <bigbrother@bonbon.net> To: K Anderson <freebsduser@attbi.com> Cc: freebsd-questions@freebsd.org Subject: Re: Diskless Workstation Boot - kernel.diskless can't parse file... Message-ID: <20030423182045.A84894@bigb3server.bbcluster.gr> In-Reply-To: <3EA62535.5000805@attbi.com> References: <012901c308a1$6b8ee6b0$e203a8c0@macedon> <3EA62535.5000805@attbi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<..>
> >> hardware ethernet 00:0b:db:13:90:ab;
> >> fixed-address 192.168.100.200;
> >> next-server 192.168.100.105;
> >> filename "kernel.diskless";
> >> option root-path "192.168.100.105:/diskless_root";
> >>}
<...>
>
> Hmm, thanks for your response I managed to get a little further.
> 1) Kernel is loading and booting.
> 2) DHCP got root path - rootfs 192.168.100.105:/diskless_boot hostname
> bailey
> 3) Adjusted interface xl0
> 4) Shutdown interface faith0
> 5) panic: nfs_boot: mountd root, error=72
> (how about meaningfull error messages like..you dummy create something)
>
This means that the machine cannot mount the root filesystem.
Check whether on your server the /diskless_root partition is exported
to this client, or the portmap,nfsd,and mountd daemons are running also.
In my diskless setup I have
hardware ethernet 00:50:ba:1d:f2:38;
next-server 192.168.3.200;
fixed-address iapetos.vlsi.gr;
filename "/tftpboot/kernel";
option root-path "192.168.3.200:/";
while the export file of the server is:
/ -ro -alldirs -maproot=root: -network 192.168.3.0 -mask 255.255.255.0
/usr -ro -alldirs -maproot=root: -network 192.168.3.0 -mask 255.255.255.0
/var -ro -alldirs -maproot=root: -network 192.168.3.0 -mask 255.255.255.0
This works fine for me, and has the added benefit thatI only upgrade my
server and all the diskless machines are upgraded also. Also it is secure
because the server exports read-only the partitions.
Check any syslog messages for denied mount attempts. Also check that in
the /etc/fstab entry for the diskless you DONT specify a mount for the '/'
filesystem. The '/' is mounted using the bootp request.
rgz,
BB
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030423182045.A84894>