Solaris

#dd if=/dev/dsk/c2t0d0 of=/dev/null bs=1024k
#dd if=/dev/dsk/c2t1d0 of=/dev/null bs=1024k

/usr/bin/truss -eflda -p -rall -wall -vall -fall -o /tmp/truss.explorer.out

or

/usr/bin/truss -eflda -rall -wall -vall -fall -o /tmp/truss.explorer.out /upt/SUNWexplo/bin/explorer -w default

No output for the below command

df -h
more /etc/mnttab

mount the mnttab file
mount -F mntfs mnttab /etc/mnttab

Now try
df -h
more /etc/mnttab

Error Message:

# passwd root
New Password:
Re-enter new Password:
Permission denied
#

#grep passwd /etc/nsswitch.conf
passwd: files nis
#

Use the below syntax to change the password

# passwd -r files
passwd: Changing password for root
New Password:
Re-enter new Password:
passwd: password successfully changed for root
#

Clearing the unavailable disk device path and changing the boot disk path


1) old c1t0d0s* device still exist...

node# ls -lart /dev/rdsk/c*s2
lrwxrwxrwx 1 root root 47 Sep 22 2005 /dev/rdsk/c1t1d0s2 -> ../../devices/pci@1c,600000/scsi@2/sd@1,0:c,raw
lrwxrwxrwx 1 root root 47 Sep 22 2005 /dev/rdsk/c1t0d0s2 -> ../../devices/pci@1c,600000/scsi@2/sd@0,0:c,raw
lrwxrwxrwx 1 root root 46 Sep 22 2005 /dev/rdsk/c0t0d0s2 -> ../../devices/pci@1e,600000/ide@d/sd@0,0:c,raw
lrwxrwxrwx 1 root other 47 Dec 31 12:26 /dev/rdsk/c1t2d0s2 -> ../../devices/pci@1c,600000/scsi@2/sd@2,0:c,raw
node#

2) So can remove old c1t0d0s* device files using “devfsadm –Cv”. Below I’ve added the “-s” option to preview the actions...

cssv04# devfsadm -Cvs
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:a
devfsadm[2811]: verbose: removing file: /dev/dsk/c1t0d0s0
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:b
devfsadm[2811]: verbose: removing file: /dev/dsk/c1t0d0s1
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:c
devfsadm[2811]: verbose: removing file: /dev/dsk/c1t0d0s2
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:d
devfsadm[2811]: verbose: removing file: /dev/dsk/c1t0d0s3
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:e
devfsadm[2811]: verbose: removing file: /dev/dsk/c1t0d0s4
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:f
devfsadm[2811]: verbose: removing file: /dev/dsk/c1t0d0s5
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:g
devfsadm[2811]: verbose: removing file: /dev/dsk/c1t0d0s6
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:h
devfsadm[2811]: verbose: removing file: /dev/dsk/c1t0d0s7
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:a,raw
devfsadm[2811]: verbose: removing file: /dev/rdsk/c1t0d0s0
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:b,raw
devfsadm[2811]: verbose: removing file: /dev/rdsk/c1t0d0s1
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:c,raw
devfsadm[2811]: verbose: removing file: /dev/rdsk/c1t0d0s2
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:d,raw
devfsadm[2811]: verbose: removing file: /dev/rdsk/c1t0d0s3
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:e,raw
devfsadm[2811]: verbose: removing file: /dev/rdsk/c1t0d0s4
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:f,raw
devfsadm[2811]: verbose: removing file: /dev/rdsk/c1t0d0s5
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:g,raw
devfsadm[2811]: verbose: removing file: /dev/rdsk/c1t0d0s6
devfsadm[2811]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:h,raw
devfsadm[2811]: verbose: removing file: /dev/rdsk/c1t0d0s7

3)Remove old c1t0d0s* device files using “devfsadm –Cv”

