|A P P E N D I X B|
Frequently Asked Questions
As of SunVTS 5.1, the SunVTS software is compatible with multiple Solaris operating environment software releases for backwards compatibility. The following table lists the Solaris operating environment release to SunVTS version correspondence.
Yes. See Installing and Removing SunVTS.
Will installing SunVTS negatively affect any of the existing files on my system?
If I reinstall SunVTS, will I have access to the options files that were created before the reinstall?
No. You must install SunVTS as described in Installing and Removing SunVTS on each system for which you plan to run SunVTS.
Can I run SunVTS from maintenance-mode (single-user level)?
I know that SunVTS runs on my 32-bit Solaris Operating Environment systems. Will it run on my Solaris 64-bit Operating Environment systems?
Yes. The sunvts command detects which operating environment is running and starts the appropriate SunVTS kernel. You must have the 64-bit SunVTS package installed (SUNWvtsx) to run 64-bit tests. See SunVTS Packages.
No, SunVTS tests are not data destructive. However, when the disktest is run with the rawtest write/read mode enabled, it does write data on the selected partition. The test, however, backs up the original data first, and puts it back when the write/read/compare operation is complete. By default, disktest runs in read-only mode. In addition, a few intervention mode tests, such as tapetest and disktest (for the floppy drive) require that you load scratch media that can be written on. Specific test details are explained in the SunVTS Test Reference Manual.
If I add a device to my system, how do I get SunVTS to recognize the device?
Once the Solaris Operating Environment recognizes the device (either through a boot -r or another configuration command), SunVTS uses probe routines to recognize the device. The probe routines run automatically when SunVTS is started. Also, you can have SunVTS probe your system for devices at any time with the SunVTS reprobe command.
Can I customize any of the SunVTS options or menus?
Can I add my own tests to the SunVTS environment?
Yes. See Adding a Custom Test.
Why does it take SunVTS a long time to start, and a long time to complete a reprobe?
When SunVTS starts (performing the initial probe), and during a reprobe, SunVTS has to determine your system configuration and initiate the tests that correspond specifically to your system. If your system has many devices, the probe takes a while to complete.
First, the Solaris operating environment must recognize a device before SunVTS can see it. Make sure that the operating environment is aware of the device (perform a boot -r if necessary). Second, the device might have had a failure when SunVTS probed it. Check the window where you started SunVTS to see if any errors are reported that might direct you to the problem. Third, while most Sun devices have a corresponding test in SunVTS (and therefore show up in the SunVTS UI), you might have a device that is not supported by SunVTS.
What should I do if the SunVTS appears hung?
First, give SunVTS some time to run the tests. Sometimes the tests use so much of the system resources that there is a delay in updating the SunVTS UI, and it appears hung. Second, if you determine that SunVTS is indeed hung, it might be caused by one specific test. Try deselecting the test that is indicated as currently running. You can start another UI (see Starting the SunVTS Kernel and Interface Separately) to control SunVTS.
You are probably using the physical view, which causes some devices to be listed several levels below what the trace dialog box can display. Try selecting the logical view. You will probably be able to locate the device.
How can I identify the name of the test for a given device?
The test name is enclosed in parentheses and displayed next to the device in the SunVTS UI. For example, the test for the memory device is displayed as mem(pmemtest), where mem is the device and pmemtest is the name of the test.
I get errors when I run my frame buffer test, but the frame buffer is functional. Why?
Testing frame buffers requires special considerations. In some cases you must disable the screen saver, enable a frame buffer lock option, and other steps. Sometimes the smallest mouse or keyboard input will cause the test to fail. Refer to the specific frame buffer test in the SunVTS Test Reference Manual for details.
As of SunVTS 5.0, the VTS_OLD_MSG variable is no longer supported. It was used to display test messages in a pre-SunVTS 4.0 format, usually because a script relies on the older format. Now your scripts must accept the current SunVTS message formtat. You must update your script to use the message format that has had the same format since the SunVTS 4.0 release (see TABLE 4-2).
During a SunVTS installation, I was asked if I wanted to create a new instance of this package. What does this mean?
This is an indication that one or more of the SunVTS packages are already installed. You should remove them before installing the new ones. See Installing and Removing SunVTS for the procedures.
Sometimes the SunVTS CDE UI (vtsui) fails to start, or while running, it exits with "X Error of failed request". What can I do to correct this problem?
Why do I get the following error when I select c1t0do in a multi-path configuration?
This type of error indicates that a disk drive was already selected and you tried to select it again using one of its alternate multi-path device names. SunVTS does not permit the selection of multiple paths of the same device.