Unable to see the attached volume in instance

I have the same error message on a single node setup of grizzly

whats the cloud image you are using ?... Have uou find the route cause for this issue ?

Sorry I've since rebuild my dev cloud. If I were you I would be dugging the iscsi side of things.

Is it possible that the databases think the volume is connected but the iscsi connection has been dropped. i.e. have you rebooted your all in one node with the vm's and volumes still attached ?

As per https://answers.launchpad.net/cinder/+question/222896

"""""
And this problem was solved after doing: "yum install sysfsutils"
it seems "systool" was missing..
"""""

but in ubuntu I'd try "sudo apt-get install sysfsutils" which should install systool for you

Thanks for your response.

the Q/A https://answers.launchpad.net/cinder/+question/222896 its related to attachment issue.

I'm getting the log as attachment successful and the horizon & CLI also says as volume attached to instance.

cinder list
+--------------------------------------+--------+--------------+------+-------------+----------+--------------------------------------+
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+--------+--------------+------+-------------+----------+--------------------------------------+
| 03d68746-6519-4f63-91d3-ba96603cf8cd | in-use | Testvol1 | 2 | None | false | 3d34826f-480e-40bb-a2d5-9bd32b14ee05 |
+--------------------------------------+--------+--------------+------+-------------+----------+--------------------------------------+

coming to systools installation. do I need to install in launched instance or in controller node..

bcoz my VM doesnt have external route and doesnt have internet connection.

I would try in install systools on the compute node, not the vm instance

i meet the same problem, but i have installed systool on all compute nodes, no error message can be found in compute and volume log.

Shu, are you able to see the volume after your systool installation

In my environment, after installing sysfsutil tools on compute node, i saw warning message went away from nova-compute.log. However, fdisk -l on the launched instance still does not show the recently attached volume. Any ideas?

In my setup, my glance image does not load ‘acpiphp’ module to support hot plug, so after i loaded this module , everything is ok

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Hrushikesh
Sent: Friday, May 17, 2013 2:17 PM
To: Shu, Xinxin
Subject: Re: [Question #226471]: Unable to see the attached volume in instance

Question #226471 on OpenStack Compute (nova) changed:
https://answers.launchpad.net/nova/+question/226471

Hrushikesh posted a new comment:
In my environment, after installing sysfsutil tools on compute node, i saw warning message went away from nova-compute.log. However, fdisk -l on the launched instance still does not show the recently attached volume. Any ideas?

--
You received this question notification because you are a direct subscriber of the question.

I wrote up a blog post really for my own reference but you might as well have a look if your having issues with cinder as it covers the basics

http://drolfe.github.io/drolfe/blog/2013/05/01/troubleshoot-cinder-volumes/

Thanks Xinxin and Daniel. Those information were really useful. In addition, here is what my observations were:

The confusion was that if you attach a device /dev/vdc, it used to get detected as /dev/vdb. So, it looks like when you attach a device with any path (/dev/vdc or /dev/vdd), OpenStack takes care of attaching with next device in the loop. For example, if you select a flavor m1.small, the devices that gets created by default are /dev/vda (root) and /dev/vdb (ephemeral). So, when you attach disk to that instance, it will show up as /dev/vdc (regardless of which device name is suggested while attaching). Seems to be a bug, but we know now how it works.

use "sudo fdisk -l" you can see the attached disk

I am using the VMDK image pointed below:

http://partnerweb.vmware.com/programs/vmdkimage/debian-2.6.32-i686.vmdk

https://wiki.openstack.org/wiki/NovaVMware/DeveloperGuide

Uploaded to Glnace:

# glance image-create --name Debian-Modified-Img --is-public=True --container-format=bare --disk-format=vmdk --property vmware-disktype="preallocated" < debian-2.6.32-i686.vmdk

1). Launch Instance works fine.

2). Getting internal IP to eth0 with adapter_type "lsiLogic" and and disk_type "preallocated".

3). Floating ip association works fine.

4). Able to ssh to VM.

5). Able to take VM console on Dashboard.

6). Able to create volume.

7). Able to attach volume when instance is running.

8). Unable to see the attached volume in instance.

# fdisk -l

Disk /dev/sda: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000ae3eb

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 119 949248 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 119 131 96257 5 Extended
Partition 2 does not end on cylinder boundary.
/dev/sda5 119 131 96256 82 Linux swap / Solaris

# cinder list
+--------------------------------------+--------+--------------+------+---------------+----------+--------------------------------------+
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+--------+--------------+------+---------------+----------+--------------------------------------+
| a4c7ca6f-402c-4f54-bde5-0e6b6329fed9 | in-use | Vol2 | 1 | thick_volume2 | false | 2546eda7-8f92-47bd-8575-f6c26d895484 |

# nova list
+--------------------------------------+-----------------+--------+------------+-------------+--------------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+-----------------+--------+------------+-------------+--------------------------------------+
| 2546eda7-8f92-47bd-8575-f6c26d895484 | Debian-Modified | ACTIVE | - | Running | sravan-net1=2.2.3.36, <external_ip> |

I sysfsutils is already installed in Compute Node:

# yum install sysfsutils
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
Setting up Install Process
Package sysfsutils-2.1.0-7.el6.x86_64 already installed and latest version

I have the following kernel modules loaded at boot time:

# lsmod
Module Size Used by
acpiphp 13281 0
loop 9777 0
snd_pcm 47226 0
snd_timer 12270 1 snd_pcm
psmouse 44845 0
snd 34431 2 snd_pcm,snd_timer
soundcore 3450 1 snd
evdev 5609 2
snd_page_alloc 5061 1 snd_pcm
serio_raw 2916 0
parport_pc 15799 0
shpchp 21200 0
parport 22554 1 parport_pc
container 1833 0
i2c_piix4 7076 0
pcspkr 1207 0
processor 26343 0
button 3598 0
ac 1636 0
pci_hotplug 18545 2 acpiphp,shpchp
i2c_core 12795 1 i2c_piix4
ext3 94536 1
jbd 32449 1 ext3
mbcache 3762 1 ext3
sd_mod 26029 3
crc_t10dif 1012 1 sd_mod
mptspi 9617 2
mptscsih 14196 1 mptspi
mptbase 43012 2 mptspi,mptscsih
ata_generic 2247 0
scsi_transport_spi 14874 1 mptspi
ata_piix 17744 0
libata 115925 2 ata_generic,ata_piix
floppy 40923 0
thermal 9206 0
thermal_sys 9378 2 processor,thermal
e1000 77357 0
scsi_mod 105157 5 sd_mod,mptspi,mptscsih,scsi_transport_spi,libata

However, fdisk -l on the launched instance still does not show the recently attached volume.

After instance reboot I am able to see attached volume:

# fdisk -l

Disk /dev/sda: 5368 MB, 5368709120 bytes
255 heads, 63 sectors/track, 652 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000ae3eb

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 119 949248 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2 119 131 96257 5 Extended
Partition 2 does not end on cylinder boundary.
/dev/sda5 119 131 96256 82 Linux swap / Solaris

Disk /dev/sdb: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sdb doesn't contain a valid partition table

Any ideas?