node# devfsadm -Cv
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:a
devfsadm[12183]: verbose: removing file: /dev/dsk/c1t0d0s0
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:b
devfsadm[12183]: verbose: removing file: /dev/dsk/c1t0d0s1
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:c
devfsadm[12183]: verbose: removing file: /dev/dsk/c1t0d0s2
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:d
devfsadm[12183]: verbose: removing file: /dev/dsk/c1t0d0s3
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:e
devfsadm[12183]: verbose: removing file: /dev/dsk/c1t0d0s4
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:f
devfsadm[12183]: verbose: removing file: /dev/dsk/c1t0d0s5
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:g
devfsadm[12183]: verbose: removing file: /dev/dsk/c1t0d0s6
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:h
devfsadm[12183]: verbose: removing file: /dev/dsk/c1t0d0s7
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:a,raw
devfsadm[12183]: verbose: removing file: /dev/rdsk/c1t0d0s0
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:b,raw
devfsadm[12183]: verbose: removing file: /dev/rdsk/c1t0d0s1
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:c,raw
devfsadm[12183]: verbose: removing file: /dev/rdsk/c1t0d0s2
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:d,raw
devfsadm[12183]: verbose: removing file: /dev/rdsk/c1t0d0s3
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:e,raw
devfsadm[12183]: verbose: removing file: /dev/rdsk/c1t0d0s4
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:f,raw
devfsadm[12183]: verbose: removing file: /dev/rdsk/c1t0d0s5
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:g,raw
devfsadm[12183]: verbose: removing file: /dev/rdsk/c1t0d0s6
devfsadm[12183]: verbose: removing file: /devices/pci@1c,600000/scsi@2/sd@0,0:h,raw
devfsadm[12183]: verbose: removing file: /dev/rdsk/c1t0d0s7
node#

4) Check the current the deviece status

node# ls -lart /dev/rdsk/c*s2
lrwxrwxrwx 1 root root 47 Sep 22 2005 /dev/rdsk/c1t1d0s2 -> ../../devices/pci@1c,600000/scsi@2/sd@1,0:c,raw
lrwxrwxrwx 1 root root 46 Sep 22 2005 /dev/rdsk/c0t0d0s2 -> ../../devices/pci@1e,600000/ide@d/sd@0,0:c,raw
lrwxrwxrwx 1 root other 47 Dec 31 12:26 /dev/rdsk/c1t2d0s2 -> ../../devices/pci@1c,600000/scsi@2/sd@2,0:c,raw
node#

5)EEPROM is still pointing to the hardware path of c1t0d0 as the primary boot device...

node# eeprom | egrep '^(boot|nvram|devalias)'
boot-command=boot
boot-file: data not available.
boot-device=primary secondary
nvramrc=devalias primary /pci@1c,600000/scsi@2/disk@0,0:a
devalias secondary /pci@1c,600000/scsi@2/disk@1,0:a
node#

6) So reset devalias devices to primary (c1t1d0) then secondary (c1t2d0)...

node# eeprom 'nvramrc=devalias primary /pci@1c,600000/scsi@2/disk@1,0:a devalias secondary /pci@1c,600000/scsi@2/disk@2,0:a'

node# eeprom | egrep '^(boot|nvram|devalias)'
boot-command=boot
boot-file: data not available.
boot-device=primary secondary
nvramrc=devalias primary /pci@1c,600000/scsi@2/disk@1,0:a devalias secondary /pci@1c,600000/scsi@2/disk@2,0:a
node#

7) Copy the ufs boot block to the newly replaced c1t2d0 disk...

installboot /usr/platform/SUNW,Sun-Fire-V240/lib/fs/ufs/bootblk /dev/rdsk/c1t2d0s0

Clear FAULTED issue in the zpool

# zpool status
pool: pool
state: DEGRADED
status: One or more devices are faulted in response to persistent errors.
Sufficient replicas exist for the pool to continue functioning in a
degraded state.
action: Replace the faulted device, or use 'zpool clear' to mark the device
repaired.
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
pool DEGRADED 0 0 0
mirror DEGRADED 0 0 0
c1t50060E8005707700d14 FAULTED 2 151 0 too many errors
c5t50060E8005707711d14 ONLINE 0 0 0
mirror DEGRADED 0 0 0
c1t50060E8005707700d15 FAULTED 0 179 0 too many errors
c5t50060E8005707711d15 ONLINE 0 0 0
mirror DEGRADED 0 0 0
c1t50060E8005707700d16 FAULTED 0 182 0 too many errors
c5t50060E8005707711d16 ONLINE 0 0 0
mirror DEGRADED 0 0 0
c1t50060E8005707700d17 FAULTED 0 171 0 too many errors
c5t50060E8005707711d17 ONLINE 0 0 0
mirror DEGRADED 0 0 0
c1t50060E8005707700d18 REMOVED 0 0 0
c5t50060E8005707711d18 ONLINE 0 0 0
mirror DEGRADED 0 0 0
c1t50060E8005707700d19 REMOVED 0 0 0
c5t50060E8005707711d19 ONLINE 0 0 0
mirror DEGRADED 0 0 0
c1t50060E8005707700d20 REMOVED 0 0 0
c5t50060E8005707711d20 ONLINE 0 0 0

