07-03-2012
Booting problem on Sun 3500
Booting problem on Sun 3500
Hi,
I have a Sun 3500 server on which i installed solaris 5.2 installed . i dont know why from the time i have built this server whenever i try to boot it, the server doesnot come back smooth.i got a message Sync file system than restart
some times showing ok promptalso get one message "instence access exception"
Have i got to do any changes in any files for it to reboot smoothly?
Thanks in advance.
Najeer
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I was trying to test run a /bin/bash script i had just written when my monitor suddenly went blank.I had to shut down the machine from the systems main power. I was unable to boot afterwards and soo i went for the interactive boot process by typing boot -a.
I succeded in the first stage of the... (1 Reply)
Discussion started by: lealyz
1 Replies
2. UNIX for Dummies Questions & Answers
I have a Sun box that I am trying to get started up, but everytime it will crap out because it is bound to an NIS domain that no longer exists. The Master for that domain was put out of commission. It was suggested to me that I could boot off of the Installation cd for the OS (Solaris 8) and... (4 Replies)
Discussion started by: Jody
4 Replies
3. Solaris
Hi,
I have a Sun 3500 server on which i installed solaris 8 and have also installed veritas 4.0 on it. i dont know why from the time i have built this server whenever i try to boot it, the server doesnot come back smooth.... i have got to connect a laptop to the serial port of the server and... (3 Replies)
Discussion started by: ishila
3 Replies
4. Solaris
Hello
I have Sun Ultra 10 with Solaris 7 installed on it.
Sometimes back
after that the machine use to get hang .Even after
rebooting the system was not booting.
I have manually switch on /off many times from the
power board itself .Once in a while it
use to boot .After... (12 Replies)
Discussion started by: turki_00
12 Replies
5. Solaris
Hi,
I have a sun ultra enterprise 450 server. This server powers on and a white screen appears with the system and network information.
But it doesnot boot up completely. Booting operation wil be halted by a warning:
\usr\sbin\fsck not found. Most likely the mount of \usr failed or the... (5 Replies)
Discussion started by: tgashwini
5 Replies
6. Solaris
Dear All,
I am facing a specfic problem with my New SunFire T2000.Recently we bought new sunfire T2000 sparc server.When i am trying to install solaris 10 through cdrom , I get error messgae
Error:Last Trap: Instaruction Access Exception
{0} ok boot cdrom
Boot device:... (6 Replies)
Discussion started by: solaris8in
6 Replies
7. Solaris
Hi,
I have two Sun Fire V490 with Solaris 10 5/08, FC switch and two Sun StorageTek 3500 FC arrays. Each array is connected to switch and to one server at a time. In the last week I installed Solaris 10 5/08 on both servers and set up Sun Cluster, version 3.2. At wednesday all was fine - all... (7 Replies)
Discussion started by: Sapfeer
7 Replies
8. Solaris
Got the console cable all connected up and got tot he ok prompt.
Typed in boot cdrom and got the following:
ok boot cdrom
Boot device: /pci@8,700000/scsi@6/disk@6,0:f File and args:
ERROR: /packages/deblocker: Last Trap: Corrected ECC Error
Can't read disk label.
Can't open disk... (4 Replies)
Discussion started by: bbbngowc
4 Replies
9. UNIX for Dummies Questions & Answers
Hello Everyone,
First: English is not my native language, sorry.
I was given today on the work of a SUN Enterprse 220r, then I was going to install Debian-sparc, but the server remains in the boot process in a loop of the Fork interpreter depends (begin to load with power-up) starts the... (4 Replies)
Discussion started by: snap
4 Replies
10. Solaris
Hello
I have an old sun fire v250 server that I am trying to revive.
I am trying to boot it from cdrom to install the OS (Solaris 10). The original data in the disk is corrupt and I am trying to do a new clean install. However I encounter the following errors.
Does it look like the disk itself... (1 Reply)
Discussion started by: br1an
1 Replies
nfs(7) Miscellaneous Information Manual nfs(7)
NAME
nfs, NFS - network file system
DESCRIPTION
The Network File System (NFS) allows a client node to perform transparent file access over the network. By using NFS, a client node oper-
ates on files residing on a variety of servers and server architectures, and across a variety of operating systems. File access calls on
the client (such as read requests) are converted to NFS protocol requests and sent to the server system over the network. The server
receives the request, performs the actual file system operation, and sends a response back to the client.
NFS operates in a stateless manner using remote procedure calls (RPC) built on top of an external data representation (XDR) protocol. The
RPC protocol enables version and authentication parameters to be exchanged for security over the network.
A server grants access to a specific file system to clients by adding an entry for that file system to the server's file.
A client gains access to that file system using the command to request a file handle for the file system (see mount(1M)). (A file handle
is the means by which NFS identifies remote files.) Once a client mounts the file system, the server issues a file handle to the client
for each file (or directory) the client accesses. If the file is removed on the server side, the file handle becomes stale (dissociated
with a known file), and the server returns an error with set to
A server can also be a client with respect to file systems it has mounted over the network; however, its clients cannot directly access
those file systems. If a client attempts to mount a file system for which the server is an NFS client, the server returns with set to The
client must mount the file system directly from the server on which the file system resides.
The user ID and group ID mappings must be the same between client and server. However, the server maps UID 0 (the superuser) to UID -2
before performing access checks for a client. This process prevents gaining superuser privileges on remote file systems.
RETURN VALUE
Generally, physical disk I/O errors detected at the server are returned to the client for action. If the server is down or inaccessible,
the client receives the message:
where is the hostname of the NFS server. The client continues resending the request until it receives an acknowledgement from the server.
Therefore, the server can crash or power down, and come back up without any special action required by the client. The client process
requesting the I/O will block, but remains sensitive to signals (unless mounted with the option) until the server recovers. However, if
mounted with the option, the client process returns an error instead of waiting indefinitely.
AUTHOR
was developed by Sun Microsystems, Inc.
SEE ALSO
exportfs(1M), share(1M), mount(1M), mount_nfs(1M), nfsd(1M), mount(2), fstab(4), dfstab(4).
nfs(7)