similar to: PXELinux Kernel NFS Root Errors

Hi, Thanks for your reply Josef. > In netstat -p |grep rpc I get: > dgram 56732 rpc.nfsd > dgram 55905 rpc.mountd > While client looks for socket 100003/2 or 100005/1, mine rpc.mountd is on socket 55905. Maybe it is a reason for an error 22. >The port numbers are RPC numbers, not sockets. Try 'rpcinfo -p' for these. rpcinfo -p 100005 mountd 100003 nfs So this looks

Hello all, Though the question is NFS-related, it is in conjunction with the PXE booting. Issue/Scenario: - PXE/DHCP/NFS and tFTP server running CentOS51 and is configured per PXE/Syslinux and RHEL diskless workstation documentation. 1. Attempt to test ability for client to PXE boot over the network and run Root-NFS 2. NFS export in the PXE server is: # # NFS Export Files for qatest1 host #

Hello everyone, I am using pxelinux to boot kernel from network, which goes ok. But when root must be mounted from NFS, I get the following code: Looking up port 100003/2 on 192.168.1.1 RPC: sendmsg returned error 22 portmap: RPC call returned error 22 ROOT-NFS: unable to get nfsd port number from server, using default looking up port of RPC 100005/1 on 192.168.1.1 RPC: sendmsg returned error

Hello all, I have observed a problem with a diskless PXE client I am attempting to configure. PXE/NFS/DHCP/TFTPd server is running CentOS5.1 and the Diskless workstation's root and kernel was extracted from a CentOS5.1 (custom kernel due to setting to enable Root File System support). Problem: When the diskless client boots and logs in I notice that my root user is being squashed, even if I

Hi all, I'm setting up a diskless linux system using pxelinux. I have reached the point where the kernel boots and init starts. However, I'am getting this message: INIT: version 2.78 booting can't create lock file /etc/mtab~14: Read-only file system (use -n flag to override) INIT: Entering runlevel: 2 INIT: Id "1" respawning too fast: disabled for 5 minutes INIT: no more

I have been googling and searching the archive , haven''t got anything helpful. Would appreciate any help. Got the follow error when trying to start a domain using NFS root IP-Config: Incomplete network configuration information. Looking up port of RPC 100003/2 on 10.10.24.141 <http://10.10.24.141> RPC: sendmsg returned error 101 portmap: RPC call returned error 101 Root-NFS:

Hey Folks, I am attempting to set up a router box on a diskless machine. I have PXE boot rom and am able to load a kernel (2.4) and mount the root filesystem off the server. The kernel executes and then I get the kernel panic, with the "no init found" message. I have tried various permutations of the init= parameter (/bin/init, /bin/sh, etc..), the client machine can't seem to

I am doing yet another variation on diskless clients using Red Hat 9, tftp-hpa 0.34, and pxelinux. The client's Ethernet card is Intel 1000/100/10. My clients are booting OK, except that some new traffic has been occurring. Here is what gets logged on the server: Feb 25 00:34:20 localhost dhcpd: DHCPACK on 192.168.1.101 to 00:07:e9:0f:e9:d3 via eth0 Feb 25 08:34:20 localhost

Hi everyone, I got the error: NET4: Unix domain sockets 1.0/smp for linux NET4.0 ds: no socket drivers loaded request_module[block-major-8]: root fs not mounted VFS: Cannot open root device ""or 08:03 Please append a correct "root"boot option The strange thing is that it tries to mount from harddisk. This I got somewhere else: "the kernel looks like it is trying to

I used pxelinux.0 to boot my kernel, then the kernel began to boot. However, it cannot mount nfs root. I checked the nfs root is exported OK! The last screen is as followed: serial sub-system self-test: passed. internal registers self-test: passed. ROM checksum self-test: passed (0x04f4518b). eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/dri ver/eepro100.html

I am having a problem with setting up diskless clients under CentOS 5.2. I have everything working under CentOS 4.7. This is an adaptation of the (somewhat old) Diskless Linux with PXE HOWTO by Gerd v. Egidy, originally at the URL http://www.intra2net.com/opensource/diskless-howto/, which is now defunt (there is a mirror of it at http://blog.chinaunix.net/u/2389/showart_82438.html). What I am

Hi Everyone, I have been trying to setup an NFS v4 File Server but have come across an odd issue. Mounting the /nfs4exports/share appears to be successful and the information displayed about partition size and free space seem correct but if I try to do anything inside the mounted directory the client will just hang. Does anyone have any idea what I am missing?? I have try disabling all

Hi I have trouble with disklessclient with CentOS6.5 but 6.2. I have been using disklessclient from CentOS6.2 well. Both server and clients work with CentOS6.2. Recently I set up PXE boot server with CentOS6.5 and has trouble. I built vmlinuz and initrd.image in the same method I did for CentOS6.2 [root at pxe ~]# yum -y groupinstall "Base" "Server Platform"

Hi, I'm trying to configure PXE syslinux to boot a diskless client but the client can't find the PXE boot image. I've configured the DHCP server as follows: ---------------------------- # cat /etc/dhcp3/dhcpd.conf option domain-name "cluster.net"; option domain-name-servers 10.0.0.1; default-lease-time 6048; max-lease-time 604800; log-facility local7; subnet 10.0.0.0

Hi I've suddenly lost access to some permanent cross-server shares. I think this was following the Nov 5 new kernel, rather than the Centos version upgrade. I don't see any difference to man mount.nfs I have:- [root at hs6 ~]# mount hs8:/data /sysback/hs8-data -v mount: no type was given - I'll assume nfs because of the colon mount: trying 172.26.0.8 prog 100003 vers 3 prot tcp port

After getting a reasonably configured NFS4 setup working on my Scientific Linux server, I spent a majority of my evening trying to do the same with my Centos 5 box, with fruitless results. Most attempts to mount that server returns the following message: [root at sl01 log]# mount -t nfs4 192.168.15.200:/opt/company_data /mnt mount.nfs4: Operation not permitted As nearest as I can tell, I was

Hi all, Which ports do I need to have open on an NFS client's firewall to allow it to connect to a remote NFS servers? When I disable iptables (using ConfigServerFirewall), it connects fine, but as soon as I enable it, NFS gives me this error: root at saturn:[~]$ mount master1.mydomain.co.za:/saturn /bck mount: mount to NFS server 'master1.mydomain.co.za' failed: RPC Error: Unable to

Hi, I am trying to mount the windows NT share to solaris 8.0 using Redhat 8.0 nfs. Using smbmount I mounted windows share in Linux as /home/percipia/smb. I setup Linux as NFS Server and exported /home as nfs export. [root@ldap root]# cat /etc/exports /home 192.168.1.0/255.255.255.0(ro,nohide,insecure,sync) [root@ldap root]# rpcinfo -p program vers proto port 100000 2 tcp 111

Hello, I am running an NFS server/PXE on a Cent OS 5.1 server. I have defined an NFS export with "no_root_squash" option in my /etc/exports file: # # NFS Export Files # /export/images *(rw,sync,no_root_squash) ... A client PXE boots as a diskless station to the above server into a root-NFS directory underneath the above /export/images export. When the client boots;

Hey everyone -- Is there a way to refer to the server with the tftpboot images so that when a client is booting diskless, it can mount an nfs directory to that tftp server? That is to say that I have a tftp server on 192.168.0.244. The usr directory is set to be shared amoung the diskless clients via nfs. In the root image, I have /etc/fstab set to something like: blah blah