Re: etherboot & NFS problem

[Christoph Plattner <christoph.plattner@alcatel.at>]

Hi again !

First of all test the mount point on your local linux server:

	bash# mount -t nfs your_server:/tftpboot/xxxxxx /mnt/tmp

(Of course, you must have a /mnt/tmp directory !)

Further try following to nfs root for the diskless client:
2 ways:

ONE:	Use bootloader GNU Grub. Compile it with network support 
	(uses etherboot network drivers !!)
	Install boot loader to disk and boot from disk (on client)
	Now you are at the GRUB prompt:

	grub> bootp

	(Now you see the server and client address)

	grub> root (nd)

	(Use the network connction as root for the boot loader (not linux !)

	grub> kernel /tftpboot/xxxxxx/vmlinuz root=/dev/nfs 
			nfsroot=ip_of_server:/tftpboot/xxxx/root ip=........

	(All in one line, then the command ...)
	
	grub> boot

The advantage here is to try the kernel without any image and to use the 
kernel parameter line for the boot (no bootp or any automatic for the
first test (see /usr/src/linux/Documentation/nfsroot.txt, 
	/usr/doc/HOWTO/mini/NFS-Root, /usr/doc/HOWTO/BootPrompt-HOWTO).

The second way is to boot via ldlinux.sys (syslinux.cfg), like on the
RedHat boot disk (!). Here in syslinux.cfg the kernel parameter line can
also be added.

I prefer GRUB for all those experiements. I added support for diskless
boot of GRUB itself. So the boot image is nbgrub, and you never had to
use mknbi(-linux) any more !!!
With the use of the grub config file (menu.lst) you can also
automatcally
boot the linux, everything diskless !! (I use this at home !)

With friendly regards

	Christoph plattner

	


Rajesh Fowkar wrote:
> 
> On Tue, Oct 31, 2000 at 09:23:36AM +0100, Christoph Plattner wrote:
> 
> >
> >Hi in this mailing list !
> 
> Hi Christoph,
> 
> Thanks for the detailed explanation.
> 
> >
> >Your problem:
> >Recheck the /etc/exports file.
> 
> -------------------------------------------------
> [root@rhlinux /etc]# more exports
> /tftpboot/rajeshpc rajeshpc(rw,no_root_squash)
> /usr (ro)
> -------------------------------------------------
> 
> >Also recheck if all NFS server parts are running (sometimes
> >they brake, if an error occurs), use for example
> >       ps auxw | grep rpc
> 
> -------------------------------------------------
> [root@rhlinux /etc]#  ps auxw | grep rpc
> root       376  0.0  0.0     0    0 ?        SW   14:47   0:00 [rpciod]
> root       385  0.0  0.2  1156  560 ?        S    14:47   0:00 rpc.statd
> root       552  0.0  0.1  1104  396 ?        S    14:47   0:00 rpc.rquotad
> root      1147  0.0  0.3  1472  804 ?        S    15:09   0:00 rpc.mountd --no-nfs-version 3
> -------------------------------------------------
> 
> -------------------------------------------------
> [root@rhlinux /etc]# exportfs
> /tftpboot/rajeshpc
>                 rajeshpc.edp
> /usr            <world>
> -------------------------------------------------
> 
> >"Error -13": I got this also and I debugged the mountd for this.
> >I found out, that I wanted to export a path, which is also an NFS
> >part of another machine
> >
> >SERVER                 WORKSTATION which exports for DISKLESS     DISKLESS
> >holding /tftpboot      mounted /tftpboot from server
> >                       playing bootp server
> >                       exporting /tftpboot
> >
> 
> I have got only one linux machine here. ie.: this linux redhat server. I am currently trying out remote booting using etherboot on one of the diskless client using floppy booting.
> 
> My entire configuration looks to be correct. Above I have given the output of my configuration.
> I am using dhcp server here. My /etc/dhcpd.conf file contains the following :
> 
> --------------------------------------------------------------
> subnet 192.168.20.0 netmask 255.255.255.0 {
>      range 192.168.20.61 192.168.20.99;
>      default-lease-time 60000;
>      max-lease-time 72000;
>      option broadcast-address 192.168.20.255;
>      #option routers 239.252.197.1;
>      #option domain-name-servers 239.252.197.2, 239.252.197.3;
>      option domain-name "edp";
> }
> 
> host rajeshpc {
>         hardware ethernet 00:40:95:22:90:95;
>         fixed-address 192.168.20.61;
>         filename "/tftpboot/kernel";
>       }
> --------------------------------------------------------------
> 
> I am surprised to see that kernel boots from the same directory /tftpboot and then why while mounting root filesysetm I am getting error ?
> 
> Am I doing something wrong.
> 
> Thanks again for the help.
> 
> Regards
> 
> Rajesh
> 
> ===========================================================================
> This Mail was sent to netboot mailing list by:
> Rajesh Fowkar <Mail@dempos.com>
> To get help about this list, send a mail with 'help' as the only string in
> it's body to majordomo@baghira.han.de. If you have problems with this list,
> send a mail to netboot-owner@baghira.han.de.

-- 
  +--------V--------+	Christoph.Plattner@alcatel.at
  |  A L C A T E L  |	-----------------------------
  +-----------------+	Phone: +43 1 27722 3706	
         T A S		Fax:   +43 1 27722 3955
===========================================================================
This Mail was sent to netboot mailing list by:
Christoph Plattner <christoph.plattner@alcatel.at>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.