Finally figured it out. The disk was in fact showing up under fdisk -l. I 
just needed to create a partition and format it. More details in the 
comments here: 
https://github.com/mitchellh/vagrant-aws/pull/93#issuecomment-50815091

On Thursday, July 31, 2014 1:40:51 PM UTC-7, Greg Barker wrote:
>
> I'm also having problems attaching ephemeral storage. After the instance 
> boots there is not ephemeral storage attached. Did anybody ever get this to 
> work?
>
> On Thursday, November 28, 2013 9:14:47 PM UTC-8, Quinton Anderson wrote:
>>
>> No one tried this before? 
>>
>> On Wednesday, November 20, 2013 3:53:27 PM UTC+11, Quinton Anderson wrote:
>>>
>>> Hi Guys,
>>>
>>> I am having trouble getting the block device mappings to work, I have 
>>> added the following to my Vagrantfile:
>>>
>>> aws.block_device_mapping = [
>>>         {
>>>             :DeviceName => "/dev/sdb", 
>>>             :VirtualName => "ephemeral0"
>>>         },
>>>         {
>>>             :DeviceName => "/dev/sdc", 
>>>             :VirtualName => "ephemeral1"
>>>         },
>>>         {
>>>             :DeviceName => "/dev/sdd", 
>>>             :VirtualName => "ephemeral2"
>>>         },
>>>         {
>>>             :DeviceName => "/dev/sde", 
>>>             :VirtualName => "ephemeral3"
>>>         } 
>>>         ]
>>>
>>> These are for m1.xlarge instances, where the AMI was built using the 
>>> following packer config: 
>>>
>>> "builders": [{
>>>         "type": "amazon-ebs",
>>>         "ami_name": "huddle-{{ user `type` }}-{{timestamp}}",
>>>         "source_ami": "ami-f261f0c8",
>>>         "ssh_username": "ec2-user",
>>>         "ssh_timeout": "5m",
>>>         "instance_type": "{{ user `instance_type` }}",
>>>         
>>>
>>>         "ami_description": "Huddle Server ({{ user `type` }})",
>>>         "region": "ap-southeast-2",
>>>
>>>         "vpc_id": "{{ user `vpc_id` }}",
>>>         "subnet_id": "{{ user `subnet_id` }}",
>>> "user_data_file":"user_data.json"
>>>     }],
>>>
>>> Does anyone have any idea what I might be doing wrong? I get a fairly 
>>> harmless output during Vagrant up:
>>>
>>> -- Block Device Mapping: [{:DeviceName=>"/dev/sdb", 
>>> :VirtualName=>"ephemeral0"}, {:DeviceName=>"/dev/sdc", 
>>> :VirtualName=>"ephemeral1"}, {:DeviceName=>"/dev/sdd", 
>>> :VirtualName=>"ephemeral2"}, {:DeviceName=>"/dev/sde", 
>>> :VirtualName=>"ephemeral3"}]
>>>
>>> All that I can see on the instance is the root device which is EBS 
>>> based. The second question I have is how do I increase the size of the root 
>>> device? 
>>>
>>> Your help is appreciated!
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to