errors: No known data errors
bash-3.00#

The below command will clear the faulty error

#zpool clear


bash-3.00# zpool status
pool: pool
state: DEGRADED
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
pool DEGRADED 0 0 0
mirror ONLINE 0 0 0
c1t50060E8005707700d14 ONLINE 0 0 0
c5t50060E8005707711d14 ONLINE 0 0 0
mirror ONLINE 0 0 0
c1t50060E8005707700d15 ONLINE 0 0 0
c5t50060E8005707711d15 ONLINE 0 0 0
mirror ONLINE 0 0 0
c1t50060E8005707700d16 ONLINE 0 0 0
c5t50060E8005707711d16 ONLINE 0 0 0
mirror ONLINE 0 0 0
c1t50060E8005707700d17 ONLINE 0 0 0
c5t50060E8005707711d17 ONLINE 0 0 0
mirror DEGRADED 0 0 0
c1t50060E8005707700d18 REMOVED 0 0 0
c5t50060E8005707711d18 ONLINE 0 0 0
mirror DEGRADED 0 0 0
c1t50060E8005707700d19 REMOVED 0 0 0
c5t50060E8005707711d19 ONLINE 0 0 0
mirror DEGRADED 0 0 0
c1t50060E8005707700d20 REMOVED 0 0 0
c5t50060E8005707711d20 ONLINE 0 0 0

errors: No known data errors
bash-3.00#

Some time SAN storage disk will loss the connection and back to online but in the ZFS pool it shows REMOVED state. Clear the removed error with detaching and reattching the zpool disks

bash-3.00# zpool detach pool c1t50060E8005707700d18
bash-3.00#

bash-3.00# zpool attach pool c5t50060E8005707711d18 c1t50060E8005707700d18


bash-3.00# zpool status
pool: pool
state: ONLINE
scrub: resilver completed after 0h0m with 0 errors on Wed Sep 1 06:59:02 2010
config:

NAME STATE READ WRITE CKSUM
pool ONLINE 0 0 0
mirror ONLINE 0 0 0
c1t50060E8005707700d14 ONLINE 0 0 0
c5t50060E8005707711d14 ONLINE 0 0 0
mirror ONLINE 0 0 0
c1t50060E8005707700d15 ONLINE 0 0 0
c5t50060E8005707711d15 ONLINE 0 0 0
mirror ONLINE 0 0 0
c1t50060E8005707700d16 ONLINE 0 0 0
c5t50060E8005707711d16 ONLINE 0 0 0
mirror ONLINE 0 0 0
c1t50060E8005707700d17 ONLINE 0 0 0
c5t50060E8005707711d17 ONLINE 0 0 0
mirror ONLINE 0 0 0
c5t50060E8005707711d18 ONLINE 0 0 0
c1t50060E8005707700d18 ONLINE 0 0 0
mirror ONLINE 0 0 0
c1t50060E8005707700d19 ONLINE 0 0 0
c5t50060E8005707711d19 ONLINE 0 0 0
mirror ONLINE 0 0 0
c1t50060E8005707700d20 ONLINE 0 0 0
c5t50060E8005707711d20 ONLINE 0 0 0

errors: No known data errors
bash-3.00#

QLC error message:

Aug 9 02:00:42 test1 qlc: [ID 607548 kern.info] QEL qlc(4): ql_sdm_setup, failed, version
Aug 9 02:00:42 test1 qlc: [ID 599862 kern.info] QEL qlc(4): ql_sdm_ioctl, failed, sdm_setup
Aug 9 02:00:42 test1 qlc: [ID 771894 kern.info] QEL qlc(4): ql_ioctl,unknown command = 115
Aug 9 02:00:42 test1 qlc: [ID 875411 kern.info] QEL qlc(4): ql_ioctl,failed, rval = 25
Aug 10 02:00:45 test1 qlc: [ID 607548 kern.info] QEL qlc(4): ql_sdm_setup, failed, version
Aug 10 02:00:45 test1 qlc: [ID 599862 kern.info] QEL qlc(4): ql_sdm_ioctl, failed, sdm_setup
Aug 10 02:00:45 test1 qlc: [ID 771894 kern.info] QEL qlc(4): ql_ioctl,


