LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Failed to mount the root directory via nfs (https://www.linuxquestions.org/questions/linux-networking-3/failed-to-mount-the-root-directory-via-nfs-307798/)

banner 03-30-2005 10:01 AM

Failed to mount the root directory via nfs
 
I am a newbie at Linux and I am trying to connect my thin client to my Linux server, this is the error I get at the workstation computer, I am lost with this error, I have checked nfs services and it is running, but I do Not know how to fix this error so my thin client can connect to my server, below is the error I get from my workstation. Can some please help as I need to get this to work for my boss?

This is the error i get


Running dhcp on port 67

Mounting root filesystem:192.168.1.4/opt/ltsp/i386 from:
Mount: Unknown host
Mount: nfsmount failed: Connection refused nfs warning: mount version newer than kernel
RPC: send msg returned error 22
nfs:rpc call returned error 22
nfs-get-root: getattr error=22
nfs_read-super= get root inode failed
Mount: mpounting-192.168.1.4/opt/ltsp/i386 on/mnt failed: Invalid argument

Error! Failed to mount the root directory via NFS


Possible reasons include:

1) NFS services may not be running on the server

2) Workstation IP does not map to a hostname, either in /etc/hosts or in DNS.

3) Wrong address for NFS server in the dhcp config file

4) Wrong pathname for root directory in the DHCP config file

keefaz 03-31-2005 06:27 AM

In my opinion, correct syntax should be :
192.168.1.4:/opt/ltsp/i386

(note the ':' between ip and file path)
Could you post your dhcp conf ?

banner 04-01-2005 02:04 AM

Dhcpd details
 
Thank you for your reply, as i said i am brand new in Linux less then one week old learing Linux, so be easy on me. As mentinoned before the thin client is supose to connect and log in to the Linux server, but i ran in to the problem mentioned in my last post. Here are the dhcpd details. Soory that it is so lenghty. By the way iam using a Thin client mangement system to help administer the thin clients once i log in.

Any ways here is my dhcpd information

## ALL ENTRIES BELOW WILL BE OVERWRITTEN BY SYMBIONT ##
ddns-update-style none;
default-lease-time 21600;
max-lease-time 21600;
option option-128 code 128 = string;
option option-129 code 129 = text;

shared-network WORKSTATIONS {
subnet 192.168.1.0 netmask 255.255.255.0 { # Autodetect
next-server 192.168.1.4;
option broadcast-address 192.168.1.255;
option domain-name "localhost";
option log-servers 192.168.1.4;
option root-path "192.168.1.4/opt/ltsp/i386";
option subnet-mask 255.255.255.0;

pool {
deny unknown clients;
range dynamic-bootp 192.168.1.201 192.168.1.220;
if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
filename "/lts/2.4.26-ltsp-1/pxelinux.0";
}
else {
filename "/lts/vmlinuz-2.4.26-ltsp-1";
}
}
}

}

group Default { #
use-host-decl-names on;

if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
filename "/lts/2.4.26-ltsp-1/pxelinux.0";
}
else {
filename "/lts/vmlinuz-2.4.26-ltsp-1";
}

host ws00001 { #
hardware ethernet 00:0b:6a:d4:19:4a; # Autodetect
fixed-address 192.168.1.203;
}

host ws00002 { #
hardware ethernet 00:0b:6a:d2:dd:9d; # Autodetect
fixed-address 192.168.1.201;
}

}

group Students { #
use-host-decl-names on;

if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
filename "/lts/2.4.26-ltsp-1/pxelinux.0";
}
else {
filename "/lts/vmlinuz-2.4.26-ltsp-1";
}

}


All times are GMT -5. The time now is 01:29 AM.