On Saturday 05 October 2002 09:29, Stew Benedict wrote:
> On Sat, 5 Oct 2002, Brent Hasty wrote:
> > On Saturday 05 October 2002 05:40, Stew Benedict wrote:
> > > On Sat, 5 Oct 2002, Brent Hasty wrote:
> > > > 2 issues
> > >
> > > 1 issue - your mailer borks the "Reply To:" :)
> > >
> > > > fist all my terminals are using the eepro100 ic with pxe. how do I
> > > > set the server up to boot the terminals using these nics with pxe?
> > >
> > > Sorry. Several people have asked about PXE. I know Erwan did some PXE
> > > work for the clustering project, and I read the docs, but I don't have
> > > PXE capable hardware to implement/test. Patches welcome :)
> > >
> > > > second is when booting the terminals (using a boot flopy) it fails at
> > > > mounting the root filesystem. I have 5 partitions /, /usr, /var,
> > > > /home, /tmp
> > > >
> > > > my exports lists the
> > > >
> > > > / (ro,all_squash)
> > > > /home 192.168.1.0/255.255.255.0(rw, root_squash)
> > > >
> > > > do i need to modify my exports to reflect all system partitions?
> > > > am i overlooking a step to give the terminals permission to mount the
> > > > shared resources?
> > >
> > > That should be OK as you list. I'm assuming the subnet is correct for
> > > you network. Any messages at the client or server end? Is clusternfs
> > > running on the server? You shouldn't have to mount all the partitions
> > > specifically, it's only done for /home for rw access.
> > >
> > > Stew Benedict
> >
> > in the control center under services it shows that clusternfs is running
> > (started at boot)
> >
> > the dmesg printed to screen on a terminal as booting ends with these
> > errors:
> >
> > SIOCADDRT: Network is unreachable
> > Mounting root filesystem 192.168.1.255:/ at /sysroot
> > If this appears to hang, check that the server of 192.168.1.255:/ is able
> > to reverse map my IP address 192.168.1.12 to obtain my hostname
> > client_192_168_1_12
> > mount: nfsmount filed: Bad file number
> > nfs: mount program didn't pass remote address!
> > mount: mounting 192.168.1.255:/ on sysroot failed: Invalid argument
> > sucessfully obtained IP address via wired link [eth0]
> > FATAL ERROR: failed to mount root filesystem
> > ~reboot~
> >
> > so it sounds like the terminal is not getting told whear to acess its
> > /sysroot on the server, the ip address of the server, and is not being
> > given permission to mount it.
> >
> > So where do I go to begin to make this work?
>
> Your server is at 192.168.1.255?
>
> Stew Benedict
yes is there anything wrong with this ip (192.168.1.255)?