Solution:

The error messages observed are the consequence of enabling the extended loggin on qld driver, see configuration file qlc.conf:

#Name: Enable extended logging
#Type: Integer, flag; Range: 0 (disable), 1 (enable); Default: 0
#Usage: This field enables logging of driver detected events occurring
# either in the driver or fibre channel bus. Events are logged
# in Solaris /var/adm/messages file.
#
#
# extended-logging=0;
extended-logging=1; <---!!!

Those messages are reported against instances 3 and 4, this are related to the following paths:

"/node@1/pci@8,700000/pci@2/SUNW,qlc@4" 0 "qlc"
"/node@1/pci@8,700000/pci@2/SUNW,qlc@5" 1 "qlc"

"/node@1/pci@9,600000/QLGC,qla@1" 4 "qlc" -->
"/node@1/pci@9,600000/QLGC,qla@2" 3 "qlc" -->

"/node@1/pci@8,600000/SUNW,qlc@2" 2 "qlc"


There are two SUN HBAs :

Opening Device: /devices/pci@8,700000/pci@2/SUNW,qlc@4/fp@0,0:devctl
Detected FCode Version: ISP2200 FC-AL Host Adapter Driver: 1.13 01/03/05

Opening Device: /devices/pci@8,700000/pci@2/SUNW,qlc@5/fp@0,0:devctl
Detected FCode Version: ISP2200 FC-AL Host Adapter Driver: 1.13 01/03/05

Opening Device: /devices/pci@8,600000/SUNW,qlc@2/fp@0,0:devctl
Detected FCode Version: ISP2200 FC-AL Host Adapter Driver: 1.14 01/11/20


1) | 'PCI Dual FC Network Adapter+' | X6727A | 375-3030
/devices/pci@8,700000/pci@2/SUNW,qlc@4/fp@0,0:devctl NOT CONNECTED qlc0
/devices/pci@8,700000/pci@2/SUNW,qlc@5/fp@0,0:devctl NOT CONNECTED qlc1



2) | 'Onboard FC-AL (ISP220x)' | N/A | N/A
/devices/pci@8,600000/SUNW,qlc@2/fp@0,0:devctl CONNECTED qlc2



And there is a third party HBA, configured under Sun qlc driver, used to access EMC array:

/devices/pci@9,600000/QLGC,qla@1/fp@0,0:devctl CONNECTED qlc4
/devices/pci@9,600000/QLGC,qla@2/fp@0,0:devctl CONNECTED qlc3

DEVICE PROPERTIES for disk: 5006048441dde6a3
Vendor: EMC
Product ID: SYMMETRIX
Revision: 5568
Serial Num: 702042C64000
Unformatted capacity: 4095.000 MBytes
Read Cache: Enabled
Minimum prefetch: 0x0
Maximum prefetch: 0xffff
Device Type: Disk device
Path(s):

/dev/rdsk/c6t5006048441DDE6A3d15s2
/devices/pci@9,600000/QLGC,qla@1/fp@0,0/ssd@w5006048441dde6a3,f:c,raw
LUN path port WWN: 5006048441dde6a3
Host controller port WWN: 210000e08b06abcb
Path status: O.K.
/dev/rdsk/c7t5006048441DDE69Cd15s2
/devices/pci@9,600000/QLGC,qla@2/fp@0,0/ssd@w5006048441dde69c,f:c,raw
LUN path port WWN: 5006048441dde69c
Host controller port WWN: 210000e08b06accb
Path status: O.K.


bash-3.00$ more luxadm_-e_port.out

Found path to 5 HBA ports

