> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/how-to/cinder-fails-to-create-a-boot-from-volume-instance-when-multipa.md).

# Cinder Fails to Create a Boot From Volume Instance When Multipath is Enabled on the Storage Array

## Problem

Boot from volume creation fails when multipath is enabled for the storage array. The following error can be observed in the ***pf9-cindervolume-base*** log located at */var/log/pf9/cindervolume-base.log* *.*

{% tabs %}
{% tab title="None" %}

```none
ERROR oslo.service.loopingcall [-] Fixed interval looping call 'os_brick.initiator.connectors.fibre_channel._wait_for_device_discovery' failed: NoFibreChannelVolumeDeviceFound: Unable to find a Fibre Channel volume device.
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All versions
* Cinder

## Cause

When multipath is enabled and a bootable volume is being created using a *Glance* image, the volume creation times out.

## Resolution

1. Edit the ***cinder\_override.conf*** located at */opt/pf9/etc/pf9-cindervolume-base/conf.d/* on Cinder hosts and add the following property to the backend section.

{% tabs %}
{% tab title="None" %}

```none
use_multipath_for_image_xfer = true
```

{% endtab %}
{% endtabs %}

2. Restart the ***pf9-cindervolume-base*** service using the following command.

{% tabs %}
{% tab title="None" %}

```none
sudo service pf9-cindervolume-base restart
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/how-to/cinder-fails-to-create-a-boot-from-volume-instance-when-multipa.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.