Troubleshoot SCSI devices with probe-scsi-all
If you experience trouble with SCSI devices, one of the best ways to determine if the host hardware can see the SCSI hardware is with probe-scsi-all. This recipe describes a procedure to use this command.
The probe-scsi-all is a bootprom command that is not available in the Solaris operating enviroment. To use it, you must be at the ok prompt. To access this prompt, you must be consoled into the computer through a serial interface or the RSC (remote system control) card, if present. Once you have access to the system console, the safest way to get to this prompt is to use the init command is Solaris:
This will change the system's run level to 0 (bootprom) shutting down processes gracefully. At this point, the system has not restarted. To avoid serious problems, it is best to restart the system before running probe-scsi-all. Since you need to be at the ok prompt after rebooting, set the auto-boot? environment variable to false and reboot:
reset-all
You will be able to see the system restart and should get back to the ok prompt. Now you can issue the command:
The output of this command will show you all of the SCSI devices that the host system can see and their device paths, for example:
/pci@1f,2000/scsi@1
Target 0
Unit 0 Removable Tape QUANTUM DLT7000 2150
Target 1
Unit 0 Removable Device type 8 HP C6280-7000 2.00
Before you reboot your system, you must reset the auto-boot? variable to true:
reset-all
Also see ...
H3Solaris provides extensive control over the means of looking up various name services including DNS. If DNS resolution of hostnames has not been setup, the nsswitch.conf file must be configured in addition to resolv.conf. /H3POnce you have a href="solaris_system_administration_tips96.html
H3Some problems cannot be fixed through the operating system, for example not remembering the root password or changes to configuration files that prevent the system from booting. Solaris allows booting from the CD ROM into single user mode which will allow you to mount your filesystems and repai
H3Errors in a filesystem can prevent a system from booting properly and are commonly caused by improper system shutdown. The fsck (filesystem check) utility can identify and repair errors./H3PTo check and interactively repair filesystem errors on the device c0t0d0s1, run the following command
H3When filesystem errors prevent a reboot, you are instructed to run fsck on the affected filesystem. If there are lots of errors, you may be stuck typing y for hours. An option to fsck can automatically answer yes for you./H3Pspan style="color: red"Warning:/span Use this at your own ris
H3Some applications require a specific set of patches in order to function properly. To list the applied patches or to dertermine the presence of a specific patch, use the showrev command./H3PTo list all patches applied to the system, run: br / br /div class="code"showrev pP b