/devices/pci@8,700000/pci@2/SUNW,qlc@4/fp@0,0:devctl NOT CONNECTED
/devices/pci@8,700000/pci@2/SUNW,qlc@5/fp@0,0:devctl NOT CONNECTED
/devices/pci@8,600000/SUNW,qlc@2/fp@0,0:devctl CONNECTED
/devices/pci@9,600000/QLGC,qla@1/fp@0,0:devctl CONNECTED
/devices/pci@9,600000/QLGC,qla@2/fp@0,0:devctl CONNECTED


If you don't want to see those debugging messsages, you can edit /kernel/drv/qlc.conf and chage line extended-logging=1; to extended-logging=0; , save the file and reboot.

/usr/openwin/bin/kcms_server: Hangup in Solaris
May 10 17:10:08 test1 last message repeated 404 timesMay 10 17:10:09 test1 inetd[170]: [ID 858011 daemon.warning] /usr/openwin/bin/kcms_server: Hangup
Solution:
The Solaris kcms_server(1) daemon is part of the Kodak Color Management System (KCMS), an API and libraries to create and manage profiles that can describe and control the color performance of digital color images on desktop computers and associated peripherals. The kcms_server(1) daemon is enabled by default in the inetd.conf(4) file.
1. Disable the kcms_server(1) daemon on all systems.
a) Edit the “/etc/inetd.conf” file and comment out the following line by prepending the ‘#’ symbol as follows.
# 100221/1 tli rpc/tcp wait root /usr/openwin/bin/kcms_server kcms_server b) Instruct the inetd(1M) process to reread the newly modified “/etc/inetd.conf” file by sending it a hangup signal, SIGHUP:
$ ps -ef grep inetd $ kill -HUP 2. Remove the KCMS related packages using pkgrm(1) as the root user.
The following are the KCMS packages:
Core KCMS packages:
application SUNWkcslx KCMS Runtime Library (64-bit) application SUNWkcspf KCMS Optional Profiles application SUNWkcspg KCMS Programmers Environment application SUNWkcspx KCMS Programmers Environment (64-bit) system SUNWkcsrl KCMS Runtime Library Support system SUNWkcsrr KCMS Runtime Profiles application SUNWkcsrt KCMS Runtime Environment application SUNWkcsrx KCMS Runtime Environment (64-bit)
Translated KCMS packages:
ALE SUNWckcsr Simplified Chinese (EUC) KCMS Runtime Environment application SUNWdkcsr German KCMS Runtime Environment application SUNWekcsr Spanish KCMS Runtime Environment application SUNWfkcsr French KCMS Runtime Environment ALE SUNWhkcsr Traditional Chinese (EUC) KCMS Runtime Environment application SUNWikcsr Italian KCMS Runtime Environment application SUNWjkcsr Japanese KCMS Runtime Environment ALE SUNWkkcsr Korean (EUC) KCMS Runtime Environment application SUNWskcsr Swedish KCMS Runtime Environment
After Disabled
Jan 28 16:07:59 mtest1 inetd[971]: [ID 244026 daemon.notice] config: 100083/rpc/tcp still active and was not reconfigured.Jan 28 16:07:59 test2 inetd[971]: [ID 244026 daemon.notice] config: 100068/rpc/udp still active and was not reconfigured.

1. If 'configure' can't find ssl, change the configure command to:

   ./configure --prefix=/usr --with-ssl-dir=\ /usr/local/ssl --with-tcp-wrappers

2. Sometimes compilation of openssh bombs out with the following error messages:

   sshd.c:1660: error: storage size of req isn't known sshd.c:1663: warning: implicit declaration of function fromhost sshd.c:1660: warning: unused variable req

3. Another frequent problem is that configure bombs out with the message:

   configure: error: Your OpenSSL headers do not match your library

   The easiest solution is to go to your openssl directory and type:

   make install cd include/openssl cp * /usr/include/openssl/ cp * /usr/local/ssl/include/openssl/

   Compile openssh, using the following command line, and substitute the appropriate path after --with-ssl-dir :

   ./configure --prefix=/usr --with-tcp-wrappers \ --with-ssl-dir=/usr/local/ssl make make install

4. If it says:

   Connecting to carbon... OpenSSL version mismatch. Built against 90603f, you have 90607f Couldn't read packet: Connection reset by peer

   Get rid of your old libcrypto libraries in /usr/lib and rerun ldconfig:

   cd /usr/local/ssl/lib cp * /usr/lib/ ldconfig

   Then rebuild and reinstall openssh (make clean; make; make install), and restart sshd.
