You are here: Troubleshooting > No Shared Storage Found when Configuring a Hierarchy

No Shared Storage Found When Configuring a Hierarchy

When you are configuring resource hierarchies there are a number of situations that might cause LifeKeeper to report a "No shared storage" message:

 

Possible Cause: Communications paths are not defined between the servers with the shared storage.  When a hierarchy is configured on the shared storage device, LifeKeeper verifies that at least one other server in the cluster can also access the storage.  

Suggested Action: Use the LifeKeeper GUI or lcdstatus (1M) to verify that communication paths are configured and that they are active.

 

Possible Cause: Communication paths are not operational between the servers with the shared storage.  

Suggested Action: Use the LifeKeeper GUI or lcdstatus (1M) to verify that communication paths are configured and that they are active.

 

Possible Cause: Linux is not able to access the shared storage.  This could be due to a driver not being loaded, the storage not being powered up when the driver was loaded, or the storage device is not configured properly. 

Suggested Action: Verify that the device is properly defined in /proc/scsi/scsi.

 

Possible Cause: The storage was not configured in Linux before LifeKeeper started.  During the startup of LifeKeeper, all SCSI devices are scanned to determine the mappings for devices.  If a device is configured (powered on, connected or driver loaded) after LifeKeeper is started, then LifeKeeper must be stopped and started again to be able to configure and use the device.  

Suggested Action: Verify that the device is listed in $LKROOT/subsys/scsi/Resources/hostadp/device_info where $LKROOT is by default /opt/LifeKeeper. If the device is not listed in this file, LifeKeeper will not try to use the device.

 

Possible Cause: The storage is not supported. The Storage and Adaptors topic lists specific SCSI devices that are supported and have been tested with LifeKeeper. However, note that this list includes known devices; there may be other devices that SIOS Technology Corp. has not tested which meet LifeKeeper requirements.

Suggested Action: Verify that the device is listed in $LKROOT/subsys/scsi/Resources/hostadp/device_info where $LKROOT is by default /opt/LifeKeeper. If the device is listed in this file but the ID following the device name begins with "NU-" then LifeKeeper was unable to get a unique ID from the device. Without a unique ID LifeKeeper cannot determine if the device is shared.

 

Possible Cause: The storage may require a specific LifeKeeper software to be installed before the device can be used by LifeKeeper. Examples are the steeleye-lkRAW kit to enable Raw I/O support and the steeleye-lkDR software to enable data replication.

Suggested Action: Verify that the necessary LifeKeeper packages are installed on each server. See the LifeKeeper Release Notes for software requirements.

 

Additional Tip:

The test_lk(1M) tool can be used to help debug storage and communication problems.

© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.