Troubleshooting Nytro XD

Troubleshooting Nytro XD

This topic describes the known issues on the MegaRAID Storage Manager (MSM) GUI and their probable solutions.

Nytro XD Configuration Issues

*

The device discovery is automatic; the devices have to be identified automatically and added to Nytro XD as either cache devices or target devices.

*

Take care not to add the devices that have boot partition or any other information as cache devices, because it would be overwritten.

Nytro XD Start-up Issues

*

I encountered problems during start-up checks.

Restart your system.

Linux Start-up Issues

*

I encountered problems during start-up checks.

Restart your system.

*

My Nytro XD service stop failed.

The Nytro XD service stop can fail if the target device is active, or if there is an active mounted file system on the target device. Unmount all of the target devices and stop the Nytro XD service.

*

Unable to restart the Nytro XD service after the stop service failed.

If the previous invocation of the Nytro XD service stop has failed, the subsequent invocation of start service can fail or might fail to bring up all of the configured target devices. Unmount all of the target devices and stop the Nytro XD service.

Windows Start-up Issues

*

I encountered problems during start-up checks.

Restart your system.

Steady Mode Issues

This section describes the problems encountered after the Nytro XD solution is configured and when it is in a running state.

Cache Device Failure

*

My cache device failed.

*

Check the reason for failure and take suitable action.

*

Check the event messages for the failure description.

*

If the failure is correctable, perform these steps:

Bring down the server.

Remove the cache device, correct it, and reinsert it.

Bring up the server.

*

If this is the only cache device, your configuration would be lost. Bring down the server, replace the cache device, and call the LSI customer support personnel (http://www.lsi.com/about/contact/pages/support.aspx) to retrieve this information.

*

Perform the first-time configuration (see First-Time Configuration).

Logical Drive Failure

*

My logical drive (VD) failed.

*

Check the reason for failure and take suitable action.

*

Check the event messages for the failure description.

*

Check the cable.

*

Check if the back-end enclosure is up and running.

*

If the failure is correctable, perform these steps:

Remove the VD from the Nytro XD configuration.

Remove the VD from the enclosure.

Fix the VD and insert back into the enclosure.

Add the VD into the Nytro XD configuration.

*

If the failure cannot be corrected, perform these steps:

Remove the VD from the Nytro XD configuration.

Remove the VD from the enclosure.

Insert a new working VD.

Logical Drive Offline Issues

*

My VD state is offline.

*

Check if the back end enclosure is up and running.

*

Check the back end cable.

*

Check if the disk is up and running.

*

Check the event messages for the offline events.

*

Check the offline reason and take suitable action.

*

If you cannot bring it online, perform these steps:

Remove the VD from the Nytro XD configuration.

Replace the VD with the new VD.

Add the VD to the Nytro XD configuration.

*

I made my VD offline using my application, but the state is not reflected in Nytro XD.

Nytro XD is a host-based solution, and relies on the operating system (OS) component to update the device state change. Different tools might have their own way to make the devices offline or online. Nytro XD does not receive these events unless this is propagated to the OS by the corresponding software. Nytro XD does not move the state of the device if the state is not propagated, because this would result in miss match between the device OS state and Nytro XD state.

Logical Drive Online Issues

*

My VD is back online, but I am unable to access it.

See Making the Cached Logical Drives Online.

*

Foreign Configuration Issues

Nytro XD depends on BIOS UU ID to identify native and foreign configurations. Some flavors of Linux are known to report the same BIOS UU ID in different formats due to which Nytro XD might report foreign configuration on an firmware upgrade (for example, RHEL 5.7 to RHEL 6.0). You must reconfigure the Nytro XD if you notice this error.