User's Manual

5. If the PCIe SSD was removed from the system, plug it back in and reactivate it.
6. Reactivate caching on the back end disk by running the command: fldc --
reactivate --disk=<disk_name>
7. Check that the PCIe SSD is now available. At the prompt, run the command: fldc --
status
If the status of a PCIe SSD is changed to failed, follow the steps below:
1. At the prompt, run either of the following commands: fldc --status --
ssd=<dev_name> or fldc --status --ssd<dev_name>
2. Use Dell OpenManage Server Administrator to determine if the PCIe SSD is at end-of-life.
For more information, see the Dell PowerEdge Express Flash PCIe SSD User's Guide at
dell.com/support/manuals.
3. The PCIe SSD may have an internal fault. Replace the PCIe SSD and follow enable
procedures as outlined in Configuring Fluid Cache For DAS Using fldc CLI.
PCIe SSD Name Changes
Probable Cause Name slippage occurs when one or more PCIe SSDs are inserted, removed, replaced, or
reinstalled. Linux sequentially numbers the PCIe SSDs during a hot swap. However, since Fluid
Cache for DAS uses UIDs to map PCIe SSDs and DAS disks internally, Fluid Cache continues to
identify components successfully regardless of Linux name slippage issue.
Solution This error does not affect the functionality of the program. To display the UID, run the
command: fldc --list --ssd
Fluid Cache Disk Does Not Appear
Probable Cause
• The Fluid Cache service did not start when you restarted the system.
• Caching is not enabled.
• The Fluid Cache license has expired.
Solution
• If after a system reboot, the Fluid Cache service did not start (even though fldc0 was
visible prior to rebooting), follow the steps below:
a. To determine the state of the Fluid Cache service, run the command: fldc --
status
b. Attempt to restart the service, run the command: service fluid_cache
start
NOTE: Fluid Cache must restart. You may want to determine whether you can
enable auto-start on boot.
• Fluid Cache for DAS may not restart if caching is not enabled on the disk. The back end
PERC virtual disk may be mounted (using the original device path) instead of the Fluid
Cache disk (using the virtual device path). For example, in the case where the original
Linux reference to the back end PERC virtual disk was /dev/sdd/data1 ext4
defaults 1 2, the Fluid Cache disk reference after --mount must be /dev/
fld0/data1 ext4 defaults 1 2
. If the original Linux reference is displayed
in the /etc/fstab file and is not commented out, you are mounting the incorrect disk. To
resolve the mounting issue, follow the steps below:
28