5. Sometimes ssh has the following connection problem:
   On client

   Request for subsystem 'sftp' failed on channel 0 Couldn't read packet: Connection reset by peer

   On server

   sshd[7079]: Accepted password for tjnelson from 63.127.146.196 port 32777 ssh2 sshd[7079]: subsystem request for sftp sshd[7079]: error: subsystem: cannot stat /usr/local/libexec/sftp-server: No such file or directory sshd[7079]: subsystem request for sftp failed, subsystem not found

   To solve this problem, do the following:
   Edit /etc/ssh/sshd_config and add:

   Subsystem sftp /usr/local/libexec/sftp-server Protocol 2

   Create /usr/libexec and make a link to sftp-server. For some reason sshd sometimes looks there instead of the path specified in its configuration file.

   mkdir /usr/libexec cd /usr/libexec ln -s /usr/lib/ssh/sftp-server sftp-server

   Stop and start sshd (don't restart, because the port takes a while to close).

   cd /etc/rc.d ./sshd stop ./sshd restart

6. If it says:

   checking for socklen_t equivalent... configure: error: Cannot find a type to use in place of socklen_t

   this means your computer is totally screwed, and you should take it out back and shoot it.
7. If it says:

   sshd re-exec requires execution with an absolute path

   The startup script needs to be modified to include the full path of sshd.
8. If it says:

   Permission denied (publickey,keyboard-interactive).

   This can happen after an upgrade when you change from PAM to password authentication. Edit /etc/ssh/sshd_conf and change PasswordAuthentication to yes.

Problem description: - ./explorer[76]: HOSTID: is read only

#pwd

/opt/SUNWexplo/bin

# ./explorer

./explorer[76]: HOSTID: is read only

Solution: -

# find / -name exp_main

/opt/SUNWexplo/lib/exp_main

# file /opt/SUNWexplo/lib/exp_main

/opt/SUNWexplo/lib/exp_main: executable /bin/ksh script

# grep -i hostid /opt/SUNWexplo/lib/exp_main

# Save HOSTID

HOSTID=`hostid`

export HOSTID EXP_MAIN_VERSION

EXP_SERIAL=`eval echo $"EXP_SERIAL_${HOSTID}"`

# Translate %H to hostid

EXP_SUBJECT=`echo ${EXP_SUBJECT} | sed -e "s~%H~${HOSTID}~g"`

echo "Hostid: \c" >>${EXP_TARGET}/README

hostid >>${EXP_TARGET}/README

EXP_ID="explorer.${HOSTID}.`uname -n`-`date -u +\%Y.\%m.\%d.\%H.\%M`"

eval "EXP_SERIAL_${HOSTID}"=${exp_parms[44]}

Take backup

# cp -p /opt/SUNWexplo/lib/exp_main /opt/SUNWexplo/lib/exp_main.20090609.MUR

Comment below entry to solve this issue and then re-run the explorer script.

# vi /opt/SUNWexplo/lib/exp_main

HOSTID=`hostid`

Solaris booting issues & Problems:

Check the status of the syslogd:

logger -p local0.err "syslogd is alive"

TRUSS:

truss -dDelaf -vall -p `pgrep cron`

Following are some of the booting issues, error messages their meaning and possible solutions

1) Booting in single user mode and mounting root disk.
2) Making boot device alias
3) "Timeout waiting for ARP/RARP packet"? error message.
4) "The file just loaded does not appear to be executable" error message.
5) "bootblk: can't find the boot program" error message.
6) "boot: cannot open kernel/unix" error message .
7) "Error reading ELF header"? error message .
8) "Cannot open '/etc/path_to_inst'" error message.
9) "Can't stat /dev/rdsk/c0t3d0s0" error message .

1. Booting in single user mode and mounting root hard disk.

Most important step in diagnosing the booting problems is booting the system in single user mode and examining the hard disk for possible errors & work out the corrective measure. Single user mode can be achieved by any of the following methods :-
ok> boot -s ;from root disk
ok> boot net -s ;from network

ok>boot cdrom -s ;from cdrom
Rebooting with command: cdrom -s
Configuring the /devices directory
Configuring the /dev directory
INIT: SINGLE USER MODE
#
# fsck /dev/rdsk/c0t3d0s0
# mount /dev/dsk/c0t3d0s0 /mnt

