If you cannot see your volumes or the devices associated with those volumes, you might have a connection failure. Connection failures can occur if an adapter, cable, or switch in the path between the server and the storage device fails for any reason. If there is a connection failure, repair or reconfigure the equipment.
For OES Linux, if the Storage plug-in for iManager or NSSMU for Linux do not recognize a device, it might be because NSS recognizes only what the Enterprise Volume Management System (EVMS) recognizes. NSS recognizes hard drives, CD drives, DVD drives, USB drives, and Zip* drives that are managed by EVMS. If your hard drive is managed by Linux Volume Management (LVM), it cannot be managed by EVMS, and NSS does not recognize it.
For OES Linux, whenever you reboot your system, EVMS discovers and mounts the device nodes under /dev/evms/. For example, if you use commands to create and mount a partition at /dev/sdb2/, after the reboot, EVMS discovers and mounts the partition at /dev/evms/sdb2. The iManager Storage plug-in and NSSMU work through EVMS to manage partitions, and this behavior is expected. However, if you create and mount partitions from the command line, your partitions might appear to be lost after a reboot and EVMS discovery.
IMPORTANT:If you mount pools from the command line, you must modify your mount point to the partition’s new apparent location under /dev/evms/.
If you have multiple interconnect paths in your server-to-storage configuration, turn on Multiple Connection Path Support. For instructions, see Managing Multiple Connection Paths to Devices (NetWare). Then repair the equipment.
In OES, NSS does not provide Multiple Connection Paths Support for OES Linux. Your system does not have the appropriate multipath drivers.