Sponsored Content
Full Discussion: Jumpstart solaris
Operating Systems Solaris Jumpstart solaris Post 302165835 by reborg on Saturday 9th of February 2008 10:06:02 AM
Old 02-09-2008
It looks like the nfs share for the root is not available to the client. Check the dfstab, and restart the NFS daemon on the server.
 

9 More Discussions You Might Find Interesting

1. Solaris

Solaris 10 Jumpstart Problem

Hi, I build a jumpstart server with a running dhcp server. I already managed to install a x86 client via network. But my sparc clients aren't still working. When booting via network I get the following message: Timeout waiting for ARP/RARP packet I ran "snoop" on the server: client2 ->... (1 Reply)
Discussion started by: Jay_Fisi
1 Replies

2. Solaris

jumpstart Solaris 10 on Solaris 9 server

I just built a jumpstart server on a Solaris 9 sun box and have had no problems jumpstarting other sol9 boxes using the custom rules. I've also copied a Solaris 10 image onto that same solaris 9 server and have had problems loading Solaris 10. These boxes will go directly to the manual OS install... (5 Replies)
Discussion started by: salty
5 Replies

3. Solaris

Jumpstart Solaris 10 x86

I need a little help figuring out why my custom jumpstart network installation is dumping me to a manual install. I am trying to install Solaris 10 (unattended) over the wire from my jumpstart server to an HP Proliant DL380 server but I'm having difficulties with the unattended part. So, what... (2 Replies)
Discussion started by: alias.256
2 Replies

4. Solaris

Solaris 10 Jumpstart woes

Hi All I have a Solaris 10 jumpstart boot/config server set up on a subnet, and am trying to use it to build a client (the only other machine on the network). Things start out just fine, with the client booting into the Solaris Installation program, but then it just coredumps just as it's... (4 Replies)
Discussion started by: rickedwards44
4 Replies

5. Solaris

Jumpstart Issues Solaris 10

I'm trying to jumpstart my remote server. My /etc/hosts and /etc/ethers files have the correct data. Keep getting the following message at the ok prompt after running a boot net - install Link hasn't comeup yet Ran a test-net and got the following message. Link is -- down When... (7 Replies)
Discussion started by: soupbone38
7 Replies

6. Solaris

Jumpstart Solaris 10

Hello everyone, I tried to install solaris 10 using the command # boot net - install. I take the image correctly but when you start installing the Operating system installation takes a long (4 hours I have left and not advancing but not send me any errors), it can be seen from the following: ... (7 Replies)
Discussion started by: yflores
7 Replies

7. Solaris

Jumpstart Solaris 10

I have a laptop and need to build an Oracle Linux kickstart server and a Solaris Jumpstart server that can build sparc and x86 systems. Is the best way to create a dual boot from grub for Oracle Linux and Solaris x86? Can the Oracle Kickstart be used as a Jumpstart to build both Solaris 10... (2 Replies)
Discussion started by: Gian
2 Replies

8. Solaris

Solaris 10 JumpStart Server

Hello, Can anyone share a good online article/tutorial on how to properly set up JumpStart server for Solaris 10? Thanks, Regards. (3 Replies)
Discussion started by: NewSolarisSquad
3 Replies

9. Solaris

Solaris 10 Jumpstart Error

Hey All, I'm trying to jump start a new Sun Server from an existing jump start server, but this last machine is giving me driver errors :s It doesn't make sense as we've built a few of these exact same servers just recently, but this last one displays: "No driver (or driver binding)... (2 Replies)
Discussion started by: UnxAdm1101
2 Replies
nfsd(1M)																  nfsd(1M)

NAME
nfsd - NFS daemon SYNOPSIS
/usr/lib/nfs/nfsd [-a] [-c #_conn] [-l listen_backlog] [-p protocol] [-t device] [nservers] nfsd is the daemon that handles client file system requests. Only users with {PRIV_SYS_NFS} and sufficient privileges to write to /var/run can run this daemon. The nfsd daemon is automatically invoked using share(1M) with the -a option. By default, nfsd starts over the TCP and UDP transports for versions 2 and 3. By default, it starts over the TCP for version 4. You can change this with the -p option. A previously invoked nfsd daemon started with or without options must be stopped before invoking another nfsd command. Administrators wanting to change startup parameters for nfsd should, as root, make changes in the /etc/default/nfs file. See nfs(4). The following options are supported: -a Start a NFS daemon over all available connectionless and connection-oriented transports, including UDP and TCP. Equivalent of setting the NFSD_PROTOCOL parameter to ALL in the nfs file. -c #_conn This sets the maximum number of connections allowed to the NFS server over connection-oriented transports. By default, the number of connections is unlimited. Equivalent of the NFSD_MAX_CONNECTIONS parameter in the nfs file. -l Set connection queue length for the NFS TCP over a connection-oriented transport. The default value is 32 entries. Equiva- lent of the NFSD_LISTEN_BACKLOG parameter in the nfs file. -p protocol Start a NFS daemon over the specified protocol. Equivalent of the NFSD_PROTOCOL parameter in the nfs file. -t device Start a NFS daemon for the transport specified by the given device. Equivalent of the NFSD_DEVICE parameter in the nfs file. The following operands are supported: nservers This sets the maximum number of concurrent NFS requests that the server can handle. This concurrency is achieved by up to nservers threads created as needed in the kernel. nservers should be based on the load expected on this server. 16 is the usual number of nservers. If nservers is not specified, the maximum number of concurrent NFS requests will default to 1. Equivalent of the NFSD_SERVERS parameter in the nfs file. USAGE
If the NFS_PORTMON variable is set in /etc/system, then clients are required to use privileged ports (ports < IPPORT_RESERVED) to get NFS services. This variable is equal to zero by default. This variable has been moved from the "nfs" module to the "nfssrv" module. To set the variable, edit the /etc/system file and add this entry: set nfssrv:nfs_portmon = 1 0 Daemon started successfully. 1 Daemon failed to start. .nfsXXX Client machine pointer to an open-but-unlinked file. /etc/default/nfs Contains startup parameters for nfsd. /etc/system System configuration information file. /var/nfs/v4_state Directories used by the server to manage client state information. These directories should not be removed. /var/nfs/v4_oldstate See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnfssu | +-----------------------------+-----------------------------+ ps(1), svcs(1), mountd(1M), share(1M), svcadm(1M), nfs(4), sharetab(4), system(4), attributes(5), smf(5) Manually starting and restarting nfsd is not recommended. If it is necessary to do so, use svcadm to enable or disable the nfs service (svc:/network/nfs/server). If it is disabled, it will be enabled by share_nfs(1M), unless its application/auto_enable property is set to false. See the , and svcadm(1M) for more information. The nfsd service is managed by the service management facility, smf(5), under the service identifier: svc:/network/nfs/server Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. If nfsd is killed with SIGTERM, it will not be restarted by the service management facility. Instead, nfsd can be restarted by other sig- nals, such as SIGINT. 27 Apr 2005 nfsd(1M)
All times are GMT -4. The time now is 02:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy