ptx/Online Diagnostics Version 1.4.1 Release Notes

These release notes contain information on Version 1.4.1 of the ptxTM /Online Diagnostics software. The information does not appear elsewhere in the documentation set. Read the release notes before installing and running the online diagnostics. The following topics are covered in these notes:


1.1 Product Compatibility

Version 1.4.1 of the Online Diagnostics software is compatible with all systems running DYNIX/ptx® V1.4 or later.

Your system must be running DYNIX/ptx V1.4 or later to use the full functionality of the Online Diagnostics software. The Online Diagnostics software will operate on DYNIX/ptx versions prior to V1.4, but the SCSI commands options will not work.

The Online Diagnostics software is not compatible with WinServer® systems, SCED-based systems, or systems that contain Balance® processor boards.


1.2 Changes Since the Previous Release

Version 1.4.1 includes all the functionality of Version 1.4, plus the following:


1.3 Software Installation

You can install the Online Diagnostics software onto the boot disk by using the ptx/ADMIN® menu system. Refer to the ptx/INSTALL Software Installation Guide and the DYNIX/ptx and Layered Products Software Installation Release Notes for software installation information and procedures.


ATTENTION

Refer to the NUMA-Q Systems Online Diagnostics Guide for important information about installing a special diagnostic partition on disks that will be tested with the Online Diagnostic software.



1.4 Related Documentation

The NUMA-Q Systems Online Diagnostics Guide explains how to start and use the software.


1.5 Call Customer Support for Assistance

If your shipment is incomplete or you encounter problems while installing the Online Diagnostics software, contact Customer Support.


1.6 Problem Report Summary

This section describes known problems in Version 1.4.1 of the ptx/Online Diagnostics software. Most problem reports include a way to work around the problem.


ATTENTION

Unless otherwise stated, fixes for the problems listed here will be considered for inclusion in a future release of the product.



1.6.1 Some zd Disks Return " Sector Not Found" Errors

While running disks on 792-MB or 1550-MB SMD-E disks (zd disks), you may see " Sector Not Found" errors at the beginning of the diagnostic tracks. The failing locations will be reported as:

     (743, 2, 80)  for 792-MB disks

     (1914, 2, 80) for 1550-MB disks

Workaround. These errors do not affect the test. You can ignore the errors, or you can add the locations to the bad block list for the appropriate disk.


1.6.2 Read Sweep Tests Can Degrade Performance on Some Systems

Read sweep disk tests can require up to 2-MB of memory for each disk tested (depending on the size of the disk). Running several concurrent read sweep tests on systems with insufficient free memory can seriously degrade system performance.

Workaround. You can run other online disk tests that do not require as much free memory as read sweep tests. You can also limit the number of concurrent read sweep tests.


1.6.3 Testing xt Tape Drives May Require Special Kernel Configuration

The driver for the Xylogics® 472 MULTIBUSTM Tape Drive (xt) does not support data blocks larger than 32-KB without special kernel configuration.

Workaround. When running online tape tests on xt devices, do not use data blocks over 32-KB unless you are sure the DYNIX/ptx kernel has been configured to support them. Refer to the DYNIX/ptx System Configuration and Performance Guide for information about reconfiguring the kernel.


1.6.4 Nuisance Errors Can Occur During Owl Token Ring Board Testing

Nuisance errors can occur after several hours of running the Owl Token Ring Board Test. The error is caused by a timing issue between the owl driver and the Owl Token Ring Board Test. When this nuisance error occurs, you will see one of the following messages on the console:

   owl_test: -<E>-: <owl0>: Error #210:
   "Buffer ram address test ioctl failed"

   owl_test: -<E>-: <owl0>: Error #210:
   "Buffer ram data test ioctl failed"

   owl_test: -<E>-: <owl0>: Error #210:
   "Vme data transfer test ioctl failed"

These messages do not indicate a problem on the Token Ring board. If a valid error occurs, you will see the following message on the console:

   "WARNING: LAN owlx owl_cintr:
   Diagnostics Failed  Status=0x4001"

Workaround. If you do not see the WARNING message on the console, these errors do not affect the test. You can ignore the errors.