Writing Samples

Solaris Disk Check

See Support Policies for restrictions on time of day to run procedure.

General Procedure to check status of Solaris OS disks.

Verify that format can read all of the disk device paths: echo | /usr/sbin/format | more
For disks under Veritas control, run: /usr/sbin/vxdisk list All configured disks should show a status of "online".
Check for any DISABLED or FAILED Veritas volumes: /usr/sbin/vxprint -ht | egrep 'DISA|FAIL' If a volume is marked DISABLED: Check if the volume is in a restore operation, confirm normal configuration.
If a volume is marked FAILED: Confirm the volume is mirrored (ie:The volume has redundant plexes).
Verify that all file systems are online and accessible: df -kF ufs; df -kF vxfs I/O errors or a hung listing will indicate you have a serious issue.
For network storage disks, EMC:
- Verify Solaris Version, if Solaris 10, go to
  Knowledge Base: EMC Procedures/Solaris 10
- For Versions 5.9 and under,run: /etc/powermt display Both lun device paths should show a status of "optimal".
  I/O path totals should be equal.
  Errors should be 0. The error count is cumlative from uptime or from the last time a "restore" was run.
  If there is an error count, run:
  /etc/powermt restore Recheck. The restore will reset the error count to 0.
  If the error count resumes after the restore, see
  Knowledge Base: EMC Procedures
  for additional diagnostics and escalation procedures.
Check /var/adm/messages for more detailed error information, the following factors should be taken into consideration to determine a course of action:
- Error frequency. grep error and monitoring logs for counts and timestamps.
- Does the error frequency indicate a failing disk, even if the FAILED/DEGRADED flag has not yet been set? Is there a recent marked increase in the rate?
- Is the fault notification transient (timeout) related to system/network load or scheduled work?
- Is the error FATAL or Retryable? Was it a READ (more serious) or a WRITE error?
- Was Veritas able to correct the bad block from the mirror?
- Is it the same block in every instance, or multiple blocks?
- Run a search for the host in the [event tracking database/Remedy] Is this the first occurrence? Has a disk repair or analyze already been run?
  Has the issue already been escalated, if so, can fault monitoring be disabled til the disk is replaced?

Solaris Architecture Table

Architecture	Local Disks	Hot Swap	Power Supply	Hot Swap	Server List

E220R	scsi	Yes	PS	Yes	25
E420R	scsi	Yes	PS	Yes	100
E450	scsi	Yes	PS	Yes	20
E4000	scsi	No	PS/PPI	Yes PPI-No**	25
E4500	scsi	No	PS/PPI	Yes PPI-No**	25
F280R	fiber*	Yes	PS	Yes	250
F3800	scsi	Yes	PS	Yes	5
Netra T1	scsi	Yes	PS	No	25
Netra 1280	fiber*	No	PS	Yes	25
Ultra 2	scsi	No	PS	No	2
V120	scsi	Yes	PS	No	15
V240	scsi	Yes	PS	Yes***	15
V440	scsi	Yes	PS	Yes***	15
V480	scsi	Yes	PS	Yes***	15
V490	fiber*	Yes	PS	Yes***	15
V880	scsi	Yes	PS	Yes***	10
V890	fiber*	Yes	PS	Yes***	10

How to determine Solaris System Model and OS Version:

uname -a or
/usr/platform/sun4u/sbin/prtdiag | grep "System Configuration" or
/home/unix/bin/[script] [hostname] | grep Model or
From the http//:corporate_server_information online database Enter the [hostname] in the Find search field. Select the Hosts/Services link. The Model will be listed in the General Information block. If the host is completely down this is the method you will want to use.

* Hot swappable fiber disks require running additional luxadm commands for administration of the Network Array subsystem and individual FC-AL devices, as well as manually entered disk device commands. See Knowledge Base: Replacing Solaris Fiber Disks for replacement instructions.

** E3500/E4000/E4500/E6500 have two types of Power Supplies, PS and Peripheral Power Supplies (PPIs) that control the IO and system boards. PPIs need to be configured (or patched) to be hot swappable.

*** The V Series Sun Fires require a command line reset following a PS hot swap to stop error messages from generating.