Perform the required operation on mounted disk, now accessible through /mnt ,& unmount the hard disk after you are done ;
# umount /mnt
# reboot

2. Making boot device alias

In case system can not boot from primary disk and it is needed to make another boot disk to access the data, nvalias command is used.
nvalias command makes the device alias and assigns an alternate name to a physical disk. Physical address of target disk is required which can be had by show-disk command on ok>.

ok> nvalias disk7 /iommu@f,e0000000/sbus@f,e0001000/dma@3,81000/esp@3,80000/sd2,0
The new aliased disk can be named as boot disk or can be used for booting by refering its name .
ok> setenv boot-device disk7
ok>reset
or
ok> boot disk7

3."Timeout waiting for ARP/RARP packet"?

At ok> type printenv and look for these parameters.
boot-device disk
mfg-switch? false
diag-switch? false

If you see "boot-device net” or true value for the other two parameter change it to the values above.
In case you want to boot from network make sure your client is properly configured in boot server and network connections & configuration are proper.

4. The file just loaded does not appear to be executable.

Boot block on the hard disk is corrupted .Boot the system in single user mode with cdrom and reinstall boot block.

#installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t3d0s0

5. Bootblk: can't find the boot program

Boot block can not find the boot program - ufsboot in Solaris .Either ufsboot is missing or corrupted. In such cases it can be restored from the cdrom after booting from cdrom & mounting the hard disk
# cp /platform/`uname -i`/ufsboot /mnt/platform/`uname -i`

6.boot: cannot open kernel/unix

Kernel directory or unix kernel file in this directory is not found .Probably deleted during fsck or deleted by mistake .Copy it from the cdrom or restore from the backup tape.
#cp /platform/`uname -i`/kernel/unix /mnt/platform/`uname -i`/kernel

7."Error reading ELF header."?

Kernel directory or unix kernel file in this directory is corrupted. Copy it from the cdrom or restore from the backup tape.
# cp /platform/`uname -i`/kernel/unix /mnt/platform/`uname -i`/kernel

8."Cannot open '/etc/path_to_inst'

System can not find the /etc/path_to_install file .It might be missing or corrupted and needs to be rebuild.
To rebuild this file boot the system with -ar option:
ok > boot -ar
Press enter to select default values for the questions asked during booting and select yes to rebuild /etc/path_to_install
The /etc/path_to_inst on your system does not exist or is empty. Do you want to rebuild this file [n]? y
System will continue booting after rebuilding the file.

9."Can't stat /dev/rdsk/c0t3d0s0"

When booted from cdrom and done fsck the root partition comes out to be fine but on booting from root disk this error occurs. The device name for / is missing from /dev/dsk directory and to resolve the issue /dev & /devices directories has to be restored from root backup tapes.

Solaris Basics:

1) In Solaris how many disk slices a disk can have?
a) 8 b) 7 c) 6 d) 1

2) Which file is used to set the default mask in Solaris?
a)/etc/profile b) .profile c) /etc/system d) /etc/inittab

3) What are the advantages for making disk partitions?
a) Easy to maintain b) Easy for backing up
c) Limits problems to one partition only d) Space can be monitored easily.

4 )What does a + sign in /etc/hosts.equiv indicates ?
a) All hosts are allowed b) Only known hosts are allowed c) All users are allowed d) Unknown hosts are also allowed .

5 )Which command is used to mount local file system ?
a) mount -l b) mountall c) mount d) mount -r

6) Which command line option gives a run level and output headings?
a) who -b b) who -r c) who -rh d) who -rH

7) Which command is used to change the auto-boot feature in sun ultra?
a) eeprom "auto-boot?"=true b) eeprom auto-boot?=true c) eeprom autoboot? true d) eeprom auto-boot = true

8) If patch id is 123456-10 then its revision number is -
a)123 b)456 c)10 d)6-10

9) Which commands can be used to make a device alias
a) devalias ay ok prompt b) dvalias at root prompt
c) nvram at ok prompt d) drvconfig at root prompt.

10) Where in Solaris encrypted passwords are stored?
a) /etc/passwd b) /etc/shadow c)/etc/default/passswd d)/etc/initttab

