Troubleshooting for Solaris host attachment

Virtual Storage Platform Family Host Attachment Guide

Version
A3-02-2x
Audience
anonymous
Part Number
MK-90RD7037-32

The following table lists potential error conditions that might occur during storage system installation on a Solaris host and provides instructions for resolving the conditions. If you cannot resolve an error condition, contact customer support.

Error Condition Recommended Action
The logical devices are not recognized by the system. Ensure the READY indicator lights on the storage system are ON.

Ensure the Fibre Channel cables are correctly installed and firmly connected.

Run dmesg to recheck the fibre buses for new devices.

Verify the contents of /kernel/drv/sd.conf file.

File system cannot be created (newfs command) Ensure the character-type device file is specified for newfs command.

Verify that logical unit is correctly labeled by UNIX format command.

The file system is not mounted after rebooting. Ensure the system was restarted properly.

Ensure the file system attributes are correct.

Ensure the /etc/vfstab file is correctly edited.

The Solaris system does not reboot properly after hard shutdown. If the Solaris system is powered off without executing the shutdown process, wait three minutes before restarting the Solaris system. This allows the storage system’s internal time-out process to purge all queued commands so that the storage system is available (not busy) during system startup. If the Solaris system is restarted too soon, the storage system will continue trying to process the queued commands, and the Solaris system will not reboot successfully.
The storage system performed a self-reboot because the system was busy or it logged a panic message. Reboot the Solaris system.
The storage system responds Not Ready, or displays Not Ready and timed itself out. Contact Hitachi Vantara customer support.
The system detects a parity error. Ensure the HBA is installed properly. Reboot the Solaris system.