[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

NFS Trouble using custom install CD w/ linux-2.4.27-1



Hello all,

I've reached the end of my rope with this and I'm left scratching my head.
I'm hoping someone out there has more of a clue than I do.

I'm building a set of custom installation CDs for our network.  The client
boots from a ramdisk image on the CD, loads modules, set up networking, and
then mounts an install server with scripts and programs to finish the job.

I have two test machines to use as installation clients.  One test machine, a
Sun Ultra-10, has no problems booting and mounting the installation server.  A
second machine, a PC, cannot mount the server at all.  Both clients are using
the exact same version of everything, the only difference being that one uses
packages compiled for an i386 and the other uses packages compiled for the
Sparc64 architecture.

Here's my setup:

1) The installation server:
   - A PC running Debian Sarge with nfs-kernel-server, last updated five days
     ago.
   - A directory: /export/install/nfs/static containing stuff to be mounted by
     the clients.
   - An entry in /etc/hosts.allow for each client:

     portmap lockd mountd rquotad statd : <client1's name> : SPAWN (/bin/echo "CONNECTION LOG\: %d[%p]\:%n/%a" | /usr/bin/logger -pdaemon.notice) : ALLOW
     portmap lockd mountd rquotad statd : <client2's name> : SPAWN (/bin/echo "CONNECTION LOG\: %d[%p]\:%n/%a" | /usr/bin/logger -pdaemon.notice) : ALLOW

   - An entry in /etc/exports:

     /export/install/nfs/static *(async,ro)

     (For some reason using @all_ng does not work, even though the command
     "ypmatch <client> hosts" does work.  That's another mystery to me.)

2) The clients:
   - Using kernel-image-2.4.27-1 debian installer udeb package
   - Using *-modules-2.4.27-1 debian installer udeb packages:
			cdrom-core-modules-2.4.27-1
			cdrom-modules-2.4.27-1
			ext3-modules-2.4.27-1
			fat-modules-2.4.27-1
			fb-modules-2.4.27-1
			firewire-core-modules-2.4.27-1
			firmware-modules-2.4.27-1
			floppy-modules-2.4.27-1
			ide-core-modules-2.4.27-1
			ide-modules-2.4.27-1
			input-modules-2.4.27-1
			ipv6-modules-2.4.27-1
			irda-modules-2.4.27-1
			isa-pnp-modules-2.4.27-1
			jfs-modules-2.4.27-1
			loop-modules-2.4.27-1
			md-modules-2.4.27-1
			nic-extra-modules-2.4.27-1
			nic-modules-2.4.27-1
			nic-pcmcia-modules-2.4.27-1
			nic-shared-modules-2.4.27-1
			nic-usb-modules-2.4.27-1
			ntfs-modules-2.4.27-1
			parport-modules-2.4.27-1
			pcmcia-modules-2.4.27-1
			pcmcia-storage-modules-2.4.27-1
			plip-modules-2.4.27-1
			ppp-modules-2.4.27-1
			reiserfs-modules-2.4.27-1
			sata-modules-2.4.27-1
			scsi-common-modules-2.4.27-1
			scsi-core-modules-2.4.27-1
			scsi-modules-2.4.27-1
			serial-modules-2.4.27-1
			socket-modules-2.4.27-1
			ufs-modules-2.4.27-1
			usb-modules-2.4.27-1
			usb-storage-modules-2.4.27-1
			xfs-modules-2.4.27-1
   - Using dash-udeb_0.5.1-3 debian installer udeb package
   - Using busybox-0.60.5-2.2 debian installer udeb package
   - Using modutils-full_2.4.26-1.1 debian installer udeb package
   - Each client has a directory named /mnt/nfs on which to mount the server
     directory.

Symptoms:
- Each client correctly boots, loads modules, and set up ethernet.
- Each client can ping the server's IP address.
- Mounting the server using the command:

  # mount -t nfs -o ro,nolock <server's IP>:/export/install/nfs/static /mnt/nfs

  On the Ultra-10 this command works without a hitch, and the following lines
  are seen in the log file on the server:

    Jan 10 06:56:11 <Server' name> logger: CONNECTION LOG: portmap[1447]:unknown/<Sparc client's IP>
    Jan 10 06:56:11 <Server' name> logger: CONNECTION LOG: mountd[16637]:unknown/<Sparc client's IP>
    Jan 10 06:56:11 <Server' name> rpc.mountd: MNT3(/export/install/nfs/static) called
    Jan 10 06:56:11 <Server' name> rpc.mountd: authenticated mount request from <Sparc client's name>:936 for /export/install/nfs/static (/export/install/nfs/static)
    Jan 10 06:56:11 <Server' name> logger: CONNECTION LOG: portmap[1447]:unknown/<Sparc client's IP>

  On the PC this command results in the error message:

    mount: Mounting <server's IP>:/export/install/nfs/static on /mnt/nfs failed: No such device

  And the following lines are seen in the log file on the server:

    Jan 10 06:52:19 <Server' name> logger: CONNECTION LOG: portmap[1447]:unknown/<PC client's IP>
    Jan 10 06:52:19 <Server' name> logger: CONNECTION LOG: mountd[16637]:unknown/<PC client's IP>
    Jan 10 06:52:19 <Server' name> rpc.mountd: MNT3(/export/install/nfs/static) called
    Jan 10 06:52:19 <Server' name> rpc.mountd: authenticated mount request from <PC client's name>:649 for /export/install/nfs/static (/export/install/nfs/static)
    Jan 10 06:52:19 <Server' name> logger: CONNECTION LOG: portmap[1447]:unknown/<PC client's IP>

  The server reports the same thing for the PC as for the Sparc, but the PC
  gives an error message.



Anyone have any ideas?

Thanks in advance,

Michael Peek



Reply to: