Ask Your Question

Another user getting Block Device Mapping Invalid

asked 2017-03-27 19:44:06 -0600

tiger gravatar image


Launch Instance

Instance Name: MyCentos7 Availability Zone: nova Count:1

Select Boot Source: Image

Volume Size: 20GB

I hit the up-arrow on a previously uploaded Ubuntu14.04.5LTS

m1.small (2GB, 20GB)

Defaults on everything from that point hence

Launch Instance

I get the same useless error everyone else does: "Error: Failed to perform requested operation on instance "MyCentos7", the instance has an error status: Please try again later [Error: Build of instance e17bc224-42e2-49ec-9eb4-47cfe40d1cc3 aborted: Block Device Mapping is Invalid.]."

"Please try again later", ummmmm, what?

Anyway, the error is useless. I have sifted through tons of posts, lots of BS. If anyone has a straight answer they'd like to share, or a legitimate course of action on how to proceed, I'd appreciate it.

edit retag flag offensive close merge delete


The error indicates that the cloud is not correctly configured. Try this: The instance launch dialog features a flag named something like "create volume", which is set to YES in the more recent versions Newton and Ocata. Set it to NO so that the instance uses ephemeral storage.

Bernd Bausch gravatar imageBernd Bausch ( 2017-03-28 13:15:29 -0600 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2017-03-28 09:04:10 -0600

updated 2017-03-28 09:05:48 -0600

I had the same problem on Ubuntu Server 16.04.02 which seemed to be that there was no device connected to cinder. With this commands (for Ubuntu) executed on the nodes where cinder is active it worked:

# dd if=/dev/zero of=./filesyst bs=2G count=1
# losetup /dev/loop1 ./filesyst
# mkfs.ext3 /dev/loop1
# pvcreate /dev/loop1 -ff
# vgcreate stack-volumes-lvmdriver-1 /dev/loop1

Change the loop device to the correct one which Cinder is using en the size of 2G...

Hope it helps!

edit flag offensive delete link more


Your solution supposes an OpenStack distro that uses loop devices to simulate physical disks, such as Devstack or Packstack.

Bernd Bausch gravatar imageBernd Bausch ( 2017-03-28 13:16:26 -0600 )edit

Yes indeed, didn't know how it was deployed but in my case OpenStack was deployed with DevStack and that fixed a similar error. Sorry for the confusion

jmoeyersons gravatar imagejmoeyersons ( 2017-03-28 14:10:14 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2017-03-27 19:44:06 -0600

Seen: 406 times

Last updated: Mar 28 '17