|
Tech Support >> FAQ-Three
for SPARC Solaris
- Solaris OS Installation and Upgrade
- CD-ROM, DVD, & FD Driver
Solaris OS Installation and Upgrade
Solaris
OS installation/Upgrade information sources
Cautions: Before doing new OS Installation /Upgrade, please read and
check the related document carefully and backup your valuable data first.
The latest updated Solaris OS information are always online on: http://docs.sun.com
, Answerbook2..., You can also order the document CD, visit the Sun
Documentation Center on Fatbrain.com at http://www1.fatbrain.com/documentation/sun.
I.e.Related Information about Solaris 8.
Solaris 8 (SPARC Platform Edition) Release Notes and Solaris 8 Installation
Supplement.
Describes any bugs, known problems, software being discontinued, and
patches related to the Solaris 8 release.
Solaris 8 Sun Hardware Platform Guide
Contains supported hardware information.
Solaris 8 Advanced Installation Guide
Describes how to install the Solaris operating environment on networked
systems and how to use the Solaris 8 Interactive Installation Program,
Solaris JumpStart, and Solaris custom JumpStart to set up, automate,
customize, and perform the installation of Solaris on any number of systems
in a large enterprise network environment.
Solaris Transition Guide (The most important note for OS upgrade)
Describes transition issues including backing up Solaris 1.x (SunOS 4.x)
files before installing Solaris 8 software, and restoring files after
Solaris 8 software is installed.
SUN Solaris 8 Upgrade FAQ
http://docs.sun.com/ab2/coll.214.7/SPARCINFOLIB/@Ab2PageView/2270?Ab2Lang=C&Ab2Enc=iso-8859-1
Back
to Top 
Worksheet for Installation
There is very useful Worksheet for Installation of Solaris OS at http://www.sun.com/bigadmin/content/misc/installworksheet.html
for new installation, update, or sys-unconfig.
Some important files for Solaris system setup.
These file are most important while you change system setups.
/etc/hostname.hme0 # host IP for the first NIC
/etc/hostname.hme1 # for the second NIC host IP
/etc/hosts # for the hosts naming
/etc/defaultdomain # default domain name of network
/etc/defaultrouter # default router on your network
/etc/nsswitch.conf # network information service config file
/etc/netmasks # IP netmasks file
/etc/resolv.conf # IP resolve config. file
Back
to Top 
How can I tell my EEPROM version? is that support 64 bit OS?
Xhost% prtconf -V {Capital V}
OBP 3.7.2 1997/07/24 16:29
Xhost% prtconf -x
NOTICE: The firmware on this system does not support the 64-bit OS.
Please upgrade to at least the following version:
OBP 3.11.2 1997/12/05 10:25
Solaris OS installation/Upgrade Troubleshooting
Please refer this page for the detailed guide line for troubleshooting.
http://docs.sun.com/ab2/coll.214.7/SPARCINFOLIB/@Ab2PageView/4890?Ab2Lang=C&Ab2Enc=iso-8859-1
That chapter provides a list of specific error messages and generic problems
that you might encounter when installing the Solaris software.
Back
to Top 
How can I tell my OS is 64 bit or 32 bit? which OS version?
Xhost % uname -a
SunOS Xhost 5.8 generic sun4u sparc SUNW, Ultra-2
Xhost% isainfo -v
32-bit sparc application
Xhost% isainfo -kv
32-bit sparc kernel moules
Recommended Patch Cluster Note.
The patch cluster is intended to provide a selected set of patches for
the designated Solaris release level. This is a bundled set of patches
conveniently wrapped for one-step installation. Only install the cluster
on the appropriate Solaris system. Carefully read all important notes
and install instructions provided in the README file before installing
the cluster. A cluster grouping does not necessarily imply that additional
compatibility testing has occured since the individual patches were
released.
INSTALL INSTRUCTIONS:
1. Download the patchs or patch clusters
2. Run the install_cluster script
cd <patch directory>
./install_cluster
3. Verify the patch installation
Xhost% /usr/bin/showrev -p
For more installation messages refer to the installation logfile:
/var/sadm/install_data/<cluster name>_log
4. ) The system should be rebooted for all patches to take effect.
CD-ROM, DVD, & FD Driver
Frequently used commends: % eject cdrom0 {recommend: always using eject or file manager to eject
CD-ROM}
% fuser -u /cdrom/cdrom0 {identify processes using the floppy0}
% /etc/init.d/volmgt stop {stopping the volmgt}
% ps -ael |grep vold {checking vold status}
% mount -F hsfs -o ro /dev/sr0 /cdrom {manually mount CD-ROM}
% volcheck -v {asking Volume Management to check all floppy media}
% fdformat -v {format floppy diskette}
% fuser -u /floppy/floppy0 {identify processes using the floppy0}
% eject floppy0
% newfs -v /vol/dev/aliases/floppy0
% volrmmount /floppy/floppy0
Error Message: no media was found
If vold, Volume Management, did not detect a CD in your CD-ROM driver
then
Actions:
1. Make sure a CD is inserted properly and you are apporch the correct.
2. If unsuccessful, check the CD; it could be damaged, dusty.. or different
format.
3. If still without any luck, try to unmount then mount the CD manually.
Back
to Top 
How to Prepare a System for a New CD-ROM Drive?
Preparing the system with auto-configuration method in which the kernel
will be rebuild or loaded with new add-on new device.
Actions:
Method 1:
# su root { Become super user}
# touch /reconfigure {Create a file called /reconfigure}
# init 6 { Reboot the system.}
Power off system to add new CD-ROM then reboot system
Method 2:
1. Shutdown the system
2. under ok prompt
ok boot -r
"Device busy" message
Cause
An attempt was made to unmount a device containing an active device (such
as an open file, a directory, a mount point, or a running process).
Actions for CD-ROM
1. Change directories from /cdrom/cdrom0/.. to other hierarchy directories.
2. Quit any programs using the CD-ROM.
3. % fuser -u -k /cdrom/cdrom0 {check & kill the processes using
cdrom0}
4. Try to unmount again.
Actions for floppy disk
1. Change directories /floppy/floppy0/.. to other hierarchy directories.
2. Quit any programs using this floppy.
3. % fuser -u -k /floppy/floppy0 {check & kill the processes using
floppy0}
4. Try to unmount again.
"I/O error" message
Cause
Some physical Input/Output error or media error has occurred.
Actions
1. Make sure a CD is inserted into the drive correctly.
2. Bad media could be at fault or incorrect format.
3. Unmount & remount the floppy disk manually.
Actions for FD
1. Make sure a diskette is inserted into the drive correctly.
2. Bad media/diskette could be at fault. fdformat the diskette or replace
it.
3. Unmount & remount the floppy disk manually.
Back
to Top 
Why can't I access CDs or floppies?
Floppy and CD-ROM are control by "vold", a volume daemon automatically
mounting removable media.
Actions:
1. if using File manager, check the "set filter options" on
View menu bar.
2. if unsuccessful, checking "vold" is running or not
% ps -ael |grep vold
if vold is inactive, start is by "/etc/init.d/volmgt start"
if vold is active, stop it then restart it again.
3. If unsuccessful on action 2, stop the "vold", mount the
cdrom0 manually.
The vold is running and file manager is work fine.
Why can't I see the contents of CDs or floppies? Floppy and CD-ROM are control by "vold",
this daemon automatically mounting removable media while system boot
up.
Actions:
0. Check the CD media first to make sure is readable HSFS format.
1. if using File manager, check the "set filter options" on
View menu bar.
2. checking "vold" is running by " % ps -ael |grep vold"
if vold is running, stop it then restart it again. by
$ /etc/init.d/volmgt stop
$ /etc/init.d/volmgt start
3. If unsuccessful on action 2, stop the "vold", mount the
cdrom0 manually.
$ mount -F hsfs -o ro /dev/sr0 /cdrom
Back
to Top 
What to do if my /vol directory is corrupt?
Floppy and CD-ROM are control by "vold", this daemon automatically
mounting removable media while system boot up. If dev, dsk, rdsk, rmt
are not in the "/vol" directory, system reboot is required
to rebuild the vol directory.
Error message: SCSI transport failed: reason 'reset'
Cause
The system sent data over the SCSI bus, but the data never reached its
destination because of a SCSI bus reset or time out. The most common
cause of this condition is conflicting SCSI targets.
If you run 440 MHz CPU on system with Solaris 2.6, please check the
special note below. The combination of new CPU and 2.6 Solaris will cause
some timing issues on SCSI devices i.e. hard driver, CD-ROM.
Action
1. Please verify that all cables measure no longer than six meters, all
SCSI connections are properly terminated and connected.
2. Verify the SCSI ID to make sure there is no conflict: hard driver
start from ID # 0,#1,2. CD-ROM default ID #6, tape default ID #4
3. Verify the SCSI ID & match all SCSI devices under ok boot prompt
using "probe-scsi-all" command
4. If power surges cause the problem, acquire a surge suppressor or an
UPS.
** Note: If you run 440 MHz CPU on new installed system with Solaris
2.6, please follow the instruction below and please install patch #106125,
#105181, 105604 on Solaris 2.6 version 3/98, install patch #105181 on
Solaris 2.6 version 5/98. You can find these or the latest version patch
at sunsolve.sun.com patch finder section.
Actions:
1. Get the system to the ok prompt by stop+a or control+break on PS/2
keyboard
2. key in these commands under ok prompt
ok setenv auto-boot? false
ok reset
ok also hidden
ok d# 404 at-speed
ok .speed { the speed should be 404 or lower MHz}
3. Install the OS 2.6. then the 2.6 patch files.
4. Verify your system speed under ok prompt
ok .speed { now it should display correct speed of CPU}
ok setenv auto-boot? true { set boot option to default }
5. Cycle power on the system to bring the CPU up to full speed
Back
to Top 
How do I claim a NFS share CD-ROM to other system?
1. login or su as super user.
2. Make sure the NFS daemon is running by
# ps -aef | grep nfsd
3.Eject cdrom0; Add the following a line to /etc/rmmount.conf:
share cdrom* -o ro
4. Insert a CD in driver; after LED light off verify it by using "share" command.
How can I accessing the shared CD-ROM on Other Systems
Actions:
1. Make a mount point for remote CD-ROM
$ mkdir mount-directory
2. Identify the remote CD-ROM
$ showmount -e remote-system-name
/cdrom/cdrom (everyone)
3. su or login as superuser and mount the remote CD-ROM
$ mount -F nfs -o ro remote-system-name:/cdrom/cdrom mount-directory
$ exit
4. Verify that CD-ROM is accessible
$ ls /mount-directory
Back
to Top 
How to Configure a System to Play Musical CDs
You can play musical CDs from a Solaris CD-ROM. You can download the
Workman, www.midwinter.com/workman, which is public domain software or
other similar program i.e. Xmcd or cda. Also, you must attach external
speakers or headphones to the CD-ROM drive earphone jack; speakers attached
to the system hardware will not work.
Once you configure your system, you can play a musical CD simply by
inserting it into the CD-ROM drive. The
Workman control panel is automatically displayed on your desktop.
1. Login or su as superuser
2.Add the following line under #Actions of /etc/rmmount.conf.
action cdrom action_workman.so path/workman workman-options
3. Now you can play and enjoy your favorite music
Booting a System from CD-ROM for Recovery Purposes
Here is how to repair an important system file ( /etc/passwd, change
root shell..) by booting from CD-ROM
ok boot cdrom -s
# mount /dev/dsk/c0t6d0s0 /tmp_mount
# cd /tmp_mount/etc
# TERM=sun
# export TERM
# vi passwd
(Remove invalid entry or correct the mistake)
# cd /
# umount /tmp_mount
# init 6
Back
to Top 
How to place a UFS File System on a Diskette?
Actions:
% volcheck -v
% /usr/sbin/newfs -v /vol/dev/aliases/floppy0
% volrmmount -i floppy0
% ls /floppy/floppy0
Back
to Top 
|