11) What is required in a diskless workstation for Solaris Workstation?
a) cpu, monitor, keyboard, hard disk b) cpu, monitor, keyboard, cdrom drive
c) cpu, monitor, keyboard, Ethernet card d) cpu and Ethernet card only.

12) Which of the following points to virtual file system?
a) /dev/dsk/c0t0d0s3 b) /dev/rdsk/c0t0d0s3
c) /dev/md/dsk/c0t0d0s3 d) /dev/vx/rdsk/data/vol1

13) Which Solaris command is used to correct file system problems?
a) newfs b) fsck c) mkfs d) format

14) Which is the configuration file for the tip command?
a)/etc/tip.conf b) /etc/remote c) /etc/inittab.d d) .profile

15) When automounter daemon needs to be restarted?
a) When direct map is changes b) when indirect map is changes
c) No need to restart d) when a new user is created

16) What is the default configuration cluster in Solaris installation?
a) Developer b) Core c) End user d) Entire Distribution

17) Which utility is used to administer the port monitor?
a)sacadm b) pmadm c) ttyadm d) admintool

18) What is the command to assign a ip address to qfe network interface?
Write the command

19) 10 30 * * 4 /usr/bin/loginfo entry in crontab will execute the program
a) Every Friday at 10.30 b) Every Thursday at 10.30
c) Every Saturday 10.30 d) Every Wednesday at 10.30

20) What do you need for a fresh Solaris Installation?
a) Host Name b) IP Address c) Net mask d) Domain name

21) How can you see the prom version?
a) show version b) prom c) banner d) version

22) Which file enables you to disable root login on terminals?
a) /etc/profile b) .profile
c) /etc/default/login d) /etc/system

23) Which directory contains run level control scripts?
a) /etc/rc2.d b) /etc/init.d c) /etc/rc3.d d) /usr/bin

24) Which command show the patch installed in the system?
a) patchadd -p b) showrev -p c) showpatch d) patchlist

25) What is the advantage of having a virtual file system?
a) Large capacity volumes b) Increased File system size
c) Performance enhancement d) backup becomes easy

26) Which file is used to define default run level for init process at booting time?
a) /etc/ttyyab b) /etc/ttyadm
c) /etc/inittab d) /etc/profile

27) Which command shows kernel parameters and and driver module information?
a) sysconfig b) prtconfig
c) dmesg d) prtconf

28) A multiuser operating system is one - in which
a) Many users can work simultaneously b) Many Processes can work simultaneously
c) A large number of users can be created d) A number of user home directories can be created.

29) What is true about software packages?
a) It is group of files & directories b) They are grouped to form clusters
c) It is standard way of delivering software in Solaris d) they can be installed using pkgadd command.

30) What type of names are used for administering disk drives in Solaris environment a) Physical b) Logical c) Virtual d) disk instance

Symptoms:
The df command reports large values that do not match the filesystem size.
Filesystems are controlled by either Veritas Volume Manager or Solstice[TM] Disk Suite
root# df -h / <--- Solaris 9 or greater--- Filesystem size used avail capacity Mounted on
/dev/md/dsk/d210 5.8G 16384E 6.3G 308102866625852% /
root#df -k grep /test
/dev/vx/dsk/datadg/testvol 147501463 18446744054756400981 19097702069127613704992 76% /test

Resolution
Size of the metadevice (Disk Suite) or the volume (Volume Manager) do not agree with the filesytem size. This can happen when the user grows/shrinks the metadevice or volume, but does not adjust the size of the filesystem. This usually occurs in error To confirm that the result of the df -k command is inaccurate: 1. Determine the number of blocks in the file system: # df
2. Determine the number of blocks in the corresponding metadevice or volume:
# metastat
# vxlist -ht -v

Note: The numbers will not match exactly but they should be close.

To adjust the numbers:
1. Unmirror the device.
2. Umount the file system (if file system is /, /usr, or /var, you will need to boot the CD-ROM).
3. Perform a ufsdump on the file system to back up the data.
4. newfs the file system.
5. Restore the data.
6. Re-mirror the device.
The following workarounds have been successful as a temporary resolution to
the problem. However, they might not work in all cases.

Please try this if not solved
1.umount /etc/mnttab
mount -F mntfs mnttab /etc/mnttab
df -k
2.umount the file system:
Fsck the file system until it reports no errors
Mount the file system
df -k